NTLMv2

[matt]

Hello,

I have a W2k domain that my workstation is in, and a separate stand-alone
server that I'm trying to make as secure as possible. On the Stand-alone
server I set LAN Manager Auth level in the Local policy to NTLMv2
only/refuse LM & NTLM . After not being able to map a drive from my pc to
the stand-alone server I realized my domains policy was set to the default
of using LM and NTLM only, and so I changed it to use LM and NTLM/use NTLMv2
if negotiated. I'm now finding that I still cannot map the drive to the
standalone server, and in My Computer my regular mapped drives seem to be
slow to connect and seem to need to reconnect each time I open up My
Computer. I've tried different notation to map the drive including:

"Server Name"\username
and
"Server DNS name"\username

The same event on the stand-alone sever occurs indicating bad username or
password.

Will NTLMv2 just not work if it's not bieng used within a domain? Do I need
to tell my pc to always use NTLMv2 via the registry?

Any feedback is appreciated

Thanks in advance,
Matt

 

[matt]

I have another question that is related to the same secure server I'm
putting together. I would like to know what my options are for making an
encrypted connection to the secure servers file systen from a remote
workstation. The 2 machines are in separate workgroups. So far, I've
thought of setting up an encrypted VPN, but it seems like overkill. The
server is a webserver so enabling IPSEC will cause the webpages to not be
accessible I believe. Unless IPSEC could be set up between the 2 without
the VPN. Can that be done? Are there other options I'm not thinking of?

Thanks again,
Matt