Re: mapping woe's..........
From: chris@nospam.comDate: 01/30/02
- Previous message: chris@nospam.com: "Re: problems with autoadminlogon."
- In reply to: Bigmellow: "mapping woe's.........."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: chris@nospam.com Date: Tue, 29 Jan 2002 21:33:56 -0800
On 29 Jan 2002 19:53:17 -0800, wood@houston.rr.com (Bigmellow) wrote:
>Hey guys...... a little help here and hopefully you seen this issue
>before.
>
>I get the following messages when I try to map network drives from a
>NT 4.0 workstation to a shared W2K server shared folder.
>
>system error 67: The network name cannot be found
NT machine couldn't find the W2K machine.
>'<UNC path>' is an invalid current directory path. UNC paths are not
>supported.
>Defaulting to Windows directory
When you run a program such as \\server\share\program, NT will
complain that it can't set the default directory to the UNC path.
Usually you can ignore this error, unless the program needs to access
the default directory.
>I'm from the Linux/Unix world......... so any clarification would be
>appreciated... or help lol.
- Next message: Dale Brewe: "Re: HELP!!!! Rebooting Win2K DC causes trust relationships to go away!!!!"
- Previous message: chris@nospam.com: "Re: problems with autoadminlogon."
- In reply to: Bigmellow: "mapping woe's.........."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]