Help! Can't connect to intrnet through router.

fred_easey · 25 Feb 2006 at 23:19

Hi,

I've just done a re-install of windows. I now can't connect to the internet through my router. Router is Netgear DG834G with a Nildram ADSL broadband connection. Can't for the life of me remember how I managed to get it working before.

Help!

Fred

Burbleflop · 25 Feb 2006 at 23:26

It should just be a case of set the network card in your PC to get an IP address by DHCP.

fred_easey · 25 Feb 2006 at 23:32

I need some sort of idiot's guide.

The router and ADSL connection are working fine as I am literally using them now via another computer through a wireless connection.

The computer that I just re-installed windows onto is connected to the router with a cat5 cable. It can "see" the network when I go to the network connections settings, but when I load up IE it says that there is no internet connection.

I've tried various permutations of setting up networks via the XP wizards but to no avail. Have completely run out of ideas of what to do now. It is especially frustrating as I managed to set it up fairly easily when I originally got the router, but can't remember how I originally did it :confused:

Burbleflop · 25 Feb 2006 at 23:35

Ignore all the wizards. Go into the control panel then networking. Right click on your network card, select properties then TCP/IP properties. Set it to get an IP address automatically (I may have some of the wording wrong - I'm doing this from memory) press OK a few times, wait a few seconds then try to open your web browser.

The way your network was setup initially when you installed XP should have worked - by default it will use DHCP (automatically get an IP address).

tolien · 25 Feb 2006 at 23:45

If that doesn't work, give the output from start, run, cmd, ipconfig /all.
Right click, mark, select the text, then paste.

Burbleflop · 25 Feb 2006 at 23:48

^ I knew there was somethign else I meant to say

fred_easey · 25 Feb 2006 at 23:52

ok, my TCP/IP properties are:

Obtain IP Adress automatically
Obtain DNS server automatically

IE still not working

Burbleflop · 25 Feb 2006 at 23:53

What do you get from ipconfig /all then? The settings you've described look ok.

Also, check the same settings on the working PC.

fred_easey · 25 Feb 2006 at 23:56

tolien said:
If that doesn't work, give the output from start, run, cmd, ipconfig /all.
Right click, mark, select the text, then paste.

Windows IP Configuration

That's all!

fred_easey · 25 Feb 2006 at 23:57

burbleflop said:
What do you get from ipconfig /all then? The settings you've described look ok.

Also, check the same settings on the working PC.

Can't paste for the working PC as it is a Mac

Burbleflop · 26 Feb 2006 at 00:00

All it says is 'Windows IP Configuration' nothing else? Very strange, sounds like either a barfed Windows install or messed up network card driver.

As for the Mac, assuming they stuck to OpenBSD vagluely, open a terminal and (as root) issue the command 'ifconfig' and paste the output.

fred_easey · 26 Feb 2006 at 00:01

I've just realised something, the network connection that I can "see" is in fact just the network card. If I ping the router then I get an error back, eg the PC can't see the network through the cat5 cable after all. Guess that must be the problem. Question is, how can I force the PC to connect to the router?

Burbleflop · 26 Feb 2006 at 00:03

In effect, you are forcing the PC to connect to the router by telling it to automatically get an IP address. What should happen is that the PC will look around the network, find that the router is there giiving out IP addresses, take an IP and away you go.

I'd assume something is wrong with your Windows installation or network card drivers. A knackered cable is a possibility too.

fred_easey · 26 Feb 2006 at 00:04

burbleflop said:
As for the Mac, assuming they stuck to OpenBSD vagluely, open a terminal and (as root) issue the command 'ifconfig' and paste the output.

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether 00:11:24:30:2c:18
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::211:24ff:fe23:eb73 prefixlen 64 scopeid 0x5
inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255
ether 00:11:24:23:eb:73
media: autoselect status: active
supported media: autoselect
fw0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:11:24:ff:fe:30:2c:18
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>

fred_easey · 26 Feb 2006 at 00:06

burbleflop said:
In effect, you are forcing the PC to connect to the router by telling it to automatically get an IP address. What should happen is that the PC will look around the network, find that the router is there giiving out IP addresses, take an IP and away you go.

I'd assume something is wrong with your Windows installation or network card drivers. A knackered cable is a possibility too.

Think you've hit the nail on the head, I haven't installed the Nforce drivers (it's a Shuttle SN45G).

Sorry guys, think I might have totally wasted all your time...

<taxi>

Burbleflop · 26 Feb 2006 at 00:07

fred_easey said:
Think you've hit the nail on the head, I haven't installed the Nforce drivers (it's a Shuttle SN45G).

Sorry guys, think I might have totally wasted all your time...

<taxi>

I'm surprised that even after 2 bottles of red wine I'm thinking straight.

No worries though, glad I could help.

fred_easey · 26 Feb 2006 at 00:17

All working now

Thanks for the help guys

Burbleflop · 26 Feb 2006 at 00:24

Glad to hear it