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

[camstone.livejournal.com]

Hmmm, sounds like a firewall issue. Did the Network router accept the configuration of the new PC's IP address for routing "net" requests out to the rest of the world?

[talvinamarich.livejournal.com]

Ugh. I have had to do this as well.

What are you using for a DNS server? Use the IP of the DLink router as your DNS server (and any other relevant addresses it asks for. It's been a while since I had to do this.) if you aren't already.

A test: plug http://64.236.29.120/ into your web-browser of choice. If CNN.com comes up, then you are dealing with a DNS issue for certain. If not, then it gets murkier.

[dewhitton.livejournal.com]

The router lets the new PC see other pcs on the network, but no connection to the outside world. I can't log on to the router from the new PC either.

[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]

Definitely a DNS problem.

[talvinamarich.livejournal.com]

Then you have narrowed it down. I am at a loss to recall where in XP you set that...I kept having to monkey with it for my wife's computer.

[theweaselking.livejournal.com]

Excellent! These are easy!

Go to Control Panel, Network Connections. Right-click on the network connection (LAN or wireless), hit Properties. Click TCP/IP, click Properties.

Right here, "Obtain DNS Server Addresses Automatically" should be selected. If it isn't, select it and click "OK" or "close" until you're back at the network connections window.

Right-click, choose STatus, click Support, click Repair, and wait for this to finish.

Poof! You should be online.

[theweaselking.livejournal.com]

Note: I'm assuming you use DHCP to assign addresses and DNS on all your machines. If you need to specify an IP address, then you will also need to specify DNS.

Specifying DNS is, fortunately, simple. Go to one of the WORKING machines, hit the command prompt, type "ipconfig /all" the way I mentioned in a previous comment. Write down the two DNS server addresses.

Go back to the new machine, and go to Control Panel, Network Connections. Right-click on the network connection (LAN or wireless), hit Properties. Click "Internet Protocol (TCP/IP)", click Properties.

Here, select "Use the following DNS server addresses" and type in the numbers you got from the working machine. Once they're in, click "OK" or "close" until you're back at the network connections window.

Right-click on the connection, choose Status, click Support, click Repair, and wait for this to finish.

And you should be online, again.

[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.

[dewhitton.livejournal.com]

Can't complete the repair due to "Cannot repair IP address."

I'll try what you suggest below, and force the bastard to accept an IP addy

[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.

[theweaselking.livejournal.com]

A-ha! Cannot "renew" IP address, right?

That's a DHCP problem. Your machine is possibly getting an address outside the router's allowed DHCP range.

DLink routers usually have an option, under either Status or LAN configuration, to view the current DHCP table. It might be enlightening to check
A) what the valid range of DHCP addresses is
B) what computers the *router* thinks have addresses from it at the moment.

[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.

[dewhitton.livejournal.com]

FIXED! It was MAC filtering on the router.

[theweaselking.livejournal.com]

See? Routers lie.

Why are you MAC filtering a wired network?

[dewhitton.livejournal.com]

Wireless laptop has to connect, and I didn't want the bastard neighbours mooching off the company broadband. They did in the early days until I shut that door.

[theweaselking.livejournal.com]

#1: WPA or even just plain old WEP will be far more effective than MAC filtering. More convenient for when you add new PCs later, too.

#2: What the kind of router lets you set MAC filtering, but doesn't let you choose to set MAC filtering for wireless clients only?

[jamesb]

All the D-Link Routers that I've seen have all or nothing MAC filtering. There's no option for just Wi-Fi MAC filtering.

[theweaselking.livejournal.com]

How... odd.

One more reason to stick with NetGear, then, hmm?

[dewhitton.livejournal.com]

you bet!

[jamesb]

If you'd seen any of my many LJ posts about the random rebooting problems that I had with a series of different model D-Link wireless routers during the 3 year warranty period, you'd definitely steer clear of them. The last replacement they sent me a few weeks before the warranty expired is still sealed in its box.

My current router is an old salvaged Pentium class PC running the Linux based IPCop.