Ghost Solution Suite
Updated: 22 May 2010 | 1 comment
I'm running a Windows 2003 server HP-7782 nics, no firewalls, it's not on a domain just local network. I have the Standard Ghost Tools installed with the 3com Services. The 3com PXE boot works fine, the client machines boot to the menu I select my option for imaging, ghost loads but is unable to contact the server. GhostCast Server & PXE Boot Server are the same server (192.168.52.1). I receive the Ghost Code 19901. Everything is connected to a NetGear GSM 7248 switch which is totally open nothing is being blocked or forwarded.
Ran netstat - a -n -o and received the following:
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:53 0.0.0.0:0 LISTENING 1140
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 696
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING 1140
TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING 452
TCP 0.0.0.0:1029 0.0.0.0:0 LISTENING 1364
TCP 0.0.0.0:1155 0.0.0.0:0 LISTENING 3828
TCP 192.168.52.1:139 0.0.0.0:0 LISTENING 4
UDP 0.0.0.0:69 *:* 1060
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 452
UDP 0.0.0.0:1026 *:* 1140
UDP 0.0.0.0:1053 *:* 756
UDP 0.0.0.0:1154 *:* 3828
UDP 0.0.0.0:4500 *:* 452
UDP 0.0.0.0:6666 *:* 3828
UDP 127.0.0.1:53 *:* 1140
UDP 127.0.0.1:1025 *:* 1140
UDP 192.168.52.1:53 *:* 1140
UDP 192.168.52.1:67 *:* 1364
UDP 192.168.52.1:68 *:* 1364
UDP 192.168.52.1:137 *:* 4
UDP 192.168.52.1:138 *:* 4
UDP 192.168.52.1:2535 *:* 1364
UDP 192.168.52.1:4011 *:* 1040
TCP 0.0.0.0:53 0.0.0.0:0 LISTENING 1140
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 696
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING 1140
TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING 452
TCP 0.0.0.0:1029 0.0.0.0:0 LISTENING 1364
TCP 0.0.0.0:1155 0.0.0.0:0 LISTENING 3828
TCP 192.168.52.1:139 0.0.0.0:0 LISTENING 4
UDP 0.0.0.0:69 *:* 1060
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 452
UDP 0.0.0.0:1026 *:* 1140
UDP 0.0.0.0:1053 *:* 756
UDP 0.0.0.0:1154 *:* 3828
UDP 0.0.0.0:4500 *:* 452
UDP 0.0.0.0:6666 *:* 3828
UDP 127.0.0.1:53 *:* 1140
UDP 127.0.0.1:1025 *:* 1140
UDP 192.168.52.1:53 *:* 1140
UDP 192.168.52.1:67 *:* 1364
UDP 192.168.52.1:68 *:* 1364
UDP 192.168.52.1:137 *:* 4
UDP 192.168.52.1:138 *:* 4
UDP 192.168.52.1:2535 *:* 1364
UDP 192.168.52.1:4011 *:* 1040
Is there anyway to get the 6666 and other Ghost ports to listen, like force them to listen? Or maybe help me figure out when GhostCast server is not listening.
Thanks!
Forgot to add scan that was done as well:
Starting Nmap 4.62 ( http://nmap.org ) at 2008-05-21 15:43 Eastern Standard Time
Initiating ARP Ping Scan at 15:43
Scanning 192.168.52.1 [1 port]
Completed ARP Ping Scan at 15:43, 0.07s elapsed (1 total hosts)
Initiating SYN Stealth Scan at 15:43
Scanning 192.168.52.1 [1715 ports]
Discovered open port 53/tcp on 192.168.52.1
Discovered open port 1029/tcp on 192.168.52.1
Discovered open port 445/tcp on 192.168.52.1
Discovered open port 139/tcp on 192.168.52.1
Discovered open port 1155/tcp on 192.168.52.1
Discovered open port 1027/tcp on 192.168.52.1
Discovered open port 135/tcp on 192.168.52.1
Completed SYN Stealth Scan at 15:43, 1.48s elapsed (1715 total ports)
Host 192.168.52.1 appears to be up ... good.
Interesting ports on 192.168.52.1:
Not shown: 1708 closed ports
PORT STATE SERVICE
53/tcp open domain
135/tcp open msrpc
139/tcp open netbios-ssn
445/tcp open microsoft-ds
1027/tcp open IIS
1029/tcp open ms-lsa
1155/tcp open nfa
MAC Address: 00:14:C2:64:70:AB (Hewlett Packard)
Initiating ARP Ping Scan at 15:43
Scanning 192.168.52.1 [1 port]
Completed ARP Ping Scan at 15:43, 0.07s elapsed (1 total hosts)
Initiating SYN Stealth Scan at 15:43
Scanning 192.168.52.1 [1715 ports]
Discovered open port 53/tcp on 192.168.52.1
Discovered open port 1029/tcp on 192.168.52.1
Discovered open port 445/tcp on 192.168.52.1
Discovered open port 139/tcp on 192.168.52.1
Discovered open port 1155/tcp on 192.168.52.1
Discovered open port 1027/tcp on 192.168.52.1
Discovered open port 135/tcp on 192.168.52.1
Completed SYN Stealth Scan at 15:43, 1.48s elapsed (1715 total ports)
Host 192.168.52.1 appears to be up ... good.
Interesting ports on 192.168.52.1:
Not shown: 1708 closed ports
PORT STATE SERVICE
53/tcp open domain
135/tcp open msrpc
139/tcp open netbios-ssn
445/tcp open microsoft-ds
1027/tcp open IIS
1029/tcp open ms-lsa
1155/tcp open nfa
MAC Address: 00:14:C2:64:70:AB (Hewlett Packard)
Message Edited by gremster on 05-21-2008 01:12 PM
Discussion Filed Under:
Comments
I'm not exactly sure, some more details might be useful. But lemme give it a try.
First, DHCP, PXE, and TFTP are working it seems like. Your client gets an IP. It gets the PXE boot menu listing. You select something (a Ghost client floppy disk image) off that list, and it transfers to your client PC correctly. The transferred floppy image boots up to DOS (PC-DOS or MS-DOS, whichever you're using.) It loads up a NIC driver. It then starts running the Ghost.exe client. You select the "Ghostcas" and "Unicast". At the bottom of the Ghost window, it'll say Initializing IP (something like that, it flashes by a bit quickly for me.) It then says "Local IP address: #####". Ghost should also show you a little window that lets you enter in the Ghostcast Session Name.
So when you say "unable to contact the server", are you referring to this stage? You enter a GCS session name, but the client can't find it? At the bottom of the Ghost window it says "Attempting to contact <###>"" but it never succeeds, and gives you an error "Unable to establish contact with session <###>"?
As always, the first thing I'd check is the network on the client. Did the DOS level NIC driver load correctly? When booting up, hit the F8 key and it'll step through the boot process a piece at a time. If you see an error msg, that'll be where it comes up. If the NIC driver loads correctly, then go through the Ghost client until you get to the point about Initializing packet driver/IP address thing. It should show you what the client IP is. Goto another system and just ping that IP address. It should respond. At least that way, you know systems can reach the client (even if not the other way around.) If it doesn't respond, then you know your client has no IP and you can start from there.
What NIC driver was used for the Ghost boot floppy? Try the Universal/UNDI one. I dunno the HP-7782, but on my HP dc7800, the NIC driver I used to create my Ghost boot floppy came from Intel. The one from HP and the one from Symantec worked poorly or not at all. So try downloading the latest DOS NIC driver for whatever is on the HP-7782 and recreate a boot-floppy using that. To me, sounds like the problem lies in your boot floppy - since you booted, got PXE, got TFTP...up to that is fine.
Make sure your Windows Server has the port opened on its firewall for the GCS. I have a Program Exception on my W2K3 server for Ghostcast Server at C:\Program Files\Symantec\Ghost\GhostSrv.exe. I dunno what version of GSS you have, and I don't know if GCS changes depending on the GSS version, but you get the idea there.
Course, I dunno what 19901 is. It might be something completely different, and I'm sure Symantec folks will jump in too. If you have a Ghosterr.txt file, you might post that as well. I can't decipher it (would love to learn how though!) but again, the Symantec folks can :)
Good luck,
PH
Would you like to reply?
Login or Register to post your comment.