Problem with nic on an ME to XP Home Upgrade

[shutech]

I did an upgrade for a guy and set his PIII Micron machine up with WinXP home version going the upgrade path from ME. Here is the problem. His NIC card is not working properly after the upgrade and was working fine before. It is used for a DSL connection and have even put it on 3 different network setups to try and straighten out.

The scenerio:

1 NIC card running on a DSL Line w/ME Worked fine.

Checked machine for latest bios, It had it.

I upgraded to XP Home. Well the Netgear nic was recognized and when I unplugged or repluged the cable I got either connect or disconnect on the nic status. I saw that the machine was sending packets but not receiving packets. I made sure that firewall and TCP/IP Filter was also off. Still send no receive. I was then able to "bump " the nic to work by disabling and then reenabling the nic for a time being. so I did get nic to work until the "bump" stoped working for me.

I tried then a 3com card. Nic worked from the get go. no problem. I then gave the machine back on a friday after 2 days of working fine. I get call on sunday. No internet connection. I go over and the nic is doing the samething. Sending packets, active but not receiving them,. I doublechecked filtering and firewall both were off.

What gives here?????


any thoughts on this?

I moved PCI slots, Installed and reinstalled several times. tried the "Bump". I even tried a fresh load of XP with the netgear card and got same symptoms.

Thank You

 

[Comtech]

Release and renew the IP.
Phone the ISP, and see if they assign IP by MAC address, it may need updating on their end.
Most DSL co's recognize a legit customer by the MAC address, and assign the IP that way. Change the NIC, changes the MAC, and the customer's IP is no longer assigned correctly.
Packets will be sent, trying to "log in", but because MAC is not correct, the server rejects it as a valid customer.

Cheers,
Jim

http://members.cnx.net/reboot/

 

[bcastner]

Most cable systems use the NIC MAC address, most DSL connections use a username/password authentication scheme.

If you are using the original DSL dialer software from the ME edition under XP therein likely lies your problem. As XP contains its own PPoE client there was little cause for system developers to write an XP compatible version.

If you are using the native XP PPoE client, then it is likely either the XP upgrade applied the wrong firmware version to the adapter, or your Winsock stacks are corrupt. The former problem can be solved by going to the NIC manufacturer's web site (unless it is a Netgear 311 or 312 NIC, which do not work reliably under XP); the latter problem can be solved by rebuilding the Winsock stacks with the utility that can be found here:

http://members.shaw.ca/techcd/WinsockXPFix.exe

 

[Comtech]

OK, then DSL is different there than here, where all the DSL ISP's use MAC address (so do the cable ISP's).
If it's not MAC adress, but username/password, then bcastner is probably right.

Cheers,
Jim

http://members.cnx.net/reboot/

 

[shutech]

I can make things a little clearer here. It is Kentucky Alltel DSL which at time of install was Verizon. It is a plug and play scheme on this DSL. From wall to their router to NIC it is Always on. No PW or User Name needed. No PPoE or IPSEC. Multiple machines can connect if through a switch or hub and DHCP will pass out IPs to all of them it behaves as if you were directly attached to a LAN with DHCP.(It is a VERY open SYSTEM and I LOVE it!) Everything is autoconfigurable. I have tried this machine on my network at work. Where I have let DHCP do everything and then I manually put in the IP, gateway, and DNS; still problems. I have tried it at my house. where my DSL is behind a Linux Box running NAT and packet filtering. Still the same. It isn't an issue with IP settings or MAC. I can take my laptop off my network and go to any DSL connection and plug and get on and go to a different one and still get on. Alltel hates that scheme I know but Verizon did it that way and I am grateful. I have done other upgrades to systems that have been on DSL and Cable outside of Kentucky that employed IPSec, PWs and Usernames, and PPoE and have hated to troubleshot those. It is behaving as if filtering is blocking all incoming traffic yet I have it turned off. I am wondering what I am missing here. I am using Default drivers and am going to try the drivers from 3coms site tonight. But I did try 2 different nics with same results.

 

[Comtech]

Sounds like the IP is getting recognized at the shop, but not at the person's home.
I would guess that you've checked that it's getting a proper IP from the ISP?
Is the machine releasing and renewing the IP correctly?
Have you rebuilt the TCP/IP stack? More on that here:

http://www.mikeshardware.com/tips/tips_winxp.html#anchor12531

You could also try the Winsock tool that bcastner posted.


Cheers,
Jim

http://members.cnx.net/reboot/

 

[allteltec]

Just a note. I am a alltel tec and work with the ADSL's that alltel uses.
First was the Cisco 677 & 678 ADSL routers PPOA username and password is programed in to the router at setup time.
Next was the SpeedStream 5660 also a router PPOA username and password programed in to the router at setup time.
Now we a usering SpeedStream 5200 PPOE, If you are usering WIN9X you need a connection program alltel supplys Tango Magager, if you have WIN XP you should use the build in PPOE.
User Name and Password is the same as you first Email user name and password.
I get troubles all the time my ADSL dose not work, when thay changed there email user name or password, and dont know that thay will have to reprogram there routers or change there Tango Magager dialup info.

 

[shutech]

I tried to qualify in my first post that This was Verizon DSL before it was Alltel. When the change over to Alltel, which bought the Kentucky market from Verizon and made the change over last August they left the infrastructure that Verizon had in place. In Lexington, Kentucky it has been from the beginning a Fujitsu Speedport modem and no PPPoE. It is different from every other setup I have encountered. Ohio, Indiana, Florida. It is literally wide open. I can plug a machine in and be running as soon as it boots up. It is the PCI Nic.

Like I said I have tried this on my own network behind a linux firewall, my network at work (Which is MY network, and the straight DSL. I don't know why but send and no receive. The netgear card that was first I could only get up and running for 5-10 minutes and it would quit with no changes to any settings. I then had the 3com card up and running for me for 3 days. I gave it back and they had it running for another 3 days.... Then boom it just stopped working. I look at the stats and same thing sending packets with no receive. it recognizes that it is connected and sets itself to 100Mbps but still no receive. I am totally stumped.
I am very familiar with the DSL here. I am very familiar with Networking. But this one has me totally stumped. I have installed about 50 DSL setups here in town from straight to behind routers(Commercial and self built Linux boxes) to behind wireless routers. I know the local DSL. This was an upgrade and although I checked the MB for XP compatibility I am guessing it’s a hardware quirk I am not going to figure out. I am going to try a USB Ethernet adapter next since I have gotten no where with the PCI cards.

 

[shutech]

Latest news...

I got the nic to work. I uninstalled the adapter I had in there. I cleared out EVERY adapter key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Adapters and also 2 IPsec references that were either strings or DWORDS that were under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
and then Did a registry scrub using a thirdparty registrty cleanup tool. I then reinstalled the nic and it worked.

Now 2 days later it has stopped working again. This is getting frustraiting. I have still yet to try the USB etheradapter.

I have found out that when you get rid of a nic including uninstalling it windows does not do it very cleanly. I had about 7 adapter keys listed.


ARGGGGGG for now.

Thanks for any suggestions