Cannot map network drive via VPN
Jimbo
Server with RRAS, the other a file and Exchange 2000 Server.
All my users can use VPN from home or remote locations, to connect to our
network for email, file sharing etc. - except one - you guessed it - my
boss.
He can connect to the VPN and get his email via MAPI successfully, but
cannot map a network drive on the "exchange" server.
He can successfully "ping" the server, using the "internal" address, but
when he tries to map a network drive it gives an error that "network path
\\xxx.xxx.xxx\source cannot the found"
Here is what I have tried:
- Changed the "local" login name and password to match the domain
versions, and named the "workgroup" the same as the domain.
- Logging in as a different user - both via the "Map Network drive"
dialog and using "net use" from a command prompt" - same result
- Attaching to the VPN as myself (he is a Domain Admin also)
- Tried using a "login script"
- Attempting to "join the domain" - can find the domain to tell me
that no account exist for this computer, but when I input the username,
password and Domain, it says the domain is invalid or does not exist.
- Re-applied SP3
Normally, when a map network drive is attempted, I get a "Connect as" dialog
to input a valid username and password - this does not happen - juts a 30
second wait and then the error message.
The only thing I have not done is try using a different computer from his
"at home" (cable) connection.
Anyone have any ideas ?
TIA
--
Jim Matthews
Dallas, Texas
Chris Dove
"Jimbo" <jm...@comcast.net> wrote in message
news:eyC7JkY4...@TK2MSFTNGP10.phx.gbl...
Jimbo
"Chris Dove" <cd...@nospam.myrealbox.com> wrote in message
news:OdxREuZ4...@TK2MSFTNGP10.phx.gbl...
Rabid_Roach
> Yes - Zonealarm - but I turned it off and had the same problem
>
>
It was necesssary to completly uninstall ZoneAlarm to get it to work.
Disabling it was not enough.
Jim Isaacs
news:eyC7JkY4...@TK2MSFTNGP10.phx.gbl:
When mapping the drive, after you input the server path, click the link
that says "connect using different user name"
The syntax for the user name MUST be domain\user, even though the box
will tell you this is what you will connect as. I reality, you wont
connect as that, because the computer has the 'cached credentials' of the
login name. You need to force the fact that he is in fact a user of
whatever domain...
hth..
jim
Benjamin Gay [MS]
Can he connect to other resources on the network or not too any? Also can
you connect using your credentials (i.e. is this a permission/ policy
issue)?
You can try this by performing the following:
Click start + run
type cmd.exe <enter>
net use \\machine\resource /user:domain\youraccount * <enter>
Thanks
--
Benjamin Gay (MS)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jimbo" <jm...@comcast.net> wrote in message
news:#KC5q7Z4...@TK2MSFTNGP09.phx.gbl...
Jimbo
we were able to connect successfully.
Weird, ZA is set to "ask me first" - but it never did.
Thanks to all
"Jimbo" <jm...@comcast.net> wrote in message
news:eyC7JkY4...@TK2MSFTNGP10.phx.gbl...
Rob
internal network and then trying to connect via VPN when he's on the road.
You said that you tried joining the domain from a VPN connection and it
failed. Are your entries in the LMHOSTS file set to the right IP address of
the Domain Controller?
You're looking at a BIG TIME NetBIOS problem. I ran into this same thing
when I had to configure remote Win XP Pro and Win2k Pro PC's which used to
be on the Local Area Network. It was like pulling teeth. I so wished they
had Windows 98 installed instead. VPN Clients are easy on that platform.
The other remote stations are running fine because they never touched the
internal network (or they're Win98 PCs). Am I correct?
Rob
Furthermore, he seems to be running Windows 2000 Pro ro XP Pro because you
mentioned a local user account.
"Jimbo" <jm...@comcast.net> wrote in message
news:#KC5q7Z4...@TK2MSFTNGP09.phx.gbl...