New
#21
That's really great to hear.Thanks for posting back, glad all is sorted.
You're Welcome.
OK here we go - in as much detail as possible:
This machine is running W7Px64 and has been fine since March 2012. It is also hosting 2 VMWare servers that all have been working fine for months.
All three had static IP addresses all of which are not pingable now.
I came in last Thurs and noticed that the machine had no network access. I checked with our IT dept and there were no known issues in our building or from the port the machine was on. I hooked up my laptop the same port with the same cable and it worked fine (runs Svr 2003x32).
It obtained an IP address, and was also able to use the same static IP the W7 box uses. So no issues with same IP or blocked segments on the switch.
Looking at the N&S Center in W7, there is a yellow triangle between the computer and the Network and red X between network and Internet and the machine is showing 'Unidentified Network'.
Tried setting the adapter to DHCP - it gets an IP address but still shows as 'unidentified' and no network access. It can PING 'localhost', 127.0.0.1 and its own IP address, but not the gateway. This is wierd.
- I tried a repair on the adapter - same.
- I removed the adapter and rebooted - same.
- I installed the latest Intel WG82567LM LOM drivers from INTEL - same.
- I have performed all the 'ipconfig' and 'netsh int' commands from previous messages - same.
- Attempted to perform a re-load of W7 onto of the existing install...fails (with the same media used to do the install) at 94%.
- Booted with UBUNTU Live CD 12.04 and everything works perfectly fine - so I know that it is in Windows7.
I at the end of my rope - but before I reload this entire system, I am looking for other ideas/suggestions.
Thank You in advance.
Curtis
chev65,
Part of the diagnosis - was to remove the corporate TRENDMICRO from the machine with the removal tool, and also disable the Windows Firewall. I even added an exception to the firewall to allow for PINGS from any address.
What is strange, is that it will not even ping the default gateway that it pulled when I put it on DHCP. When set to DHCP, it will obtain an address and all information that matches my other workstation on my desk that is using DHCP. the DNS entries match, WINS, gateway and subnet mask all match my computer - all that is different is the IP address obtained.
IPV6 was disabled when the machine was first put onto the network, and the port locked into 100mpbs/Full. Even setting this to auto-obtain it will still lock in at 100mpbs/full, even though the NIC is 1GB.
-------------------------------------[IPCONFIG /ALL]
C:\Users\Admin.CN_TSSC_VM1>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : CN_TSSC_VM1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : us.ricoh.ds
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : us.ricoh.ds
Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connection
Physical Address. . . . . . . . . : 00-25-64-8F-63-20
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 151.114.16.207(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, August 22, 2012 4:01:13 PM
Lease Expires . . . . . . . . . . : Thursday, August 23, 2012 4:01:12 PM
Default Gateway . . . . . . . . . : 151.114.16.1
DHCP Server . . . . . . . . . . . : 204.80.10.65
DNS Servers . . . . . . . . . . . : 204.80.8.38
151.114.128.185
204.80.8.39
Primary WINS Server . . . . . . . : 204.80.8.38
Secondary WINS Server . . . . . . : 172.16.4.50
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2c13:5463:26df:9e5f%11(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.158.95(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 318787670
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-B3-4E-20-00-25-64-8F-63-20
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::7c1e:6678:293a:2fc9%13(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.47.201(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 352342102
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-B3-4E-20-00-25-64-8F-63-20
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{DD0DD3B0-C343-4F99-A397-EE10548FBD72}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter 6TO4 Adapter:
Connection-specific DNS Suffix . : us.ricoh.ds
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:9772:10cf::9772:10cf(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 204.80.8.38
151.114.128.185
204.80.8.39
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{612D41F5-03A0-49F0-841B-3F3D04555DA3}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.us.ricoh.ds:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : us.ricoh.ds
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
-------------------------------------[END]
Thanks Curtis
Secondary Update -
Attempted again today to re-run the SETUP64.EXE from the installation DVD. It acts like it is going to install....gets to about 95% in the second step and errors with an 0x80070003 error - with something about unable to access files in the C:\{blah blah blah} folder.
I check the folder when I accept the only option [OK] and that folder is there - but there is nothing in it.
Now I am even more bumfuddled.
Curtis
TO ALL FOLLOWING
I resolved my issue. I decided to boot into SAFE MODE and remove everything related to the NIC that was having the problem. Removed from device manager and removed all files referenced in the device manager for the drivers.
I then checked any updates that had been processed involving the NIC, and uinstalled them.
REBOOTED
The NIC came up as 'new hardware found'. I pointed to the folder where I had downloaded the INTEL drivers and extracted, and the NIC was re-installed.
REBOOTED
To my amazement - the NIC was working. I had full access to the INTERNET and company network. I was able to set the static IP Address and could ping everything and my IP was pingable.
I then did an UPDATE CENTER check and sure enough the NIC update was out there again. I immediately HID it so that it will not install again.
Thanks for all the suggestions....
Curtis