Mapping network drive problem

  • Thread starter Thread starter Sven Dieckert
  • Start date Start date
S

Sven Dieckert

Hi,

I'm at my wit's end. I hope some expert here can help me:

I want to access a shared folder on a server at my university. To do this,
I have to do the following steps:

1) I connect to the global VPN server of the university via a Cisco client.
With this I get an IP in the address range of the university

2) I connect to another VPN server via Windows XP's built-in functionality.
This VPN server only allows connections from the university's address range
(that's why step 1) was necessary)
This second VPN server allows me to access the local area network of the
institute where the desired server is

3) Having done 1) and 2) I can e.g. execute "net view /domain:<DOMAINNAME>"
on the console and get a list of all computers in this domain (including
the server I want to connect to).
I now try to map a network drive using Explorer to Z: at
"\\<NETBIOS_NAME_OF_SERVER>\shared" using "<DOMAINNAME>\<MY_USERNAME>" as
username and my password.

The last step doesn't work. When I click on "Finish" it gives me a login
prompt?! If I enter username and password as explained above again and
click OK, the login prompt just reappears and doesn't show the contents of
the shared folder!
If I try this login too often, I get a message that my account is
temporarily banned (due to security reasons).

My computer is a Thinkpad T60 with Windows XP Professional SP2.
I have tested it on another computer with Windows XP Home and a rather
fresh installation. It works there.

I already checked the windows services... but everything seems OK.
I suspect some program (before anyone asks, yes I've switched off my
firewall) or registry entry on my computer is the source of the problem.

Has anyone ever encountered something like this?

regards
Sven D.
 
I solved the problem myself. I'll post the solution here, in case somebody
else has this problem.

My computer was configured to use a stronger authentication mechanism
(NTLMv2) than the server did support.

To change this go to:
Start > Control Panel > Administrative Tools > Local Security Policy
Now go to Local Policies > Security Options
Find the entry "Network Security: LAN manager authentication level"
Set this to "Send LM & NTLM responses (NTLMv2 ....)"

Phew, this was a hard one.
 
Thank you very much for sharing your experience with us.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I solved the problem myself. I'll post the solution here, in case somebody
else has this problem.

My computer was configured to use a stronger authentication mechanism
(NTLMv2) than the server did support.

To change this go to:
Start > Control Panel > Administrative Tools > Local Security Policy
Now go to Local Policies > Security Options
Find the entry "Network Security: LAN manager authentication level"
Set this to "Send LM & NTLM responses (NTLMv2 ....)"

Phew, this was a hard one.
 
Back
Top