Thanks for the reply, Jim. I tried LSPfix.exe and it did not seem to do anything. I removed 3 of the files it suggested but no dice. Any other thoughts?
"lspfix" is the tool you asked about in
this thread.
Rather than adding on to other people's threads, how about posting a complete description of the current state of affairs, including the problems and what's been tried, into this thread? I'm having difficulty getting a consistent picture of the symptoms, because there's not a complete description of them in one posting.
It might be good to edit your first post in this thread, and replace the two links there with a full description.
I'm not trying to be picky - it's much easier for people to follow a problem if the problem's presented, and hopefully resolved, in one thread.
Thanks, Scott! It's
much easier to follow a troubleshooting sequence if it's all in one place!
I see two possibilities. First, the Koutech card's interfering in some fundamental way with other devices on the PCI bus. Second, there are problems negotiating link speed.
You should be able to eliminate the Fireware card as a variable by uninstalling all support for it, and removing the card.
Step (5) suggests that there's a link speed negotiation problem. The fact that
everything broke after installing the USR card in Step 7 is disturbing. It also introduced more variables.
Do you still have the 3COM card? It at least worked with the direct connection to the DSL modem.
Link speed negotiation problems are fairly common. The best fix is to lock the connection speed at both ends (NIC and network switch). Getting a client to lock the connection speed may or may not be possible. But you may be able to demonstrate that link speed negotiation is the problem by locking the connection speed on your laptop's end and making a successful connection to the client's network. For the 3C920 integrated adapter in my laptop, that setting's under the "Advanced" configuration tab for the adapter. The speeds are set under "Media Type". You'll need to experiment with the various available settings and find out if any of them work.
Since the DSL setup's entirely your own, I'd suggest getting that working before attempting to get the connection to your client's network running. Once you have bidirectional communication through the DSL modem, you'll have confidence that the adapter works in at least one environment.
If you still have the 3COM card, I'd suggest putting it back and stabilizing things on your DSL connection. If not, the only logical step with the USR card is to see if uninstalling the Koutech hardware and software, and then seeing if you can get the DSL connection working, seems like the place to begin.
I agree the problem in the link you posted sounds similar. It also sounds like a link speed negotiation problem.
Thanks again for the summary. It was
very helpful in my being able to think about your problem without having to track the symptoms across several threads.
No problem on reposting. Thanks a ton for the help, Jim! I will give the steps you suggested a shot and see if they work. Will probably reply back tomorrow after I am at work. Thanks again.
Ok, I uninstalled the software and the devices relevant to the g card and the firewire/usb card. I checked the Media Type settings under the 3com nic properties and it was on "Hardware Default". I set it to "Auto". However, after reading this post:
I am thinking that when I get to work Monday I will try some different settings, as you suggested.
The problem now is that I CAN connect to DSL but am not really able to send bytes or open web pages (page cannot be displayed and it asks me to connect via dialup even though I am shown as connected.). I tried both IE and Mozilla. This is the same problem I had initially in the work environment. So, I am restoring to Jan 8 before any of this stuff and going to see what happens. Hopefully, I can restore DSL today.
You may be having link speed problems on the home setup as well. Is your DSL connection straight to a modem, or is there a router involved? Do you get an appropriate IP address assigned? That's viewable by running Start/Run cmd.exe, and then typing
ipconfig /all in the cmd.exe window. By "appropriate", I mean an Internet-routeable IP address if there's only a DSL modem involved (ISP assigns the address), or a local address (192.168, usually) if there's a SOHO router assigning the IP address.
I particularly liked the "is it me, the card, the specification, or the phase of the moon?" question at the end of that post. There seem to be many cases where autosensing results in wierd, flaky problems that go away when both ends of the connection are speed and duplex locked.
(edit) I noted one other bit of information from your original post. You weren't having any problems with the 3COM card at home after you installed the patches for the Firewire card. All the problems began at the new client site. And that night, the 3COM still worked fine on the DSL connection. That strengthens the hypothesis that it's a link speed negotiation problem.
Sorry it has taken so long to reply, but 12 hours days and weekends away prevented it. Thanks again for all the help Jim.
So, the current status is that the Laptop works when I connect it to DSL (directly to the modem) bec. I restored to Jan. 8. It still doesn't work at work despite the fact that I messed around with the Media Type setting on the 3COM NIC. It is currently set to Autoselect when it was previously set to "Hardware Default".
The laptop does not work when I plug it into the ethernet port on the back of the US Robotics wireless router with a cable (not using the wireless g card and it is not installed or used after the system restore). Seems to have the same issue as at the work location. I can ping 127.0.0.1 successfully, but no IP or Subnet gets assigned. When I type "ipconfig /all" I get the following:
Host Name: SQuiB_Laptop
Primary Dns Suffix:
Node Type: Unknown
IP Routing Enabled: No
WINS Proxy Enabled: no
Connection-specific DNS Suffix:
Description: 3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)
Physical Address:00-08-74-E5-DE-57
DHCP Enabled: Yes
Autoconfig Enabled: Yes
IP: 0.0.0.0
Subnet: 0.0.0.0
Default Gateway:
DHCP SErver: 255.255.255.255
NetBIOS over Tcpip: Disabled
Please let me know if you have any more ideas. Thanks!
So, the current status is that the Laptop works when I connect it to DSL (directly to the modem) bec. I restored to Jan. 8. It still doesn't work at work despite the fact that I messed around with the Media Type setting on the 3COM NIC. It is currently set to Autoselect when it was previously set to "Hardware Default".
The laptop does not work when I plug it into the ethernet port on the back of the US Robotics wireless router with a cable (not using the wireless g card and it is not installed or used after the system restore). Seems to have the same issue as at the work location. I can ping 127.0.0.1 successfully, but no IP or Subnet gets assigned. When I type "ipconfig /all" I get the following:
That's different from an "autoassigned" IP address, which results from a complete failure to even find a DHCP server. The client found
something but then couldn't get an IP address assigned.
I just reread that remarkably good thread at Experts Exchange. Two points occurred to me:
First the fact that a direct connection to the cable modem works, but a connection to the USR router doesn't still suggests a link speed negotiation problem. Suppose the cable modem doesn't do link speed negotiation, but the router does, and gets it wrong. That suggests using a specific speed and duplex setting. Try 10 Mbps/half duplex, or 100 Mbps/full duplex. Those are the only two likely ones.
Second, could you have a bad Cat5 cable? I
always carry my own Cat5 cable around with me, thus avoiding possible "out of spec" cables at customer sites - and I've seen some!
I tried those two media type settings and neither worked. I also tested those at work and they did not fix it. At work, you are supposed to use newer cables. I took the one from my working desktop there and connected it to my laptop. Also, tested a cable from a laptop that was already working. Here at home, the desktop I am using to type this is connected through the wireless router via ethernet cable. I switched the cables there just to check and neither made a difference. Crazy huh?
It's amazing that something could screw up windows xp so much that it can't make a simple network connection.
At this point I would (and have) go to the 3Com properties, delete the TCP/IP protocol from the list. It will warn it will remove it from all network adapters, which is ok. Then reboot, go back to the 3Com properties, and add a Protocol (TCP/IP of course). I've had to do this twice with wireless cards under W2k. Worked both times, but I, like you, had tried everything else.
jwatt
4.4K Posts
0
February 7th, 2004 20:00
Jim
phisqb
14 Posts
0
February 7th, 2004 20:00
Thanks for the reply, Jim. I tried LSPfix.exe and it did not seem to do anything. I removed 3 of the files it suggested but no dice. Any other thoughts?
jwatt
4.4K Posts
0
February 7th, 2004 22:00
Rather than adding on to other people's threads, how about posting a complete description of the current state of affairs, including the problems and what's been tried, into this thread? I'm having difficulty getting a consistent picture of the symptoms, because there's not a complete description of them in one posting.
It might be good to edit your first post in this thread, and replace the two links there with a full description.
I'm not trying to be picky - it's much easier for people to follow a problem if the problem's presented, and hopefully resolved, in one thread.
Thanks,
Jim
phisqb
14 Posts
0
February 7th, 2004 23:00
jwatt
4.4K Posts
0
February 8th, 2004 04:00
I see two possibilities. First, the Koutech card's interfering in some fundamental way with other devices on the PCI bus. Second, there are problems negotiating link speed.
You should be able to eliminate the Fireware card as a variable by uninstalling all support for it, and removing the card.
Step (5) suggests that there's a link speed negotiation problem. The fact that everything broke after installing the USR card in Step 7 is disturbing. It also introduced more variables.
Do you still have the 3COM card? It at least worked with the direct connection to the DSL modem.
Link speed negotiation problems are fairly common. The best fix is to lock the connection speed at both ends (NIC and network switch). Getting a client to lock the connection speed may or may not be possible. But you may be able to demonstrate that link speed negotiation is the problem by locking the connection speed on your laptop's end and making a successful connection to the client's network. For the 3C920 integrated adapter in my laptop, that setting's under the "Advanced" configuration tab for the adapter. The speeds are set under "Media Type". You'll need to experiment with the various available settings and find out if any of them work.
Since the DSL setup's entirely your own, I'd suggest getting that working before attempting to get the connection to your client's network running. Once you have bidirectional communication through the DSL modem, you'll have confidence that the adapter works in at least one environment.
If you still have the 3COM card, I'd suggest putting it back and stabilizing things on your DSL connection. If not, the only logical step with the USR card is to see if uninstalling the Koutech hardware and software, and then seeing if you can get the DSL connection working, seems like the place to begin.
I agree the problem in the link you posted sounds similar. It also sounds like a link speed negotiation problem.
Thanks again for the summary. It was very helpful in my being able to think about your problem without having to track the symptoms across several threads.
Jim
phisqb
14 Posts
0
February 8th, 2004 14:00
No problem on reposting. Thanks a ton for the help, Jim! I will give the steps you suggested a shot and see if they work. Will probably reply back tomorrow after I am at work. Thanks again.
Scott
phisqb
14 Posts
0
February 8th, 2004 16:00
Ok, I uninstalled the software and the devices relevant to the g card and the firewire/usb card. I checked the Media Type settings under the 3com nic properties and it was on "Hardware Default". I set it to "Auto". However, after reading this post:
http://www.experts-exchange.com/Hardware/Routers/Q_20080995.html
I am thinking that when I get to work Monday I will try some different settings, as you suggested.
The problem now is that I CAN connect to DSL but am not really able to send bytes or open web pages (page cannot be displayed and it asks me to connect via dialup even though I am shown as connected.). I tried both IE and Mozilla. This is the same problem I had initially in the work environment. So, I am restoring to Jan 8 before any of this stuff and going to see what happens. Hopefully, I can restore DSL today.
jwatt
4.4K Posts
0
February 8th, 2004 18:00
I particularly liked the "is it me, the card, the specification, or the phase of the moon?" question at the end of that post. There seem to be many cases where autosensing results in wierd, flaky problems that go away when both ends of the connection are speed and duplex locked.
(edit) I noted one other bit of information from your original post. You weren't having any problems with the 3COM card at home after you installed the patches for the Firewire card. All the problems began at the new client site. And that night, the 3COM still worked fine on the DSL connection. That strengthens the hypothesis that it's a link speed negotiation problem.
Jim
Message Edited by jimw on 02-08-2004 08:21 PM
phisqb
14 Posts
0
February 17th, 2004 17:00
Sorry it has taken so long to reply, but 12 hours days and weekends away prevented it. Thanks again for all the help Jim.
So, the current status is that the Laptop works when I connect it to DSL (directly to the modem) bec. I restored to Jan. 8. It still doesn't work at work despite the fact that I messed around with the Media Type setting on the 3COM NIC. It is currently set to Autoselect when it was previously set to "Hardware Default".
The laptop does not work when I plug it into the ethernet port on the back of the US Robotics wireless router with a cable (not using the wireless g card and it is not installed or used after the system restore). Seems to have the same issue as at the work location. I can ping 127.0.0.1 successfully, but no IP or Subnet gets assigned. When I type "ipconfig /all" I get the following:
Host Name: SQuiB_Laptop
Primary Dns Suffix:
Node Type: Unknown
IP Routing Enabled: No
WINS Proxy Enabled: no
Connection-specific DNS Suffix:
Description: 3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)
Physical Address:00-08-74-E5-DE-57
DHCP Enabled: Yes
Autoconfig Enabled: Yes
IP: 0.0.0.0
Subnet: 0.0.0.0
Default Gateway:
DHCP SErver: 255.255.255.255
NetBIOS over Tcpip: Disabled
Please let me know if you have any more ideas. Thanks!
Scott
jwatt
4.4K Posts
0
February 17th, 2004 17:00
The laptop does not work when I plug it into the ethernet port on the back of the US Robotics wireless router with a cable (not using the wireless g card and it is not installed or used after the system restore). Seems to have the same issue as at the work location. I can ping 127.0.0.1 successfully, but no IP or Subnet gets assigned. When I type "ipconfig /all" I get the following:
IP: 0.0.0.0
Subnet: 0.0.0.0
Default Gateway:
DHCP Server: 255.255.255.255
That's different from an "autoassigned" IP address, which results from a complete failure to even find a DHCP server. The client found something but then couldn't get an IP address assigned.
I just reread that remarkably good thread at Experts Exchange. Two points occurred to me:
First the fact that a direct connection to the cable modem works, but a connection to the USR router doesn't still suggests a link speed negotiation problem. Suppose the cable modem doesn't do link speed negotiation, but the router does, and gets it wrong. That suggests using a specific speed and duplex setting. Try 10 Mbps/half duplex, or 100 Mbps/full duplex. Those are the only two likely ones.
Second, could you have a bad Cat5 cable? I always carry my own Cat5 cable around with me, thus avoiding possible "out of spec" cables at customer sites - and I've seen some!
Jim
phisqb
14 Posts
0
February 17th, 2004 19:00
Thanks for these other suggestions, Jim.
I tried those two media type settings and neither worked. I also tested those at work and they did not fix it. At work, you are supposed to use newer cables. I took the one from my working desktop there and connected it to my laptop. Also, tested a cable from a laptop that was already working. Here at home, the desktop I am using to type this is connected through the wireless router via ethernet cable. I switched the cables there just to check and neither made a difference. Crazy huh?
It's amazing that something could screw up windows xp so much that it can't make a simple network connection.
Scott
jwatt
4.4K Posts
0
February 17th, 2004 19:00
Agreed! And you've already tried another NIC in the machine, with similar results. Ordinarily that would be the next thing to try...but not this time!
Can anyone else figure this one out?
Jim
johnallg
2 Intern
•
7.3K Posts
0
February 17th, 2004 23:00