Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

System error 67 / The network name cannot be found / VPN Trouble

3,536 views
Skip to first unread message

Jim Voris

unread,
Dec 17, 2000, 8:37:57 AM12/17/00
to
I'm attempting to configure an NT/SP6a workstation to connect to our domain
via a VPN. The connection seems to have been established. I am able to
ping "servername". I know for a fact that the directory "directory" has
been shared.

I attempt to map a drive typing

net use k: \\servername\directory\

The following errror is returned:

System Error 67 has occurred.

The network name cannot be found.

Any suggestions?

--

Jim Voris
Atlanta

reply to jim_...@yahoo.com

David Johns

unread,
Dec 17, 2000, 2:40:55 PM12/17/00
to
Couple of things. First, type "net view \\servername" at a command
prompt to see what shares are visible. If there's more than a single
screen's worth, you can use "|more" at the end of that command. If the
share name you're trying to map to doesn't show up, confirm the actual
share name you're trying to use is correct. If it does show up in the
list, you may want to provide a little more info on the VPN connection.

David Johns - MCP


In article <900D5037Aji...@207.46.230.185>,


Sent via Deja.com
http://www.deja.com/

Jim Voris

unread,
Dec 17, 2000, 5:57:33 PM12/17/00
to
Thanks for taking the time to help me. Here's what I've tried.

I tried "net view \\servername" which returns

System error 53 has occurred.

The network path was not found.

I tried "net view \\servername /domain:domainname" which returns the same
error.

I tried "net view \\serverip" which returns

System errror 5 has occurred.

Access is denied.

I tried "net view \\serverip /domain:domainname" which returns the same
error.

These errors occur for all servers.

The only other helpful piece of information that I might provide is that
Windows 98 SE machines have succeeded in connecting to the VPN and mapping
the same shared drives.

Jim Voris

unread,
Dec 22, 2000, 8:50:28 AM12/22/00
to
Solution:

I was using the "hosts" file for name resolution and not the "lmhosts"
file.

1) I deleted all of the names, except for localhost, from hosts. (I don't
know whether this was necessary or not.)

2) My Lmhosts file appeared in c:\winnt\system32\drivers\etc as
Lmhosts.sam. I copied this file and renamed it to Lmhosts (no extension).

3) I appended the following to the end of the file, for each of the
servers I wished to map to:

10.x.y.z servername #PRE #DOM:domainname


4) I can then map the drive using

net use * \\servername\sharename password /user:domainname\user

FYI, I created a batch file (login.bat) to do the above. For each drive I
add the following line:

net use * \\servername\sharename %1 /user:domainname\user

Then I need only type "login password" from a command line to connect to
the drives.

--

Jim Voris
Atlanta

reply to jim_...@yahoo.com

0 new messages