Windows Server 2008 R2 loses ability to connect to network share
Has this ever been resolved???? Losing mappings and connections from the RDS sessions to the file-server. Will work for three-four days, and then loses connections. Only recourses are to 'stop-start DNS server', and if that fails to resolve mapping issues, then a complete server reboot of the AD server (not the RDS server) restores the capacity to map to network drives from the RDS. Environment: Server 2008 R2 AD, Server 2003 R2 Member server - file server, Server 2008 R2 Hyper-V RDS - Terminal server. Has this ever been resolved???? Original thread stops with NO RESOLUTION on July 1, 2010. It is now June 2011. Any hotfixes from MS? Same problem as all throughout the original thread - with no resolution at that point.
June 2nd, 2011 9:26pm

Can you post an unedited ipconfig /all from DNS server and problem client? Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2011 9:55pm

I have not seen the Original thread but I had a similiar issue last year that was caused by the Version of Symantec that was running on the server. After much frustration an upgrade to the latest version of the AV fixed the issue. May not be the same and you may have ruled this out already but thought I would mention it.
June 3rd, 2011 5:23am

Hello, this sounds like pure DNS problems, so please post the requested output from Dave PatrickBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2011 9:00am

From the previous thread, one of the last posting prior to the thread being 'locked': "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. Marked As Answer byLaura ZhangMicrosoft Employee, ModeratorWednesday, June 09, 2010 2:13 AM" I had to really dig to find the hotfix located here: http://support.microsoft.com/kb/2194664 Problem resolved. As it appears to affect *everyone* who runs a 'mixed' environment of Server 2008 and Server 2003, why is this 'hotfix' not built into a service pack by now? Patch was released in August 2010!!!!!! Our install was in April 2011 and we suffered almost two months of user angst before 'stumbling' onto this hidden - yet essential - hotfix.
June 3rd, 2011 11:24pm

Hello, the DNS server is Server 2008 R2, the 'target' share folders are on Server 2003 R2 file-server role, and the client is a Server 2008 R2 RDS server. The hotfix provided by MS appears to have resolved the problem. Thank you for your assistance.
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2011 11:49pm

Hello, the DNS server is Server 2008 R2, the 'target' share folders are on Server 2003 R2 file-server role, and the client is a Server 2008 R2 RDS server. The hotfix provided by MS appears to have resolved the problem. Thank you for your assistance. http://support.microsoft.com/kb/2194664
June 7th, 2011 4:23pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics