XP Network Problem

[den]

The office has a shiny new PC (Intel 2.4GHz Dual core cpu, 1GB Ram, Leadtek FX1500 256MB OpenGL certified video card.) I can get it to connect to the office LAN and see other PCs/Print/Share files through the DLink router.

I am buggered if I can get it to connect to the net. I've tried all the setup procedures I can think of but I'm not a confident hacker and XP's lack of configureability is beating me. Please throw suggestions at me. ("switch to Mac/Linux" will earn a tongue-poke.)

Comments

[theweaselking.livejournal.com]

Definitely sounds like it could be a DNS problem.

Go to a command prompt. Run "ipconfig /all" and see what kind of results you get.

You should see something like this:

Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 24.153.22.67
24.153.23.66

- make sure you've got actual numbers in where it says DNS Servers. (My numbers are Rogers Cable's DNS servers. You could use those, but the lag from australia would probably be bad.)

Another thought: Log in to the router, ensure there is no filtering or routing based on IP or MAC. Also, ensure that the DHCP server is enabled and that the address pool is big enough to provide an address for every machine.

(Wired connection or wireless?)

[dewhitton.livejournal.com]

It's a wired network. The PC that connects:

Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.112
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 139.134.5.51
192.168.0.1

The PC that doesn't connect:
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 139.134.5.51
192.168.0.1

All router filtering is done on incoming: no outward filters are enabled.

[theweaselking.livejournal.com]

Hmm. It looks good, although the DHCP range being so big that it'll give you both a 112 and a 5 is a little unusual. It's also a little weird to see the router itself being used as a DNS server.

You might want to try manually configuring the two servers I used - 24.153.22.67
24.153.23.66
- and see what happens then. It shouldn't take longer than a few seconds to toss them in.

[dewhitton.livejournal.com]

139.134.5.51 is the Bigpond DNS. I don't know why the router is 2nd, but everything is pretty much auto-configs

[theweaselking.livejournal.com]

It shouldn't hurt to have the router that way. It's just a little odd.

And since the DNS is the same on both machines, it's *shouldn't* be a DNS thing, but I've learned that you can't routers and networks. They all lie.