Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Windows Server 2008 R2 loses ability to connect to network

Active Directory, Domain, DNS, WINS, DHCP, SBS, New Releases.

Windows Server 2008 R2 loses ability to connect to network

Postby guest » Thu Jul 29, 2010 11:48 am

Hi,

I have the following environment.
Server 1: Windows Server 2003 SP2, file server
Server 2: Windows Server 2008 R2, Terminal Server.

Server 1 is in OldDomain and Server 2 is in NewDomain.
Users are migrated from olddomain to new domain using ADMT so that they have a SID history.

Users in newdomain have a home dir configured in the AD that is pointing to a share on Server 1.

When Server 2 is newly rebooted users logging into server 2 using a RDP client will get a personal home drive mapped to the share on server 2.

After a while users will no longer get a home drive mapped when they logon to server 2.

If I try to map the home drive manually I can sometimes map it on the UNC DNS name (FQDN used) and sometimes using the IP address of server 1.

When I cannot map the home drive on the UNC name I will get the following error:
System error 53 has occurred. "The network path was not found"

When I cannot map the home drive using the IP address I will get the following error:
System error 59 has occurred. "An unexpected network error occurred."

In both cases I can ping Server 1 on both the DNS name and on the IP address.

If I then restart Server 2 then everything is working again as it should for a while.

Does anybody have a clue what is going wrong and how I can debug the problem?



Edit: Forgot to write that Server 2 is a virtuel server running in a HyperV Cluster.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Re: Windows Server 2008 R2 loses ability to connect to network

Postby guest » Thu Jul 29, 2010 11:49 am

Good news - a hotfix is in the works and a workaround has been identified:

Root cause is that since this is SMB1 all user sessions are on a single TCP connection to the remote server. The first user to initiate a connection to the remote SMB server has their logon-ID added to the structure defining the connection. If that user logs off all subsequent uses of that TCP session fail as the logon-id is no longer valid. As a workaround for now to keep the issue from happening you will want to have the user not logoff the Terminal Server only disconnect their sessions.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm


Return to Windows

Your Ad Here

Who is online

Users browsing this forum: Google [Bot], Yahoo [Bot] and 5 guests