[Unattended] Unattended Dealing with IPs (fwd)
Hi Pat, We have internal DNS servers which are delivered to clients via the DHCP server. Any client looking for an IP via DHCP will recieve these DNS server server IPs. I simply added an entry in our zone files for the LAN and refreshed the DNS tables. From there I could type: \\dvrinst\install and gain access to the share. I tried both with a username and password set, and without. I tried to add an entry into the /etc/hosts file as the RH9 distribution I had on the machine hosting the Win2k install and unattended files did not have an lmhost/s file. I did try to restart the network services on the machine prior to testing in Windows, but either wayit didn't work. I assumed this had something to do with the machine advertising itself to the WINS server which I didn't really have the time to wait aroudn for, hence the reason I went with the entry in the DNS server. THe only thing I can think of to try now would be to forcably create and lmhost/s file and restart the network services on the machine, or to try with a Windows machine. Any assistance would be great. Cheers, Gareth PS. I am really happy with the level of support from this community. I did fear it would be another linux RTFM list, but to my joy it was the exact opposite. Congrats!! :-) On 12 Dec 2003, Patrick J. LoPresti wrote: Gareth Budge [EMAIL PROTECTED] writes: 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. Which suggestion did you try? Can you please advise me on what I can do to correct this? You are the first person to report this problem, so I need more details. What did you do, exactly, to get \\dvrinst\install to work from Windows? - 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=1278alloc_id=3371op=click ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
RE: [Unattended] Unattended Dealing with IPs
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=1278alloc_id=3371op=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=1278alloc_id=3371op=click ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Unattended Dealing with IPs
Gareth Budge [EMAIL PROTECTED] writes: 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. Which suggestion did you try? Can you please advise me on what I can do to correct this? You are the first person to report this problem, so I need more details. What did you do, exactly, to get \\dvrinst\install to work from Windows? - 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=1278alloc_id=3371op=click ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
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=1278alloc_id=3371op=click ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
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=1278alloc_id=3371op=click ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
