I've seen this with my own setup previously, but have not experienced
it in awhile now. A reboot will usually fix this with the problem system.
Try setting each of the systems so they are all set to the same Workgroup,
Homegroup and Home Network (this last can be a combination of different
networks such as wired & wireless networks as in the case of the WDNR3700),
then in the router, use DHCP reservation for each of the systems.
But in the case of the wireless connections, you'll have to make sure none of
the Active Networks are set to Public as they all must be set to Home Network.
If you use DHCP and the IP address is not reserved, then this can cause this very problem on a network.
When the system goes to sleep or is shut off, then later on you wake it up/turn it on, for some reason windows is not attempting to refresh the network connections and it assumes all the IP addresses are the same including it's own address which is where the IP conflict is coming in to play.
Where as if you use DHCP reservation and have your network correctly setup, you eliminate this problem.
Prior to Windows 7, I have not encountered this particular problem.
Sorry it took so long to get back. But i have done everything to add another nic card to fresh copy of windows. It does work sometimes which is weird. But i did notice something today. I had my daughters laptop doing speedtest while my computer is on which is impossible to do. So when i turn off my computer the speedtest will complete and internet will be back up to speed. So, i do another speedtest to my isp and startup my computer. during post bios the speedtest on the laptop would slow down to practically stopping. Oviously it doesnt matter which nic im using (onboard or add on card). I have never seen anything like this.
Your motherboard may have some weird internet portal access program. Maybe if you research it and turn it off it will solve the issue. I had read manufacturers had come out with boards that could do that.
I have tried another cable. I like the simple things first. But i will grab another one to make sure. But the problem exist before windows is even starting up. This machine use to run xp 64 for a good year. installed win 7 pro and had no problems since it came out until about 2 weeks ago. gonna check into some things. thanks for the help...i'll keep updating