problems with ADSL

quackers · 26 Dec 2006 at 15:41

My uncle has bt adsl, with two pcs connected via a linksys wireless router.

Now this is the weird part, although the router is wireless they are both connected with cables. The second pc can connect to the net no problem but has no connectivity to the other pc.

Pc number 1 cant do anything, i had a look at the settings the first pc was a on 169 etc ip address with a mask of 255.255.0.0.

Second pc, as you would expect had 192 etc with 255.255.255.0

Now i've never had any experience with adsl, but surely thats not right. I tried to release/renew the ip address on the first pc and it wouldnt have it.

I even tried to set the ip address manually on the first pc and it still didnt work, anyone got ideas? Am i missing something obvious here?

Hope that post makes some sense

Immsy · 26 Dec 2006 at 15:45

Turn off the DCHP server and then set the ips manually. Make the router 192.168.0.1, and make the pc's 192.168.0.2 and 192.168.0.3 both on subnets of 255.255.255.0 with their gateways set to 192.168.0.1

That should resolve the issues.

quackers · 26 Dec 2006 at 15:48

I did try that on the first pc, maybe i didnt turn off the dhcp server?

How can you do that in xp?

Also, do you think it could be a problem with the nic?

Immsy · 26 Dec 2006 at 19:23

quackers said:
I did try that on the first pc, maybe i didnt turn off the dhcp server?

Yes it would have made no difference unless you disabled DCHP.

quackers said:
How can you do that in xp?

You dont do that in xp, you do it using the router control panel.

quackers said:
Also, do you think it could be a problem with the nic?

I doubt it because if it was you wouldnt get any ip address.

Hudzy · 26 Dec 2006 at 19:32

I'm a bit hazy on this, but might you have to set both PCs to be part of the same workgroup?

tolien · 26 Dec 2006 at 20:05

It's got sod all to do with ADSL for starters, you'd have the same problem whether it was cable, a leased line or nothing attached to the WAN interface.

Hudzy said:
I'm a bit hazy on this, but might you have to set both PCs to be part of the same workgroup?

Nope.

If the first machine's getting a 169.etc IP, it sounds like it didn't get an answer from the DHCP server on the router - it's possible the network card's screwed, but I'd probably look at firewalls (if any) first.

Immulsifier said:
Yes it would have made no difference unless you disabled DCHP.

Disabled the machine getting an IP via DHCP, not disabled DHCP on the router, but you can't manually set an IP without disabling the interface getting an IP via DHCP...
Nothing stopping you having manually set IPs and DHCP.

Immulsifier said:
I doubt it because if it was you wouldnt get any ip address.

And it isn't getting an IP address, it's getting the autoconfiguration IP that Windows randomly picks when it doesn't get an answer from a DHCP server.

quackers · 27 Dec 2006 at 12:10

ah thanks tolien, i couldnt work out were it was getting 169 etc from. I think we are going to try it with another network card today.

HomerJ · 28 Dec 2006 at 10:43

Hi

It would also be worth trying with the network cable that is currently going to the machine that is working incase there is a problem with the network cable that is attached to machine one that is getting the 169 address.