Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: swissbill on August 11, 2007, 12:32:18 PM
-
Hi,
I have a problem that is driving me mad! I had an old router which connected 2 wired PCs to the Internet and it worked fine but had no wireless facility. I recently purchased a Linksys WAG200G router. The first wired PC works fine, the 2nd. wired PC will not work, but at this PC the network adapter seems fine: local area connection indicated as working. A new 3rd PC works fine on wireless. I have tried just about everything for the 2nd PC, moving it next to the router, using the same port on the router as the 1st PC, using the same cabling as the first PC. All the port lights at the router indicate okay. I also reset the IP setting on the 2nd. PC. Gone through the router settings again and again, even tried wireless on the 2nd. PC: all to no avail! (All the PCs are Dell, of different model nrs. but recent).
Tried the Linksys community but with little help.
Would be extremely grateful for any suggestions!
-
Welcome to the forum, swissbill.
I'm not an expert on this subject, or anything else for that matter, but I once had similar problems with a Linksys gateway. Are all three PC's running XP or Vista? I couldn't get a PC running ME to work in my case, although it would work with Linux.
I'm sure somebody with more expertise than me will be along to help soon.
-
Hiya
I take it that you have switched everything off (so the router and all PCs are off), to give any weirdness chance to disappear?
What happens on the second PC if you go to a command prompt and type tracert www.bbc.co.uk (as per kitz's tutorial here (http://www.kitz.co.uk/tech/tracert.htm))
If that doesn't work at all i.e. gives you "Unable to resolve target system name" then it's a problem with DNS on that PC. If you type tracert -d 195.62.28.175 (this is the address of kitz.co.uk) then it should work.
Whatever the results of these tracerts are if you would be good enough to copy and paste them in here as per kitz's Save Results (http://www.kitz.co.uk/tech/save.htm) page, then we might be able to see what's going on.
-
Presumably the router is configured as a DHCP server, and all the PCs are configured to get their IP addresses by DHCP?
-
You'd hope so... actually, swissbill could you also type ipconfig /all into a command prompt on both the "broken" PC and one of the working ones, and let us know what that says too. :)
-
Hi all,
Many thanks for your suggestions, but in reply to Mr. Chris here are the results so far:
1. Here is the config of the “broken” wired PC:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Bill>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : lin
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-12-3F-72-81-91
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 195.186.1.109
195.186.4.109
Lease Obtained. . . . . . . . . . : 11 August 2007 18:02:48
Lease Expires . . . . . . . . . . : 12 August 2007 18:02:48
2. Here is what happened when I used the tracert with the same PC:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Bill>tracert www.bbc.co.uk
Unable to resolve target system name www.bbc.co.uk.
C:\Documents and Settings\Bill>tracert -d 195.62.28.175
Tracing route to 195.62.28.175 over a maximum of 30 hops
1 Destination host unreachable.
Trace complete.
3. And here is the config of the working PC (wired):
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Bill>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Verger
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-11-11-4D-42-0E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 195.186.4.108
195.186.1.108
Lease Obtained. . . . . . . . . . : 11 August 2007 12:23:03
Lease Expires . . . . . . . . . . : 12 August 2007 12:23:03
Again, many thanks for your help, if you could continue I will be very grateful,
swissbill
-
Hi Bill
Thanks for doing that - unfortunately it looks a bit weird to me! It's like your PC isn't recognising that you have a router connected - very odd..
Can you please type route print at the command prompt for me and let us know what it says? Also arp -a might give me another clue.
The theory I'm working on is either (a) your PC's routing table is foobar'd... but given you've said you reset your IP settings (presumably with netsh int ip reset?) that shouldn't be the case, but it's worthwhile having a look anyway...
or (b) you have some kind of what's called an LSP hijack... more info at http://www.kitz.co.uk/tech/TCPIP.htm - download and open LSPFix and if you could say what's in the list of "Keep" entries, and if there are any problems found, I can try and help diagnose if this is the case or not!
Cheers :)
-
Hi Chris,
THanks for your help. The reset I use is from Dell support : Reset the TCP/IP settings (XP): netsh int ip reset dellip.txt I do not get any answer on this command, but Microsoft seem to indicate that this could be normal.
Here are the results of tests under theory (a)
C:\Documents and Settings\Bill>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10005 ...00 12 3f 72 81 91 ...... Intel(R) PRO/100 VE Network Connection - Pa
ket Scheduler Miniport
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.100 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.0.0 255.255.0.0 169.254.154.212 169.254.154.212 30
169.254.154.212 255.255.255.255 127.0.0.1 127.0.0.1 30
169.254.255.255 255.255.255.255 169.254.154.212 169.254.154.212 30
192.168.1.0 255.255.255.0 192.168.1.100 192.168.1.100 20
192.168.1.100 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.100 192.168.1.100 20
224.0.0.0 240.0.0.0 169.254.154.212 169.254.154.212 30
224.0.0.0 240.0.0.0 192.168.1.100 192.168.1.100 20
255.255.255.255 255.255.255.255 169.254.154.212 169.254.154.212 1
255.255.255.255 255.255.255.255 169.254.154.212 2 1
255.255.255.255 255.255.255.255 192.168.1.100 192.168.1.100 1
Default Gateway: 192.168.1.1
Persistent Routes:
None
C:\Documents and Settings\Bill>arp a
C:\Documents and Settings\Bill>arp -a
No ARP Entries Found
C:\Documents and Settings\Bill>netsh int ip reset dellip.txt
Cheers,
bill
-
I noticed mr_chris was logged in earlier, swissbill. Reckon he's gone to scratch his head, or phone a friend about your little conundrum. :)
-
Hi Chris,
In terms of plan (b), I downloaded Microsoft's guide to reset IP settings on the working PC and ran it on the "broken" PC - the program completed successfully, but the PC still did not connect. I then downloaded LSPfix and ran it on the "broken" PC - program Winsock2 Repair facility - and was flagged "No problems Found." (I did not attempt the advanced settings.)
The PC seems to be working, but will not recognise the router. I think that at this stage, I'll put back the original router and check whether the "broken" PC will still work with it! If it does, I'll rethink my options.
Thanks for all your help,
bill
-
I dont fully understand routing tables - so I'm possibly pointing out something stupid.
But why is the local link block 169.254.0.0 pointing towards a specific IP in that range for the gateway (169.254.154.212)?
If you follow that through 169.254.154.212 goes back to the loopback address.
Similar with multicast 224.0.0.0. points to that particular IP address.
If I look at my own routing table all gateways/Interfaces are in the same range [either "home" or the PC or router IP addy]
>> No ARP Entries Found
:(
When I first saw your post I suspected either firewall or a DHCP problem.. the LSP thing was also something suspected - several years ago that used to be pretty common by certain malware, but not something I see as much mention of these days thankfully.
Have to wait see if chris can shine any light on the above...
I know he was in work today, but nipped home early afternoon to do something before having to go back there later so he may not have had chance to look properly yet.
-
Yes, certainly scratching my head over this - it works... yet it doesn't?
Routing table looks ok to me - I am wondering about the APIPA address though (169.254.x.x) why you have so many of those, plus a reference to network interface #2 - when in fact you haven't got one listed at the top of the routing table.
However, given there's only one default gateway, and it's pointing the right way, I can't think what's going on, although I suspect it may be something to do with that extra interface that's being reported.
As for how to go about sorting it without actually sitting there, I don't know.
I will continue scratching :|
-
:(
Well, the plot thickens or maybe it's me. I had another look at the router settings. My ISP (bluewin) seems to recommend PPPoE for encapsulation, the Linksys manual recommends RFC 1483 Bridged, while the guys at the shop insisted upon RFC 2516 PPPoE, which works in a limited sense as it gives me 1st PC wired, and the 3rd PC via wireless, but the 2nd PC wired is "broken". After attempting various options I reverted back to the original RFC 2516 PPPoE and discovered that the "broken" PC was now running full Internet access! This lasted a few minutes before falling out and providing a connection only to the ISP's home page, with no access to any of their pages.
On this basis I will re-contact Linksys.
Cheers,
swissbill
-
Since the linksys is an ADSL router, you really want to set the connection type as PPPoA (PPP over Asynchronous Transfer Mode[?]) if available, as this is the type of connection ADSL uses. PPPoE is usually used on cable routers.
-
:(
Thanks, but no connections work on config PPPoA, only on PPPoE. Linksys recommended that I upgrade to the latest firmware for the router. Which I did do, but no improvement, except for a disillusioning few seconds when the 2nd. PC connected to the Internet for a short time and then fell out once again .....
swissbill
-
It shouldnt be bridged mode (unless your using it with other equipment?). UK adsl uses PPPoA although a lot of other countries use PPPoE which is probably why only PPPoE will work for you.
I cant offer any more real suggestions Im afraid... but one thing did occur... and Im possibly clutching at straws
Ok you have 1 wired connection that works... and 1 wireless connection thats working.
You very briefly got a connection on the 2nd wired connection... was that by any chance up until the "1st" pc connected to something.. which then stopped the "2nd" from working?
-
Also clutching at straws, if you swap the connections on the router for the first and second PC, so the 'broken' one is plugged in where the 'working' one was... does that swap the problem around?
/me is lost for ideas now :(
-
:)
I found the problem! I'm sorry to have caused so much trouble and the fault should have been more obvious to me :-[ . On the 2nd. PC I had thought I had deactivated the AVG firewall and virus protection, but had only deactivated the AVG control center. This suddenly occurred to me as I realised that the "broken" PC was still receiving AVG updates. I deinstalled fully the AVG software, and the PC immediately gained full Internet access. I then reinstalled the free AVG virus protection and it still works fully (I will have to work out how to reinstall the licensed full AVG portection including firewall - presently using Windows firewall with AVG limited to virus protection). Note the same AVG program ran and runs on the 1st. PC without any problems.
Again, sorry for all the work caused - many thanks to all but especially to Mr. Chris.
:) swissbill
-
Glad you found the problem, swissbill.
-
Glad you found out what it was. :)
Thanks for letting us know