Network Adapter disconnect

  • Thread starter Thread starter Keng
  • Start date Start date
K

Keng

Sony laptop rebuilt from recovery disk. Works well except
for network adapters. On a DHCP network, it cannot come
up with an local IP address. Defaults to 169.254.xxx.xxx.

Known good network,
known good adapter(s),
known good cable
known good Port

Tried diffenent adapters with the same results, Intel,
Netgear & SMC.

Installed static IP address (Intel adapter) and ping
seemed to work but no higher level protocols would
function. No browser, or applications worked. (UDP works
but not TCP??)

Uninstalled and re-installed adapters several times.
Showed hidden devices of which there were:
Direct Parallel
Infrared Modem Port
Infrared Port
Wan Miniport (IP)
Wan Miniport (L2TP)
Wan Miniport (PPTP)

These could not be uninstalled.

Updated Windows 2000 to SP4

Not sure what to try next.
 
What happens when you issue ipconfig /renew at the command prompt.
unistall tcp/ip on the intel adapter and then reinstall tcp/ip(not
uncheck and check).

right click on the network adapter and choose status....any packets
being sent and received.
 
169.254.x.y is an apipa which indicate that you nic is set
to automatic obtain IP address but DHCP server can't be
located.

if your are connected to local network, check your DHCP
server

if you are connected to internet, check the internet
connection to isp.

Richard
 
Known good DHCP server.

Ipconfig /renew: "The following error occurred when
renewing adapter Local Aread Connection: An operation was
attempted on something that is not a socket."

I had not uninstalled the TCP/IP stack thinking that
removing the adapter would accomplish that. So I did
uninstall TCP/IP, forced a reboot, and then reinstalled
the TCP/IP stack. The problem is still the same.

I understand that the 169.254.xxx.xxx is the default IP
address range windows assignes when it cannot find a DHCP
server. Also, the error I get when I try to run a TCP/IP
program usually references a socket problem which leads me
back to the TCP/IP stack. The system at one time had a
Cisco VPN client which installs it's own deterministic
virtual network adapter. This has been removed but I'm
wondering if it corrupted something or left a remnent
somewhere.

Still Stumped.
 
Packets are being sent and received. As I mentioned, when
I set a static IP, I can ping other devices on the
network. I cannot telnet or vnc to them though. I get a
socket error.
 
Find KB Article 220874.
-----Original Message-----
Packets are being sent and received. As I mentioned, when
I set a static IP, I can ping other devices on the
network. I cannot telnet or vnc to them though. I get a
socket error.


.
Click to expand...
 
Back
Top