Re: NET USE in 2k3
- From: "Mordred201" <Mordred201@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 15 Dec 2005 11:37:03 -0800
John,
I experienced a similar issue at work. My problem ended up being a local
security policy setting.
Local Policies
Security Options
Network Security: Minimum session security for NTLM SSP (there will be one
for clients and one for servers)
Mine were all checked, and I received system error 67 whenever I tried to
map a drive to a Cellera NAS server. After clearing the settings, everything
mapped fine.
"John Schneider" wrote:
>
>
> "Ian" wrote:
>
> > John Schneider wrote:
> > > "Ian" wrote:
> > >
> > >
> > >>John Schneider wrote:
> > >>
> > >>>I have a laptop running Windows 2003 server, a Desktop running Windows XP
> > >>>Pro, and a batch file that I use once a week to synchronize some files
> > >>>between the two. A line in the batch file that maps a drive on the laptop to
> > >>>a shared drive on the Desktop worked in Windows 2000 server but doesn't work
> > >>>in 2k3.
> > >>>
> > >>>The laptop is a corporate machine, and part of our corporate domain. The XP
> > >>>box is part of my home network, with the stock named workgroup MSHOME. At
> > >>>home, I'll plug the laptop into my home network. This is the line I use to
> > >>>map the drive:
> > >>>net use J: \\DesktopName\SharedFolderName Password /user:UserName
> > >>>This worked fine in Win 2k, but since I installed 2k3, that line now gives
> > >>>me the error:
> > >>>System error 67 has occurred.
> > >>>The network name cannot be found.
> > >>>
> > >>>If I substitute "DesktopName" with the actual address, such as 192.168.1.103
> > >>>(all the machines at home are on a network/router), it maps just fine. The
> > >>>only problem with hardcoding that address is that whenever the router is
> > >>>recycled, the Desktop will probably get a new address.
> > >>>
> > >>>I know I'm missing something obvious here, but I just can't figure this one
> > >>>out.
> > >>>
> > >>>John Schneider
> > >>>
> > >>
> > >>Have you setup RRAS to allow broadcast name resolution?
> > >>
> > >>Try using deskopname.domainname ie \\desktop01.mydomain.local
> > >>
> > >>Ian
> > >>
> > >
> > >
> > > Ian,
> > >
> > > Thanks for the response, but I'm not familiar with RRAS. Is this something
> > > new with 2k3?
> > >
> > > The XP box I'm trying to connect to is not part of a domain, but just the
> > > standard MSHOME workgroup. Unfortunately, I'm in the office now and won't be
> > > able to test this until tonight. Are you saying that I should try it like
> > > this:?
> > > net use J: \\DesktopName.MSHOME.local\SharedFolderName Password /user:UserName
> > >
> > > Thanks again,
> > > John
> > Apologies,
> > I assumed you would be trying to access the corporate network from
> > home (rather than the other way round).
> >
> > Your corprate machine will be preconfigured to use the company's name
> > servers and dependant on your VPN setup broadcast name resolution my be
> > disabled - Probably safer to use IP Address to connect to the machine
> >
> >
> > Ian
> > e.g net use J: \\192.168.1.10\SharedFolderName Password /user:UserName
> >
>
> Ian,
>
> While I really do appreciate your responses, the whole purpose of this
> question is to get the mapping working with the machine name, just the way it
> did with Win 2k, even if it involves having to further qualify the machine
> name in some way. My point is that I don't want to have to hard-code an IP
> address. Again, this worked fine with Win 2k Server, so I'm trying to figure
> out what is different with the configuration of Win 2k3 Server that is
> preventing the mapping from working with the machine name.
>
> As for the VPN. When I'm home, and plug the laptop into my home network, I
> don't fire up the VPN. In other words, I'm not connected to the corporate
> network when at home. I'm simply plugged into my home network.
>
> I did notice one other thing today. I also cannot map a drive through
> Windows Explorer using just the machine name as before. With Win 2k, I could
> just select Tools, Map Network Drive, then enter the path, such as
> \\DesktopName\SharedFolderName, then click on "Connect using a different user
> name", enter my user name and password for the XP administrator account, and
> the drive would map with no problems. Now, with 2k3 when I do that, I get
> the error : "The drive could not be mapped because no network was found."
> Again, if I use the IP address of the XP box, it maps fine. Also, I can't
> map to one of the shared printers on the XP box without using the IP address.
> All of these mappings worked fine with 2k Server using the machine name.
>
> I'm just now wondering if this has anything to do with my company now using
> Active Directory. In any case, there just HAS to be a way to get this to
> work without hardcoding IP addresses.
>
> Thanks again,
> John
.
- Follow-Ups:
- Re: NET USE in 2k3
- From: John Schneider
- Re: NET USE in 2k3
- Prev by Date: Windows Server 2003 VPN Configuration for Use with a WatchGuard X1000 Firewall??
- Next by Date: PCs don't see each other through dsl router
- Previous by thread: Windows Server 2003 VPN Configuration for Use with a WatchGuard X1000 Firewall??
- Next by thread: Re: NET USE in 2k3
- Index(es):
Relevant Pages
|
|
