Hello All,
I am personally running Verizon FIOS without any problems. However, my father-in-law still has Verizon DSL, which he has been using without any problems for the last 4 years until now.
To make the long story short, it seems that the LAN card that came with his old Dell PC died. I pulled it (there is no LAN NIC on the motherboard), and installed a new LAN card, which supports 10/100 MBps and is RoHS complient. However, for some unknown still to us reason, he is getting the LAN "Limited Connection" error.
I have tried everything I could think of, and spent over 6 hours with 3 different Verizon DSL tech support folks. However, we cannot even get to 192.168.1.1 (which is the address of the Westell 6100). I have tried even slowing the LAN card to 10 Mbps / Half-Duplex (or Full). TCP/IPv4 is set to obtain IP / DNS automatically and etc... It's also set to DHCP.
We know fo sure that his Verizon DSL connection does work. Why? Because when I plugged in the same Ethernet cable into a laptop that I brought with me, we had an instant Internet connection (running Windows 7).
So it must be something within Windows XP that is blocking access. I am trying to do everything to not having for him to buy a new computer at this time and save the current system.
I have deleted any and all Network cards drivers in the Control Panel / System / Devices. I have NOT messed with any registry tricks, but am now willing.
Any and all help with suggestions is greately appreciated.
Best guess is that you need a WindowsXP compatible driver for your new LAN card. You definitely need a driver, so if you "deleted any and all Network cards drivers" it isn't going to work. Go to the company website for the new LAN card and they should have a suitable driver.
There should not be any need to mess with the registry.
@walt178 wrote:Best guess is that you need a WindowsXP compatible driver for your new LAN card ... if you "deleted any and all Network cards drivers" it isn't going to work. Go to the company website for the new LAN card and they should have a suitable driver ...
Following up on Walt's suggestions, what shows up in the XP Device Manager window for the network card? Also, most network cards including newer models will automatically find a suitable generic driver in the XP install system32 folder, because network cards are pretty much "vanilla." However this isn't always the case with AMD motherboards and processors.
The LAN card is using the default Windows XP driver, which is working. There are no any custom or newer drivers from the maker, as I checked (it's Tenda Tenda L8139D 10/100 Network Adapter)
http://www.tenda.cn/tendacn/product/show.aspx?productid=213
I even downloaded the driver, and inside the ZIP I found the Windows XP driver, dated 2002. So I am sure that Windows is providing a much better driver.
Back to step 1...
Thanks for the suggestions but this did not solve it.
@quilt191 wrote:
The LAN card is using the default Windows XP driver, which is working. There are no any custom or newer drivers from the maker, as I checked (it's Tenda Tenda L8139D 10/100 Network Adapter) ... I am sure that Windows is providing a much better driver ...
As I'm sure you know, there's nothing exotic about network card drivers. Assuming all's well within the box and that there are no software firewall issues or similar anomalies, the remaining first tier possibility is the physical connection between the box and the router. IOW try plugging the box directly into a LAN port on the router with known good cables. This will eliminate any cable faults between the box and the router.
Otherwise, I haven't much else to add at this juncture. Please let Walt and me know what happens.
Hi again.
The Westell 6100 is connected directly to the PC. There is nothing in between. No routers, no splitters, nothing.
@quilt191 wrote:
The Westell 6100 is connected directly to the PC. There is nothing in between. No routers, no splitters, nothing.
Did you change the RJ45 network cable (just a thought)?
If so, that leaves software, specifically firewall software. If that's not the root of the problem then you need a pro, not a total amateur like me (smile).
Keep us posted.
Be adviced, dup posting over at
http://www.dslreports.com/forum/r28327257-connectivity-Need-help-with-Verizon-DSL-Windows-XP
Just out of curiosity, did you guys try plugging in the USB portion of the modem at some point? You have to reboot the modem if you haven't already after using USB, or else you won't be able to connect anyways, even if Windows recognizes the network adapter and a link is seen. The modem only accepts one or the other.
Hi,
No. this Westell 6100 Verizon DSL modem has never been used in USB mode.
Okay, if the XP host is having trouble even getting an IP address from the modem at this point, let's go heavy handed to fix this, all things considered.
open a command prompt window by going to Start > run > cmd.exe > OK. Alternatively, pressing the Windows key + R on the keyboard and running the program cmd.exe will do the same thing. Once command prompt is open, run the following commands in the exact order I give them.
netsh winsock reset
netsh int ip reset
When both commands complete, reboot the system. Upon coming back up, the machine should hopefully be pulling an address via DHCP from the modem. Let me know if this works, since these two commands effecfively reset the Windows TCP/IP stack.
<<
netsh winsock reset
netsh int ip reset
>>
I did try it, and when I entered "netsh winsock reset" it went fine
but then when I tried entering in "netsh int ip reset", I got a syntax error.
In any case, after reboot, it did not fix anything. But then again, I got a chance to enter the 2nd line.
In addition, I am actually going to replace the LAN card to another of the same kind.
Will update later tonight or tommorow.
Thanks again ALL for trying!
@quilt191 wrote:
... I am actually going to replace the LAN card to another of the same kind ... Will update later tonight or tommorow...
"Broken Record Department": Did you try another RJ45 Ethernet cable?
Yes I did. And if you re-read the original message, I clearely state that if I pull the RJ-45 cable and plug it iinto my own laptop, the Internet works without any problems. So the cable is not an issue.
Sorry for not responsing earlier.
Update:
I went ahead and swapped the LAN card for another one (same kind).
I ran WinSockFix v1.2 or Windows XP
I completely uninstalled Kaspersky Antivirus
I disabled the Windows Firewall
and I also manually went to CMD.EXE and did the following:
netsh winsock reset
netsh int ip reset resetlog.txt
then rebooted the machine / DSL modem
but still have the same exact "Limited or no Internet" issue. Just wow!
Any other ideas?
P.S. His Windows XP is SP3 32-bit.
Have you tried the Dell website? They have a community board and someone there might have some more (better) ideas.
The Dell website is useless, as this is definately a Windows XP-related issue. But I will keep trying.
So if DHCP is still failing, I'm curious. If you set a Static IP, does it work? You can try the following settings:
IP address: 192.168.1.200
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DNS Server: You can use 192.168.1.1, but you can throw 8.8.8.8 and 8.8.4.4 into there.
See if you can get connected with a Static IP, or at least see if you can ping out to something like one or two of the IPs I mentioned in the "DNS Server" section once you've configured a Static IP.
@Smith6612 wrote:So if DHCP is still failing, I'm curious. If you set a Static IP, does it work? You can try the following settings:
IP address: 192.168.1.200
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DNS Server: You can use 192.168.1.1, but you can throw 8.8.8.8 and 8.8.4.4 into there.
See if you can get connected with a Static IP, or at least see if you can ping out to something like one or two of the IPs I mentioned in the "DNS Server" section once you've configured a Static IP.
Interestingly enough, it did not work, but at least the Limited Connectivity Icon dissapeared from the task bar and a few packets were sent back to "somewhere", as even pinging anything still did not get any data back and I was not able to even again get to the router itself. So puzzling! |
@Smith6612 wrote:So if DHCP is still failing, I'm curious. If you set a Static IP, does it work? You can try the following settings:
IP address: 192.168.1.200
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DNS Server: You can use 192.168.1.1, but you can throw 8.8.8.8 and 8.8.4.4 into there.
See if you can get connected with a Static IP, or at least see if you can ping out to something like one or two of the IPs I mentioned in the "DNS Server" section once you've configured a Static IP.
Thanks for the suggestion but it did not work, but at least the Limited Connectivity Icon dissapeared from the task bar and a few packets were sent back to "somewhere", as even pinging anything still did not get any data back and I was not able to even again get to the router itself. So puzzling! |
Start a new topic or ask questions in the open forum.
