Browsing to root of Server 2019 drive

[Manny-Tech]

I'm logged into my laptop as a standard user but use elevated permissions to get to shares etc.. For some reason I cannot browse to the root of our new Server 2019 install. I get an error of:

 

\\servername.local\c$ 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 username, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

 

When I try to connect to this particular share, like any other server, it prompts for my administrative account. I of course enter that and I get the above message. If I log into the server with my administrative account I can browse the root of the drive no problem. I clearly have access just not remotely. I've tried multiple machines too. I thought it may be UAC related so I temporarily removed this from the server but got no further joy on that front. Also worth noting if I log into my laptop as my administrative account then I can also browse to the root of the drive, I'm just trying to be cautious and try not to login as domain admin.

Has anyone come across this one before?

 

Edited September 9, 2021 by Manny-Tech

[Norphy]

Does this server host your user area share, or another share that’s automatically mapped when you log on? If so, your standard user account is already logged onto the server but it doesn’t have access to the c$ share. When you try to access the c$ share, the server asks for credentials but then says ’Hold on, someone is already connected to this server from this user session, I’m not going to let you in’.

 

The only way you’re going to get that share is to disconnect any mapped drives, close any SMB sessions from the server side then try again.

[Manny-Tech]

I did have staff areas mapped - I have since removed these and removed the sessions from the server, but still no luck. Interestingly, I still have a mapped drive to our I:\ drive for SIMS and can browse to the e$ of that server despite already having a connection via the mapped drive.

 

I'm failing to see why something so simple isn't actually working. I definitely have permission. \\servername\c$ - prompts for a privileged account, enter in domain admin account and then get rejected. Login to machine as domain admin and browse to \\servername\c$ and connects fine.

 

I will do some more digging next week.

[Norphy]

It's not a question of permissions. The issue is that Windows doesn't let you have two SMB sessions signed in with two different users from a single Windows user session to the same address. This is apparently by design. Reading further into it, it's a client side thing rather than a server side thing, I got that bit wrong so apologies about that.

 

According to this Microsoft article, you can get around this restriction by connecting to the server using different methods, i.e. use an IP Address for one connection, use the DNS name for another, use the NETBIOS name for a third. That's probably worth a try too.

[Manny-Tech]

Spot on @Norphy looks like I'd got folder redirection enabled on my documents still connecting to that server. Removed that, and I can now browse with the UNC path - thanks for your help on this!