Hello, this is maybe slightly offtopic, but I suppose concerns also the MSCLIENT stuff.
I wasn't able to move the server share of unattended from Windows2000 Server to Windows server 2003. The 'net start' command was successful, but "net use z: \\server\share" couldn't connect to the share and gave me an error that my password was incorrect and asked to reenter, which also doidn't help. Of course I double-doublechecked the correctness and made the share fully accessible to everyone etcetc. Another strange thing was that if I put whatever nonexisting share name for connecting, the error was the same, so MSCLIENT couldn't give appropriate error about share not existing. With Windows2000 server it could. Has anybody used a share on Win2003 server? Have you had any problems? best regards, Ain > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Gareth Budge > Sent: Friday, December 12, 2003 7:35 AM > To: Patrick J. LoPresti > Cc: Unattended Mailing List > Subject: RE: [Unattended] Unattended Dealing with IPs > > > Hello, > > Okay well I have tried the suggestion and I am able to access the > share via Windows doing \\dvrinst\install however it comes back > with the same error when doing it from the bootdisc image. > > Can you please advise me on what I can do to correct this? > > > Thanks. > > Gareth > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf > Of Patrick > J. LoPresti > Sent: Friday, 12 December 2003 1:36 PM > To: Gareth Budge > Cc: Unattended Mailing List > Subject: Re: [Unattended] Unattended Dealing with IPs > > > "Gareth Budge" <[EMAIL PROTECTED]> writes: > > > \\192.168.0.50\install > > The boot disk uses the MSCLIENT networking stack, which is pretty old. > It very possibly does not support IP addresses in the hostname field. > > You could try populating \net\lmhosts with a line like this: > > 192.168.0.50 foobar > > Then you should be able to use \\foobar\install as the share name. > > But what you really want to do is get name resolution working > properly. I believe MSCLIENT can use broadcast or a WINS server > obtained via DHCP... > > - Pat > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign > up for IBM's > Free Linux Tutorials. Learn everything from the bash shell > to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > unattended-info mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/unattended-info > ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
