SOLVED: Windows 7 Professional loses network connectivity after a restart
Since the Dell Optiplex 980 mini tower did not have an internal fiber adapter, I used a Allied Telesis AT-MC101XL external transceiver(http://www.alliedteles
I spoke to Allied Telesis tech support who tested a AT-MC101XL with Windows 7 and when Windows 7 Professional (64 bit) booted they too lost connectivity. However, the next day when I called, they told me they did not lose any connectivity and they were puzzled why they lost connectivity the first day. The same transceiver works fine with a Windows Vista/XP(both 32bit) machines in our office.
I took out a working internal Allied Telesyn AT-2701FX PCI 100Mb Fiber Adapter) card whose manual is at http://www.alliedteles
The driver installed fine and I could access the network. But, when I rebooted, I noticed a yellow flag on the network icon(located on the right-bottom corner) which states "Limited or no network connectivity". I went to the Device Manager, disabled the network card, waited for a minute, re-enabled it and then I was able to access the network.
The Dell machine(running Windows 7) has McAfee antivirus, all Windows patches, the firewall is turned on, no suspicious programs are starting up which could cause the network connectivity issue.
Allied Telesis claims their cards are compatible with Windows 7 professional 64 bit and their other customers don't have issues after reboot. But, I don't know if their other customers have static IPs for their devices and manual entries for DNS servers like we do.
1. What could be the reason that after booting up, there is no connectivity when using a Allied Telesis external transceiver or internal fiber card, but after a power reset is done for external transceiver or disable/enable in device manager for internal card I can access the network?
2. Is Windows 7 Professional 64 bit somehow configured to need a dynamic IP? After reboot, the static IP I assigned persists so it is not that the static IP address is wiped out which causes the network issue.
3. How can I fix it other than downgrading the user from Windows 7 64 bit to Windows XP 64 bit?
Any suggestions would be appreciated.