Once in a while (no pattern noticed yet), my Windows 7 system will drop from the local network. All other systems on the lan can see each other, but suddenly, the Windows 7 system is not accesable. But, if I ping it or connect to a share by IP, it works fine. The W7 sys can see and access the rest of the network just fine. It only happens w/ the W7 sys disappering. and none of the other systems on the lan. The firewalls are disabled on all local systems. This is a mixed network of Windows systems (XP, 2003, Vista), and is the only Windows 7 system on the lan.

You haven't said if you have disabled the power saving features of the network devices on Windows 7. You say on one hand the Windows 7 system is not accessible but then you say if you ping it or connect to a share by IP address it works fine, so how is it not accessible?MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]

How does it work if you access the Windows 7 computer by the computer name when the issue occurs? I suggest you upgrade the network adapter driver for the Windows 7 computer. If the issue still occurs, please try to upgrade the firmware of the router.Arthur Xie - MSFT

Power saving is not on. The problem is that while I can ping it, won't show up as a named computer on the network. That screws up the network shares from other systems. I suppose I could assign static IPs, but that makes the Windows 7 system seem like the low-tech system on the network that I can't trust, and it's also not fixing the problem.

The NIC seems fine, as there is no loss of IP or internet use. Just the local network by name. Even when I type out a path on another system using the Win7's name, it just won't find it.It hasn't happened lately, so I'm not sure if something I've done has fixed it. I tried a few tweaks over a day or so, so I wouldn't know which of them may have done it. I'll come back if it does it again. It was doing it once a week, but hasn't done it since the first post here (and used to happen every week or so).

I have the same problem I lose the shares I can still remote desktop onto the windows 7 machine but the shared drives stop wotking until I reboot. The computer is an Asus CG5270 with windows Ultimate 64 bit

It happened again this morning. Almost happens once a month or so. I'm looking in the logs, and I see a lot of logoffs by the Guest account around the times I search the network for the Win7 system.

Using the computer name is flaky without a wins box on the network.Most networks in business / corp use static IP addressing, so no that is not even a issue, DHCP is designed for home users / public networksso they do not have to get under the hood.as it can be reproduced at will let us look at outside causes. go grab "pinglog" use it on the win 7 box set it up to ping outbound some place.set it send out small packets at 5 mins each see if the network is dropping off and reconnecting or if thenetwork is stable.I assume there is no IP / Name conflict on the network like someone coming in a wi-fi node / or plugging with a static IP or the same computer nameI also assume this is wired networked, as you do not have other win 7 boxes you need to go here and confirm that all the gear is on the listhttp://www.microsoft.com/windows/compatibility/windows-7/en-us/default.aspxif it is not then post router / firewall / switch specs here.I have had to replace a few decives ( routers / switch cheap Nics) and clean up some wiring for windows 7

This fixed it for me Apparently you need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly. Set the following registry key to ‘1′: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache and set the following registry key to ‘3′: HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size After making these changes and restarting, I haven’t seen this issue arise again http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017

I already had those set, unfortunately.

It's a wired netork w/ wifi access, but the network is secured so unauthorized systems are not a problem.The big issue isn't the Win7 box losing connectivity, as it sees the network just fine. It's the Win7 box becoming invisible to some or all of the network. Currently, it's the 2003 box I have that is having the most issues seeing the Win7 system. Even after rebooting both boxes, it refuses to see the Win7 box by anything but IP.

Is there a way to apply a name to an IP address on the individual systems?Case in point, the 2003 box that refuses to see the Win7 system by name and only IP. Can I tell the 2003 box that IP = name somewhere, so regardless if it can see the Win7 system name, it just assumes it by an internal rule?

it is called a host file you edit it to add ip to namelike this192.168.1.100 win7_box_name #common name