Ghost Solution Suite

Hello and thank you in advance for any insight into my issue.

i am running ghost solution suite 2.5.1

i have a hp 8200 running this software

ip address (static) 192.168.1.1

subnet 255.255.254.0

default gateway 192.168.1.1

i have the server hooked to a dlink 8 port switch (dgs-2208)

and the client computer is also hooked to this switch (simple network)

i have created a boot usb with the ghost boot wizard in both win pe inviroment and pre dos os

winPE : in winpe i have a connection issue witht he server error 10030

i have opened all udp ports in windows fire wall(1345,1346,1347,6666,7777)

and i still cannot establish a connection with the server

i have followed many guides on this site and nothing has worked

predos os :

ghoscast is greyed out

network boot and pxe settings in bios is enabled

thanks

brandon

in the PE, have you tried turning the firewall off?

wpeutil disablefirewall

you probably already saw this too:

http://service1.symantec.com/SUPPORT/on-technology.nsf/293a5302ae81e39288256ebb0049cfe7/5998ce53fedf331c8825747f00603353?OpenDocument

Does the machine say "CONNECTED" in the console?

yes i have followed those steps and have not resolved the issue.

are we talking about the ghostcast server console , if so no usually i see an ip address in the box what is wierd is i can connect using a cdrom drive but i cannot use the usb drive that i have made ... the only thing i can think of is a driver issue but i have installed the lates intel marvel gigabit extreme 1 and 2 drivers but still no luck i have tested cables and switched out the switch but i cannot connect to a ghost cast session using the usb drive.

to disable firewall in winpe invirement do i type wpeutil disablefirewall in the CMD like window?

if so i get an error the command failed with status 0x800706d9

Try changing the subnet mask to 255.255.255.0

Error 10030 is frequently caused by using the wrong NIC drivers for your WinPE setup. You need to add Vista 32 bit drivers using Ghost Boot Wizard as WinPE is based on the Vista kernel.

The following articles may be of help:

https://www-secure.symantec.com/connect/articles/do-i-have-correct-driver-winpe

http://www.symantec.com/business/support/index?page=content&id=TECH110134

Ok thanks EdT for confirming my Issue it looks like as i suspected that i have a nic driver issue my nic information based on hp site >http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?prodSeriesId=4098436&objectID=c02030590

says i have

• Intel 82578 GbE Network Connection (integrated)
• Intel Gigabit CT Desktop NIC Card
• Broadcom NetXtreme GbE Ethernet Plus NIC (PCIe x1)

Thank you EdT for the helpful links and it does seem like i have a nic driver issue

my nic card information is :

• Intel 82578 GbE Network Connection (integrated)
• Intel Gigabit CT Desktop NIC Card
• Broadcom NetXtreme GbE Ethernet Plus NIC (PCIe x1)

i have also made a driver image with the drivers on this link https://www-secure.symantec.com/connect/downloads/latest-vista-version-drivers-use-gss with no success

OK, it looks like a bit more detective work is required, and we need to check the exact device ID of the network chipset in your machine. Can I assume that you have at least one other machine with a working windows operating system on it?  If so, go to this article: https://www-secure.symantec.com/connect/articles/readyutility-assist-identifying-plug-and-play-drivers

and run the utility described therein. It will create a text file containing a complete listing of all plug and play devices in your computer, including device ID and details of the driver INF files and drivers. This is a good starting point whenever working on builds or driver sets.

Once you have the device ID of your NIC, you can determine whether your chosen driver is at least compatible with your device, as the INF file of the NIC driver set should contain the Device ID of the NIC in your system. That's basically how Plug and Play works - it reads the device ID and searches through the INF file library on your machine looking for a match. The INF file then contains information about the driver files required to mount the NIC and any associated registry keys. This also gives you a cross check on whether you have all the required files in the driver set. As a minimum, a driver set needs to include an INF CAT and SYS file although it is not uncommon to find one or more DLL files.

I'm pretty sure you are already aware of this, but I will stress that WinPE V2 as provided with Ghost needs you to use Vista 32 bit drivers regardless of what operating system you plan to image. If using Ghost Boot Wizard, you need to both add, then select, any additional drivers. It can be beneficial to remove any unused drivers in GBW in case there are any older versions of the drivers you are trying to add, which may not correctly support your specific chipset.

thank you EdT ,using the vbs script i was able to find the driver Id.  i had to use an older driver because the 16.3 driver was not working so i rolled back to 16.0 and it worked i went ahead and used this on the hp 8200 since we are phasing out the 8100 but thank you again for providing me the correct tools and knowledge

Glad to be of service!

sorry to bug again about this issue . i was able to establis one connection with the HP_8200 it timed out half way and quit. when i run an ipconfig everything looks good but i cannot reestablish a connection now. im a bit confused on why this is happening?

A valid IP config just confirms that the basic network connection exists between your machine and the DHCP server.  If you are trying to deploy using Multicast, then you need to have IGMP snooping enabled on your switch, otherwise the imaging process tends to fails after 3-4 minutes. You haven't mentioned what server platform you are using for Ghost, so this would be good to know.

What you could try is "pulling" an image rather than pushing it down. If you can create a network connection with a server share, you can run Ghost32.exe from the share, then use it to pull down an image from the share and onto your target.

With any network configuration, there are many points of potential failure, and it's difficult to try and find the underlying cause of your problem.  Do not overlook the possibility of something basic such as a dodgy network cable or a dodgy port on the switch - it would not be the first time that users have agonised over a presumed software failure when the actual cause was a hardware problem.

i am running the ghost cast server on a HP_8200

it is connected to a simple network

ip address: 192.168.1.1

subnet: 255.255.255.0

i have the server hooked to a dlink 8 port switch (dgs-2208).....more a hub then a switch (dum)

tested the cables between server and client ....(tested good)

i have tried to restore and create an image

all ip address are static!

What server operating system are you using? What network protocols are installed?

No server os i am running the ghost solution suite 2.5 on a windows 7 enterprise on a hp 8200 compaq computer. with the generic ip proticals installed.

I have a feeling in the back of my mind that you need Netbios enabled, which is no longer the default for Win 7.

I am able to boot off of a cd and connect to the session with my current configuration with no problem.

But i am trying to get away from using the cd for the connection to the session that is why i am going to usb.

is it possible that there might be a compatability issue with the flash drive,  i have tried a couple with no success accept for the last session i connected and it timed out half way during the unicast

So you are booting a WinPE CD successfully, but not a WinPE USB key?

My own experience is that not all flash drives are created equal, and the cheap ones especially may have some fast flash memory serving the first 10% and cheap sub standard memory for the rest.  I have also seen compatibility issues between some machines and a standard WinPE USB boot that works on all other hardware. This appears to be bios related in many cases.  Generally, I have found that USB hard disks boot more reliably than USB sticks and this could be a way to test your methodology before trying to find a suitable USB stick for your hardware.  Hopefully it would serve to reduce the number of variables in your current equation and establish whether there is also a driver/network problem affecting your setup.

I prefer to image directly from a USB hard disk as it's a lot faster than network imaging in my experience and decent capacity disks are not much more cost-wise than a largish USB stick.