Windows Server 2008 R2 Disappears from Network

A customer has her network set up as a work group, but she has a computer with Windows Server 2008 R2 set up as a file server.  Everything was OK until I reset her router (a SonicWall TZ150)  I have reconfigured the firewall, and all computers including the server have Internet access.

I can ping from computer to computer, except to the server.  The computers can see each other in the network browser.  There is an entry for the server in the network browser, but selecting it returns "Network Path Not Found". The server can ping to other computers, but they do not show up in the server's network browser.  The other computers cannot ping the server by name or by IP address.

If I reboot the server it is accessible for a few minutes, but then it disappears again.  The server does not Lose Internet access.

I have turned on Network Discovery and NetBIOS over TCP/IP and turned off the Windows firewall.

What would cause the server to keep Disappearing?
Who is Participating?
ajwukConnect With a Mentor Technical Consultant / Project ManagerCommented:
Do you mean you've installed RRAS on this box? Can the server ping or browse to the clients when the clients cannot browse to the server?
If RRAS has been installed it could be the IPsec and simple firewall config there which is causing you issues.
ajwukTechnical Consultant / Project ManagerCommented:
 What's reported in the server's event log around the time you try to make an SMB connection from one of the PCs?
rhaveyAuthor Commented:
There seems to be a consistent Event ID 20106: Unable to add interface {C012B29-3A9B-4202-BEA7-813ECA2638FA} with the router manager for the IP protocol.  The following error occurred. Cannot complete this function.

The same error is in the log with interface {6CCB2ED3-C807-48ED-9981-E1BB1B0B32E2}.

Both errors are in the log twice, once for IPv4 and once for IPv6.  IPv6 is not being used.

The errors started about the time I tried to get Remote Access working.  I don't remember which services I turned on, but I will check the list.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Windows Server 2008 R2 has a firewall that is different from what we are familiar from Windows XP.
In Windows Vista the introduce term Type of Network with 3 level of trust.
Public means that your server could not trust even its own subnet.
Home means that your server could trust its own subnet.
Work means that your server could trust even host that are reachable from a router.
You should set the third level of trust unless you have a domain.
Home is the one you should choose.
I don’t know how your server behaves when you shut down its firewall.
Every time your server loses its link connection reevaluates its network and that is probably the reason of the changing behavior.
Once you turn on the firewall and set the network type to home you should google how you can make that your server keeps its settings.  Maybe the change of the evaluation of the network is because the server is using DHCP.
rhaveyAuthor Commented:
Thank you.  Your first comment was the clue that I needed.  I turned off RRAS in Services.msc, and everything worked.  I will bear you comment on IPsec in mnd when I try to enable RRAS again.  For now, the fire is out.
ajwukTechnical Consultant / Project ManagerCommented:
No worries. Glad it's working again. RRAS is fine but just remember that you are turning your server into a software router at that point.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.