Re: connect to \\server computer at login

From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 07/27/04


Date: Mon, 26 Jul 2004 20:11:24 -0700

Why don't you just create another local user on the Server with the same
credentials as the local user on the XP machine so that NET USE is
irrelevant between the two machines? Without running a domain controller to
synchronize user accounts between two machines, this method is the next-best
thing.

In other words, if you publicize the use of another user's credentials, via
NET USE, to access a share on the Server but does not control the use of
this script, it is the same as allowing "Everyone" access.

To access remote resources, you do not need to assign a network drive letter
at all.

NET USE \\server\share password /user:admin /persistent:yes

Then, you can access files via \\server\share\blahblahblah.

Mapping a drive letter only allows you to access files via Z:\blahblahblah

-- 
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Steve Waha" <SW@Mail.SpamNot.com> wrote in message
news:10gb8g8spo4qr03@corp.supernews.com...
Is there a way to write a script to run after login that will connect to a
computer using the computer name (i.e. \\server ) instead of having to
assign a network drive to a share on the computer?
I have a script that maps a drive letter to a network share, but it fails on
login because it can't find the network path.
   net use z: \\server\share password /user:admin /persistent:yes
After I am logged in I can manually login to that computer like this
start > run > \\server
authentication window pops up
I enter the username and password, and then I am connected.
I can do this but the office girl can't remember to do this, so I want to
automate it with a script that runs on start up
both computers are stand alone (no domain controller). The server runs
win2k, the client runs xp pro.
thanks for your help
-steve waha


Relevant Pages

  • Performance optimization vs satisficing (was Language Oriented Programming)
    ... >machines that were too small. ... Microsoft has been a leading offender here. ... >arcane issue for server engines. ... magnitude slower, yes, I recall working on a 200mb database, trying to ...
    (comp.object)
  • Re: network slows down after SP2 install
    ... the machines updated from W2K still open and read the ... Locate the "Microsoft network server: ... Install SP2 for WIN XP and latest service pack for Office 2003 on ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: network slows down after SP2 install
    ... These machines cannot even run the program locally being disconnected from the server with a local copy of the database. ... Install SP2 for WIN XP and latest service pack for Office 2003 on ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Should I install Certificate Authority to solve these problems ?
    ... You can use IPsec with or without certs from your PKI. ... negotiations to your AD machines or those trusting the ... > In the item 1 below, the tool in use is a HP server management tool (type ... >>> Management is pushing to get Certificate Authority ...
    (microsoft.public.win2000.security)
  • Re: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
    ... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ...
    (microsoft.public.windows.server.sbs)