\\server UNC command works with Admin but not User

[fandab]

Hello,

I have 2 untrusted subnets connected via VPN.

A user from SubnetA successfuly establishes a terminal services session with a Win2k3 server on SubnetB.

The user completes some work, and attempts to save the file to their local server on SubnetA. To do this they use an RUN command \\server and are prompted for username & password. Once authentication has been established, they can browse & save their work to a folder on their local server.

Unfortunatly for reasons unknown this has stopped working. When using \\server, they recieve the error..

\\server is not accessible. You might not have permission to use this network resource. The user name could not be found.

However, if they use the IP address it works and prompts for authentication.

If I establish a terminal services conection as the network administrator it works both with name and IP.

There are no additional events logged.
The DNS server has correct records.

Sounds like an MSCE exam question, any ideas would greatly appreciated, I have ran out....

 

[nevets2001uk]

It does sound like some sort of DNS issue but I can't imagine why it would work for one user and not another unless it's a permissions problem as well?

My initial idea would be to run NSLOOKUP under the standard user account and then query the server name to see if that resolves correctly? At least then you'll get more of an idea if DNS is functioning for the user.

Steve G (MCSE / MCSA:Messaging)

 

[fandab]

Hi,

Thanks for your reply, I tested DNS query as the user and it returned the correct IP address for the server in SubnetA.

Its a tricky one

Thanks

 

[nevets2001uk]

Very strange. Would a mapped drive be a suitable solution? It may well cause the same error though.

Steve G (MCSE / MCSA:Messaging)

 

[fandab]

Hi,

Tried.....get the error..

No network can be found

Very wierd

Thanks