Unknown device on the network
After a power outage, one of the servers cannot be connected to
Server is "acquiring network address" even though it is hard-coded (192.168.0.10)
Server reports IP address conflict
nbtstat reports that IP resolves to something named RTKDASHOOB (not the server's name)
MAC of RTKDASHOOB changes frequently- and always to something that doesn't show up when I enter it into an online database
Cannot open UNC or HTTP of the IP nor connect via Computer Management
If the network cable is pulled from the server, ping to the IP or name fails
Malware Scan of server comes up clean
Install second NIC- no change
Hard code second NIC to 192.168.0.12
Can now connect to the server by name, and if I ping it, it resolves to .10 even though there is no cable in the NIC that is .10
If I try to connect to the server by IP it fails, even if after I create a host file entry
Thoughts?
Server is "acquiring network address" even though it is hard-coded (192.168.0.10)
Server reports IP address conflict
nbtstat reports that IP resolves to something named RTKDASHOOB (not the server's name)
MAC of RTKDASHOOB changes frequently- and always to something that doesn't show up when I enter it into an online database
Cannot open UNC or HTTP of the IP nor connect via Computer Management
If the network cable is pulled from the server, ping to the IP or name fails
Malware Scan of server comes up clean
Install second NIC- no change
Hard code second NIC to 192.168.0.12
Can now connect to the server by name, and if I ping it, it resolves to .10 even though there is no cable in the NIC that is .10
If I try to connect to the server by IP it fails, even if after I create a host file entry
Thoughts?
ASKER
I tried swapping cables with another server that was running fine.
Did the second suggestion as well- the "new" NIC does the same thing as the onboard one.
Did the second suggestion as well- the "new" NIC does the same thing as the onboard one.
try these command from a elevated cmd prompt ( run as administrator)
netsh int ip reset c:\resetlog.txt and netsh winsock reset catalog after rebooting go into networking and reconfigure your static ip information
netsh int ip reset c:\resetlog.txt and netsh winsock reset catalog after rebooting go into networking and reconfigure your static ip information
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No resolution found- problem just disappeared.
Alt : disable/remove first nic settings and set second nic up as .10