Why do I get "\\SERVERNAME is not accessible... permissions"... but it *is* accessible via IP address
I've been having some unexplained issues with some 2003 and 2008 Servers that seem similar. I'll focus on one particular:
Server 2008, brand new from Dell in August 2011. I migrated Server 2003 and a half dozen users to it. Users have a H:\ home folder and a P:\ public shared folder.
-They seem to get disconnected from particularly the H:\ drive.
-Their My Documents is redirected to H
-They get a red X over the H mapped drive letter
-clicking on the red X can make it go away sometimes and they connect.
-They dont seem to have this problem with the P drive.
-I can re-map the drive and they're generally good until reboot, or logoff/logon the next morning when red X reappears.
-primary DNS points to the server 192.168.1.2, secondary to the router, 1.1.
On a client PC, if I drill down through My Network Places > Microsoft Windows Network > DOMAINNAME > SERVERNAME, I get an error that SERVERNAME is not accessible, You might not have permission to use this network resource, etc etc. Then if I enter \\192.168.1.2 in the address bar it goes right to it and I can click through folders. THEN, I go back and click on the SERVERNAME in the left window, I get the same error several times and finally it will let me connect after a while with the servername.
Should I be focusing in on DNS errors on the server?
Server 2008, brand new from Dell in August 2011. I migrated Server 2003 and a half dozen users to it. Users have a H:\ home folder and a P:\ public shared folder.
-They seem to get disconnected from particularly the H:\ drive.
-Their My Documents is redirected to H
-They get a red X over the H mapped drive letter
-clicking on the red X can make it go away sometimes and they connect.
-They dont seem to have this problem with the P drive.
-I can re-map the drive and they're generally good until reboot, or logoff/logon the next morning when red X reappears.
-primary DNS points to the server 192.168.1.2, secondary to the router, 1.1.
On a client PC, if I drill down through My Network Places > Microsoft Windows Network > DOMAINNAME > SERVERNAME, I get an error that SERVERNAME is not accessible, You might not have permission to use this network resource, etc etc. Then if I enter \\192.168.1.2 in the address bar it goes right to it and I can click through folders. THEN, I go back and click on the SERVERNAME in the left window, I get the same error several times and finally it will let me connect after a while with the servername.
Should I be focusing in on DNS errors on the server?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
just simple try ... stop windows firewall check if its will work or not
ASKER
Ok. It'll take a few days to get to that pc and try it. I'll post back soon.
ASKER
I should be in front of the system soon, if not I'll close out the question.
ASKER
In DNS event log I have a TON of Event ID 7062 for source "DNS-Server-Service" which is:
++++++++++
The DNS server encountered a packet addressed to itself on IP address 192.168.7.2. The packet is for the DNS name ".". The packet will be discarded. This condition usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
5) Root hints.
++++++++++
I checked the Forwarders list - it seemed the most probable issue - and found that there was an entry in there referring to its own IP address:
--------------------------
IP Address______________Serve
192.168.7.2 goenvio.com
--------------------------
"goenvio.com" is a locally hosted web application for the company's LOB app. I contacted Envio support and asked if it would be a problem to try removing that which they said should be fine. I removed the entry but don't think it helped the H drive problem but it did stop the error 7062.
++++++++++
The DNS server encountered a packet addressed to itself on IP address 192.168.7.2. The packet is for the DNS name ".". The packet will be discarded. This condition usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
5) Root hints.
++++++++++
I checked the Forwarders list - it seemed the most probable issue - and found that there was an entry in there referring to its own IP address:
--------------------------
IP Address______________Serve
192.168.7.2 goenvio.com
--------------------------
"goenvio.com" is a locally hosted web application for the company's LOB app. I contacted Envio support and asked if it would be a problem to try removing that which they said should be fine. I removed the entry but don't think it helped the H drive problem but it did stop the error 7062.
ASKER
This was very informative and possibly helpful:
++++++++++++++++
Set this up so you won't get the autodisconnect on network drives
http://support.microsoft.com/kb/297684
++++++++++++++++
I should also mention that the main issue or problem this causes is with Outlook. The H:\ is their home drive and the hidden "mail" folder is there. Their PST files for Outlook are in there so that the pst can get backed up by the server automatically.
Maybe this is the deeper issue - if the H: mapped drive gets auto-disconnected, why wouldn't the act of opening Outlook reconnect the H connection? When Outlook opens, we'll get errors that the PST isn't accessible, etc. Generally we close Outlook, click the H drive, it reconnects H:\ and then reopen Outlook.
I know that MS doesn't support a network location for the PST, but I've seen it done for years at other companies and it seems it *can* work. If I need to move the PSTs off the server, what would the plan be to get it backed up? How do other people deal with the Outlook PST issue?
++++++++++++++++
Set this up so you won't get the autodisconnect on network drives
http://support.microsoft.com/kb/297684
++++++++++++++++
I should also mention that the main issue or problem this causes is with Outlook. The H:\ is their home drive and the hidden "mail" folder is there. Their PST files for Outlook are in there so that the pst can get backed up by the server automatically.
Maybe this is the deeper issue - if the H: mapped drive gets auto-disconnected, why wouldn't the act of opening Outlook reconnect the H connection? When Outlook opens, we'll get errors that the PST isn't accessible, etc. Generally we close Outlook, click the H drive, it reconnects H:\ and then reopen Outlook.
I know that MS doesn't support a network location for the PST, but I've seen it done for years at other companies and it seems it *can* work. If I need to move the PSTs off the server, what would the plan be to get it backed up? How do other people deal with the Outlook PST issue?
That would solve that problem.
Run ipconfig /flushdns on clients as well.
Have you tried the autodisconnect solution?
Run ipconfig /flushdns on clients as well.
Have you tried the autodisconnect solution?
ASKER
I haven't tried the autodisconnect solution. It just seemed like that was more for a peer to peer network than a domain server / client network. I can't believe that as a normal course of action for a new Server 2008 install, I'd need to disable that. Am I wrong? Should I try it anyhow?
ASKER
ok, on the Server I went to
HKEY_LOCAL_MACHINE\SYSTEM\
and entered ffffffff in the key.
Should I also use:
net config server /autodisconnect:number
and enter 65,535?
I found another site with the same question. For reference: http://www.winvistatips.com/red-x-mapped-network-drives-new-server-2008-r2-windows-7-domain-t824201.html They mention "disable chimney" I'll have to look that up
What about disabling power saving mode on the NIC?
HKEY_LOCAL_MACHINE\SYSTEM\
and entered ffffffff in the key.
Should I also use:
net config server /autodisconnect:number
and enter 65,535?
I found another site with the same question. For reference: http://www.winvistatips.com/red-x-mapped-network-drives-new-server-2008-r2-windows-7-domain-t824201.html They mention "disable chimney" I'll have to look that up
What about disabling power saving mode on the NIC?
This is a problem with all versions in domain or workgroup
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I use Trend Worry Free Business Security for Corp AV and MalwareBytes' Antimalware as additional layer. I haven't heard or experienced either blocking NetBIOS. Maybe though?
>>Are you able to see the server by browsing through My Network Places etc and see the server name listed?<<
Yes, as I mentioned in the post:
"On a client PC, if I drill down through My Network Places > Microsoft Windows Network > DOMAINNAME > SERVERNAME". It's only when I click on the servername I get the error.
CMD>> ping "SERVERNAME" results in a reply from 192.168.7.2. So, forward resolution works
NSLOOKUP 192.168.7.2 produces the correct SERVERNAME.DOMAIN.local and Address. Reverse lookup works.