It says something like: xxx.xxx.xxx.xxx is not accessible. You might not have permission to use this network resource. Contact the administratior of this server to find out if you have access permissions.
I sometimes get error messages when I am working that have to do with Network Communications. The most recent was an Open Folder Error is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Logon Failure: The target account name is incorrect. In my case I actually got this message because the computer I wanted to connect to was not the one I wanted to connect to. Let me explainFirst a picture of the error message:I actually have two different networks (actually many more but let’s keep it simple) One network is my LOCAL network and one is my VPN (DirectAccess) CORP network.
My local desktop name is Dan-HP. My local domain is baystate.loc. My CORP network is NA.CORP. My other domains are demo environments (Contoso, WoodgroveBank, etc).
When I try to access my local workstation (from my laptop) I typed in and I get the above message. What is actually happening under the covers is DirectAccess is forwarding (or intercepting and forwarding) the request onto the DirectAccess or VPN.
The network thinks I am trying to connect to //dan-hp/na.corp. In reality, I am trying to connect to //dan-hp.baystate.loc.
To solve this problem all I need to do is explicitly connect to the computer giving the fully qualified domain name of the machine. This way the network request will go directly to the machine I want to connect to. In this case I would go to and I am presented with a folder list of shares on my dan-hp desktop.So why does this happen?
What if this happens and you are not using a VPN or multiple networks? Let me start with most of the time when there are networking issues, it is either a DNS issue or a local firewall issue. I would start by eliminating DNS as the problem. To do this simply try to access the machine via it’s IP address. In my case that would look something like this:. If that is successful it is DEFINTELY a DNS issue.
If you are suspicious of a DNS issue it is very easy to put a work around in place. I posted an article on a few months ago. Follow that article to see if you resolve the problem. Fixing DNS is a whole different discussion for another day but I did give a couple quick tips below. The next thing I would try is disabling the firewall on the destination machine. One of these two tips should help you resolve the issue.A little more about what is happening under the coversComputers speak via a network using an IP address. People tend to understand or speak in “ Real Names” (eg.
Dan-HP) when referencing to a specific computer. Since computers only talk in numbers and people only talk in names a resolution or reference table of translations between names and numbers must be done in order for communications to happen.
When you type in a name the computer will try to find the IP address of the computer you are searching for. It will try to “ resolve” the name by looking in several places. This is called “ Name Resolution”. The first place it looks is in the c:%system%driversetchostshosts. This is a text file that allows you to create your own table to be used for resolution of an IP address. The next place it goes to is your local cache, then to the DNS server (Dynamic Name Service) as is indicated by your Primary or Secondary DNS server which you can obtain from a command prompt by typing IPConfig /all.
In the case of DirectAccess, it actually has a local cache of computers and redirections which are setup via Group Policy. I will be doing a video on the details of this soon and will try to remember to come back to this post and do a cross reference. When the local computer does not have anything in the hosts file or in the local cache it requests it from the DNS server but before it does that it actually changes the computername on the fly. It changes it to a fully qualified domain name (assuming you have Append These DNS suffixes (in order) selected. It will try for each domain you have listed in the domain list.
It will try them in the order they are presented in the advanced TCP/IP settings – DNS Tab under Append these DNS suffixes (in order). You can change the order of the search using the up and down arrows in the Advanced TCP/IP settings. Yeah, 'definitely a DNS issue' isn't quite true. It's true for this case, but not all cases. I have the same error, but it's because of a problem with my domain controllers.
I'm still looking for a solution. Because I'm still looking, I.could. be wrong, but I'm pretty sure my DNS is just fine. My network is considerably simpler. Unfortunately, using Windows Explorer to servername doesn't work, but does work. It.suggests. a DNS problem, but it isn't.
Dcdiag is listing all sorts of problems. It's a DC issue. For the next person doing the same search(To be clear, the article above is not wrong, it seems to be good in the problem that it addresses, it's just that this error message comes from more than one possible source.). Hello, I have a problem accessing my network drive and the error I got is as stated below:10.83.87.250 is not accessible.
You might not have permission to use this network resource.Contact the administrator of this server to find out if you have access permissions.Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.Think you could help?The network drive was connected to the router via USB and I try to set up Secure Folder Access.
![]()
I entered the credentials, whether is correct or wrong, it just shows me that message.
Im trying to create a share which is on my admin server to a user account which is on the DC on my 2nd server.I can manage to access a share on the 2nd server from my admin server but i can't access any shares from the 2nd sever to the admin server.I get an error message that says:'(IP address)' is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. There are currently no Logon on servers available to service the logon request.I try to access it by typing the ip address in windows explorer which works when i do it on user accounts on the admin server.Can i get some help on how to resolve this please?Both servers have there own DC's.
I have 2 physical servers. 1 server is running Windows Server 2008 R2 and the other server is windows 2012 R2. All the computers on both domains are running windows 7.Edited Jun 1, 2015 at 13:15 UTC. This is a protocol Issue.In Server 2012 R2 Microsoft have discontinued support for CIFS and I think the very early SMB type connections.Your shares on the 2003 server will not support the current SMB3 connections. In order to connect to your 2003 server you need a common protocol. You cannot install SMB3 on the 2003 server and SMB1 of CIFS is not supported by 2012 R2 Out of Box.So you need to add SMB1 support to the 2012 R2 server. This can be done by adding that part of the File Sharing Feature.You will then be able to browse file shares on old Windows and old Linux Systems.Take a look at this link .
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |