dsl77
asked on
Cisco VPN client or DNS error?
Hi experts,
From time to time, my users are missing the mapped drives when logging on using Cisco VPN client. Sometimes the drive letters exist, but are empty. And now and then the drive letters are missing completely. Even when trying to run login script. (e.g. Net use j: \\servername\sharedfolder\ folder ) it cant establish the connecting.
From start run, when typing \\servername\sharedfolder\ there are no visible shares they are all missing.
But sometimes it helps typing \\ipadress\sharedfolder and the shares are showing.
Thanks in advance.
/David
From time to time, my users are missing the mapped drives when logging on using Cisco VPN client. Sometimes the drive letters exist, but are empty. And now and then the drive letters are missing completely. Even when trying to run login script. (e.g. Net use j: \\servername\sharedfolder\
From start run, when typing \\servername\sharedfolder\
But sometimes it helps typing \\ipadress\sharedfolder and the shares are showing.
Thanks in advance.
/David
just a thought... i'm wondering if it's to do with name resolution.. and if the shares are empty then it *could* from a previous authentication to the network.. since the ip connection's available you see the files, but the user's not reauthenticated to the network (due to dns resolution ??) therefore has no permission to list files..
ASKER
Would this explain why it sometimes works with the ip connection?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Is there a tool to verify and fix this?
You could try adding the servername / IP address in the hosts file of a test client. This way you should be able to ping the server on it's name. If this works the DNS works correctly.
Then try if you are able to map the drives the normal way. If this works it is indeed a DNS problem. If not... we'll have to keep looking ;-)
Then try if you are able to map the drives the normal way. If this works it is indeed a DNS problem. If not... we'll have to keep looking ;-)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
how did you get on?
ASKER
Had a minor 'bad' DC2 running - this was causing the client confusing