GeordieWire
asked on
Strange network behaviour
I have a machine that has come in to be rebuilt, user could'nt remember the password for windows, they had password protected the bios and forgotten that password and the cd-rom wasn't set to boot.
The machine has 2 network cards, one onboard and the other a PCI one which gives me the impression that there have been previous problems with the on-board card.
With both cards on in device manager, neither can see a cable plugged in however after disabling it, the pci card recognises that it is connected but performs most perculiarly.
It has a connection but picks up some wierd IP Address when set to DHCP and it doesn't send or receive packets. On manually setting the Network settings it appears to connect and shows the correct IP address but still there are no sent or received packets.
Has anyone seen this or similar before and can you give me any pointers as to what might cause this. Been playing for hours and I can't sort it.
Many Thanks
The machine has 2 network cards, one onboard and the other a PCI one which gives me the impression that there have been previous problems with the on-board card.
With both cards on in device manager, neither can see a cable plugged in however after disabling it, the pci card recognises that it is connected but performs most perculiarly.
It has a connection but picks up some wierd IP Address when set to DHCP and it doesn't send or receive packets. On manually setting the Network settings it appears to connect and shows the correct IP address but still there are no sent or received packets.
Has anyone seen this or similar before and can you give me any pointers as to what might cause this. Been playing for hours and I can't sort it.
Many Thanks
What IP address does is get? If it is in the 169.254.0.0/16 subnet, that is an IP address that MS automatically configures when a NIC is set for DHCP and it does not receive a DHCP address.
try ipconfig /all in run command and check whether both the device and ip adress are detected correctly. if not try unplug the all the ethernet and blue tooth device connected and try iprelease command and rebbot the system..
ASKER
ok, the plot thickens
I have tried changing to 10 meg full duplex, it disconnects and then re-connects picking up 169.254.191.84 as the IP address
My router is set with a dhcp range of 192.168.0.2 - 255
Could both cards be whacked?
Oh i have plugged a cable in from another machine that is known good and have the same problem.
I have tried changing to 10 meg full duplex, it disconnects and then re-connects picking up 169.254.191.84 as the IP address
My router is set with a dhcp range of 192.168.0.2 - 255
Could both cards be whacked?
Oh i have plugged a cable in from another machine that is known good and have the same problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Is it possible to get around the Bios Password?
You need to check the info for that model PC. Typically there is a jumper on the MB someplace that can changed to bypass the password.
Try changing it to 10 Mb Half-duplex or even 100 Mbps Half-duplex. Typically if there is a negotiation issue it is with duplex not speed.
You could try a NETSH INT IP RESET from the command line, also a NETSH WINSOCK RESET. Could be a problem with the TCPIP stack.
We are sure that you was test with another cables, right?
for the bios you will see a jumper in the motherboard, you can give us the model to help you better.
regards
for the bios you will see a jumper in the motherboard, you can give us the model to help you better.
regards
now click in configure then go to advanced tab.
find something about link speed and duplex or something similar
you will see values that say 10mb and 100mb half or full duplex and automatic too...
normally this value is in automatic.
put the value in 10mb full duplex and try plugin the cable, then you can try with 100mb too
regards