Can't browse Win2K servers from Win2k3 server - not accessib
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Can't browse Win2K servers from Win2k3 server - not accessib

 
Post new topic   Reply to topic    Windows Server Forum Index -> General Discussion
Author Message
Kenny
Guest





Posted: Thu Nov 10, 2005 5:50 pm    Post subject: Can't browse Win2K servers from Win2k3 server - not accessib Reply with quote

Hello,

I'm logged in as the Administrator and I'm receiving the following error
whenever I try to browse from My Network Places and double-clicking on a
Win2000 server on a different subnet (192.168.2.x). I can see the servers but
I cannot access them from a Win2003 server. Windows XP clients have no probem
accessing them.

\\servername is not accessible. You might not have permission to use the
network resources.

Any suggestions?

Thanks.
Back to top
Todd J Heron
Guest





Posted: Sat Nov 12, 2005 9:50 pm    Post subject: Re: Can't browse Win2K servers from Win2k3 server - not acce Reply with quote

"Kenny" <Kenny@discussions.microsoft.com> wrote ...
Quote:
I'm logged in as the Administrator and I'm receiving the following error
whenever I try to browse from My Network Places and double->clicking on a
Win2000 server on a different subnet (192.168.2.x). I can see the servers
but I cannot access them from a Win2003 server. >Windows XP clients have no
probem accessing them.

\\servername is not accessible. You might not have permission to use the
network resources.

There could be a security setting put in place prohibiting the connection.
Check NTFS and Share permissions on the remote host. If NTFS and Share
permissions are correct, then refer to KB article 281648 which states:

This behavior can occur because the Local Group Policy, specifically those
in the Computer Configuration\Windows Settings\Security Settings\Local
Policies\Security Options folder have a restrictive setting.

Some of the policies that may cause this behavior are:

1. Digitally sign client communications (always)
2. Digitally sign server communications (always)
3. Digitally sign server communications (when possible)
4. LAN Manager Authentication Level set to Send LM and NTLM - use
NTLMv2 session security if negotiated
5. Secure channel: Digitally encrypt or sign secure channel data
(always)
6. Secure channel: Require strong (Windows 2000 or later) session key

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> General Discussion All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB