Ghost boot disk for Dell Latitude C610

Question

Hi All - I am trying to make a ghost boot disk for a Dell Latitude C610 with a Broadcom NetXtreme 57xx Gigabit Controller.  I have tried the 'Ultimate TCP/IP Network Bootdisk' and 'Bart's network bootdisk' But, each one and every time I get to the portion of the process where it maps the network drive i get the error message 'Error 58: The network has responded incorrectly.'  So, I never have been able to map a network drive.   Any thoughts? Suggestions?

Rijko · Answer

hi,

i have a few thoughts :

if you boot using the "Ultimate TCP/IP Network Bootdisk", are you booting light ?

As in... no mouse drivers, enhanced redirectors, cdrom support etc ? Just Network drivers. No logon script.

After succesful boot, on the command prompt, use the "net use" command and see if you are able to map correctly. Maybe you made a typo in the batchfile, maybe there is another problem. At least the command prompt should show you more details on the error when mapping drives.

This disk has worked for me. But since i use a boot-cd i have enough room for the ghost exe so i do not need mapped drives. The packet driver works for me.

Let me know how it works out for you, i may be able to help.

Message Edited by Rijko on 05-24-2005 05:58 PM

collegeman · Answer

Tried all of that and still get the same error message as I stated above??  One thing that we noticed is that our network group is using a NETAPP filer for the server in which we house our Ghost images.  We can map a drive to ANY Windows computer but not this filer.    Any Thoughts?

Rijko · Answer

ok, i am not familiar with Netapp products. I looked at the website, googled a bit and the filer products are regular NAS/SAN products. They use a special OS but allow drive mappings, so my best bet would be a configuration problem on the filer box.   Like Linux, that needs a Samba driver to be able to share network drives. Maybe it is missing a deamon, plugin, protocol... dunno what they call it with this filer OS. A network monitor/sniffer may be helpful. Maybe the network group has one ? A pc can also be used for this purpose - the captured data of a failed mapping attempt should help in determining what the 'invalid response' is. Maybe a firewall blocking ports ?   If nobody can map a drive to the Netapp filer and the ghostcast server is not running on that box - how do you handle the Ghosting process now ? Does the Ghostcast server run on the server the Netapp filer is physically connected to ?   BTW, i would not have a client pc ask the Ghostcast server for an image if it needs to come from another location on the network. That would mean the ghostcast server fulls the image over the network and then sends it to the client - that's 2 images worth of traffic on the network while only 1 needs to be sent.   I think Symantec has a problem with this setup too. I read somewhere on their site that this setup is not advised, supported, or possible. Don't know which.. too bad i cannot find the article right now.   For testing purposes i would setup a simple environment. Like a pc/server running Ghostcast server, and no firewalls or other possible troublemakers. 1 or 2 client pc's and set the whole lot behind a hub - seperate from the business network so no problems can be created while testing. As soon as you get things working, try to work towards the solution by placing the ghostcast server/pc behind one of the switches on your network. Preferrably behind the same switch your current ghostcast server is running on. If this works, you are sure the problem can be found in the current ghostcast server and/or Netapp filer setup.

Rijko · Answer

Symantec has an article on that error 58. It reads :

Error 58 "The network has responded incorrectly"

Situation:
When trying to connect to a share on a network storage appliance after booting your computer with a network boot floppy disk, you see the message "The network has responded incorrectly."

Solution:
If this problem occurs, rebuild your Microsoft® TCP/IP Boot disk and place the domain name in the Workgroup box instead of the Domain box. This will cause the computer to authenticate to the network storage appliance rather than to the domain controller.

If the problem persists, you can add an entry to the Lmhosts file on the boot disk. The purpose of this entry is to cause the computer to send the authentication credentials to the network storage device instead of to a domain controller. The entry should be similar to:

IP #PRE #DOM:

Where is the name of the appliance and is the name of the workgroup or domain to which you are trying to authenticate.

Maybe this is of use.

Rijko · Answer

haha this keeps me busy..

the workgroup/domain stuff can be tested on the command prompt of every NT,W2k,XP OS using the command "NET USE * \\server\share /user:domainname\username password"

If that does not work i guess the Netapp is not configured (properly) for file sharing.

Since that is kinda its purpose in life, i wonder how the box is used....

I would suggest to create a testing setup... since you now seem to have 2 separate problems. Your Ghost bootdisk may be okay but with the drive mapping problem to the Netapp box you probably have no way to confirm failure nor success...

Message Edited by Rijko on 05-26-2005 08:16 PM

Networking, Internet, & Bluetooth

Ghost boot disk for Dell Latitude C610

Was this post helpful?