Mapped drives disconnect and will not reconnect
i having odd problem drives mapping on w2k8r2 server.
randomly drives become unavailable users remote on server itself. server has 35 rdp users , no actual pc clients. drives being mapped, on rdp server. here layout:
\\server1 - pdc, dns, dhcp. win2k8r2 xxx.xxx.xxx.150
\\server2 - rdp win2k8r2 xxx.xxx.xxx.155
\\server3 - virtual server 32 bit apps not compatible - win2k8 32 bit xxx.xxx.xxx.160
all 35 users log server2. server 24/7 , in use 24 hours day between users in , offshore. users 35, 10 off shore on night.
there 5 drive mappings setup via policy
f: \\server1 - ftp drop box
m:, r:, q:, , p: - data shares on server2 off of local d: drive.
server2 has 2 raid arrays, 2nd array d: , shares live. users log 155 , drive maps 155. drive mappings show error cannot connect them, red x on drive. stop working. happens every 2-3 weeks randomly far can tell. on several occasions problems resolves in few minutes. i'd the call have problem, remote in , in 2-3 minutes problem gone. other times problem not rectify until server rebooted.
here odd part. f: drive on server1 works no problem.
if login 150 or 160 server drives 155 server show fine , work no problem.
if browse 155 server \\server2 of shares show not accessible.
if browse 155 server \\xxx.xxx.xxx.155 shares show , work.
the dns has record \\server2 fqdn correct. can ping , resolve fqdn off of 155 server itself.
i've scoured logs , can't find @ all. no errors on either 150 or 155 server. i've tried restarting dns on 150, browser services on 155, nothing works.
it totally random far can tell , seems have during low server loads. there few people work late night , we've had happen either around 10pm @ night when there 2-3 people on before offshore people start, , in morning when we're down 2-3 off shore people , users starting login.
neither of servers rebooting due updates anytime happens.
any idea's?
hi eric,
thanks posting here.
> if browse 155 server \\server2 of shares show not accessible.
what’s particular system prompt popped when attempted access?
please try modifying problematic mapping driver address “ \\localhost\*** “ or “ \\<fqdn of server 2>\*** ”and check if issue persist?
meanwhile, i’d suggest take introduction of smb signing feature in link below , check registry key settings:
server message block communication between client-side smb component , server-side smb component not completed if smb signing settings mismatched in group policy or in registry
http://support.microsoft.com/kb/916846
thanks.
tiger li
technet subscriber support in forum
if have feedback on our support, please contact tngfb@microsoft.com
please remember click “mark answer” on post helps you, , click “unmark answer” if marked post not answer question. can beneficial other community members reading thread.
Windows Server > File Services and Storage
Comments
Post a Comment