I have used this batch file format in the past to connect to network
drives. Even people who are under two different server clients, ie.
Novell and Windows Active Directory (AD).

For some reason this time it is not authenticating the user name.

Just some background so you might be able to understand what the
problem is..
User in different location and a Novell client but has access to AD.
For performance, the application was placed at the same location but on
an AD server.
The "aa/" d user domain may be different then the server. The IP
addresses for the two locations start with different #'s. Does that
matter?
Also the users are part of a group and have a generic password set for
the whole list of users.

net use y: /d
net use y: \\XXX.XX.XXX.XX\Folder /user:aa\dez1 P@ssword

any insight would be great.
thanks

Re: connect to network drive by dthomas

dthomas
Fri Aug 18 17:04:39 CDT 2006


Matt wrote:
> I have used this batch file format in the past to connect to network
> drives. Even people who are under two different server clients, ie.
> Novell and Windows Active Directory (AD).
>
> For some reason this time it is not authenticating the user name.
>
> Just some background so you might be able to understand what the
> problem is..
> User in different location and a Novell client but has access to AD.
> For performance, the application was placed at the same location but on
> an AD server.
> The "aa/" d user domain may be different then the server. The IP
> addresses for the two locations start with different #'s. Does that
> matter?
> Also the users are part of a group and have a generic password set for
> the whole list of users.
>
> net use y: /d
> net use y: \\XXX.XX.XXX.XX\Folder /user:aa\dez1 P@ssword
>
> any insight would be great.
> thanks

I use this quite often in a number of situations with two differences.
I don't know if the differences are signficant or not.

I use:
net use y: \\XXX.XXX.XXX.XXX\Folder <password> /USER:user@domain

I.E. The order of argumnts is different and the form of the username
is different.

The different IP addresses should not be a problem as long as you have
routing between the two machines and there is no firewall in the way.

Whenever possible I use the machine name instead of the address. If
there is no name resolution between them I sometimes will make a hosts
file entry (if it's something I think I'll be doing a number of times).

David E. Thomas
Rivercrest Technologies, Inc.