Error 10030 - HELP!
Leif_G
May 15th, 2007
Last year I had Ghost 8 working fine for me. This summer we've gone to version 11. We have 3 techs at 3 different campus' and so far I'm the only one that's running into problems, so I don't think it's anything related to our network setup.
The only thing that's changed since last summer was that my Ghost server machine had to be rebuilt, and we've gone to version 11.
At thsi point I've installed both Ghost 8 and 11 on numerous machines, with a variety of configurations (on the domain, off the domain, working through a switch, working through a hub,etc).
I always get the same error when trying to Ghost Cast:
"Unable to establish connection with session ______. Check that the Ghost Casting server application is ready to accept clients (10030)"
Both client and server host machines have received IP addresses from DHCP.
There are no firewalls or routers in between. XP firewall is disabled on the server.
Both computers are on the same subnet working off of the same hub.
Both computers have PXE enabled and are set in BIOS to allow a network boot.
When I try to set up a Ghost Cast session using the 'automatic' Discovery Method, the first attempt fails as per usual, but I notice on the second attempt that the client machine was able to identify the server by IP address and has filled the IP address in by itself in the 'Discovery Method' area, switching it to manual.
So the client machine is seeing the session and server, but can't connect.
I've tried logging the attempted Ghost Cast session and the server seems ready to receive, but never seems to hear from the client.
These result are constant regardless of any changes I make in setup or configuration or my equipment or boot discs.
Anyone have any ideas or suggestions?
Thanks.
Leif
PS - I wanted to add that I have tried using the exact same version 8 boot discs with MS-DOS that I was using last year on the exact same type/model of computer. Last year they worked perfectly fine for me. This year... nothing. Same error message.
I've also tried setting a data transfer rate restriction to 500mb/min - no difference.
Message Edited by Leif_G on 05-15-200703:04 PM
Filed under: Ghost Solution Suite, Endpoint Management and Virtualization
Message Edited by Krish Jayaratne on 05-16-200709:54 PM
Message Edited by Leif_G on 05-16-200703:37 PM
I keep getting this error also and of couse I had no troubles with GSS 1.1. So far it only happens when I try to restore a image that resides on the ghost server. Haven't tried taking one and saving it to the server. The client will get a DHCP number. It will pass some certificate info as far as I can tell (screen goes by fast). Ghost starts and states that it is trying to establish a connection. Never connects to the Cast server.Then it exits ,pc reboots, goes through the certificate screens again ( much slower this time). Then just sits the sending out requests and the ghost server keeps sending Ackknowledgements until I cancel at the client. I have tried everyhting I can thing of for 2 days. What am I missing, there are no firewalls and nothing has changed on my network except the version of GSS and the clients.
Here is a ghost error log:
Date : Thu May 24 14:07:57 2007
Error Number: (10030)
Message: Unable to establish contact with session <LABBKPPUSH2>.
Check that the GhostCasting Server application is ready
to accept clients!
Version: 11.0.1.1533 (Apr 19 2007, Build=1533)
OS Version: DOS v7.10
Command line arguments: -clone,dst=1,mode=restore,src=@MCLABBKPpush2 -batch -sgb -jm=U -sgt
Active Switches :
AutoName
PathName :
DumpFile :
DumpPos : 0
FlagImplode : 0
FlagExplode : 0
CloneSrc : @MCLABBKPPUSH2
BatchPartSrc : 0
BatchPartMSrc :
CloneDst : 1
BatchPartDst : 0
Operation Details :
Total size.........0
MB copied..........0
MB remaining.......0
Percent complete...0%
Speed..............0 MB/min
Time elapsed.......0:00
Time remaining.....0:00
Program Call Stack
AbortLog
Generic_Abort
CheckCloneSwitches
ProcessArgumentsToPass
sub_main
main
Call Stack
0x00397a4c
0x0009cd91
0x0009c5cc
0x0009bca7
0x0009d8ae
0x00028b3a
0x0002c1e9
0x00030c94
0x00030e15
0x00004ad8
0x00003f2f
0x003a0c78
End Call Stack
Start heap available: 459276288
Cur heap available: 459079680
Total Memory: 468647936
Allocated
1024 DpmiDjgpp.cpp:56
33504 ghost.cpp:1396
48 DiskDriveAccessExInt13.cpp:139
528 IdeDmaServerPci.cpp:127
528 IdeDmaServerPci.cpp:127
Free
64 GetDriveType.cpp:111
512 DiskDriveAccessInt13.cpp:184
32768 MsdosFile.cpp:368
Fat details:
NTFS details:
----------------
NTFS Global Flags:
----------------
contiguousWrite=1 forceDiskClusterMapping=0
inhibitCHKDSK=1 ignoreBadLog=0 ignoreCHKDSKBit=0
enable_cache=0 xfrbuflen=0
last_attr_type = 0
loadExact = 0
----------------
Disk Info :
remote.............0
drive..............0
sectorsUsedCount.......0
estimatedUsedCount.....0
numPartitions..............0
Version............0
# Ord Boot Id Ext First Num Last Used NTFS
Disk Info :
remote.............0
drive..............0
sectorsUsedCount.......0
estimatedUsedCount.....0
numPartitions..............0
Version............0
# Ord Boot Id Ext First Num Last Used NTFS
Fixed Drives
Drive 128 Maxtor 6E040L0 E131LFLN
Int 13h
Total Sectors 16450560
Bytes per Sector 512
MB 8032
Cylinders 1024
Heads 255
Sectors per Track 63
Successful IO Count 0
Extended Int 13h
Total Sectors 80291135
Bytes per Sector 512
MB 39204
Successful IO Count 0
IDE using PIO
Total Sectors 80293248
Bytes per Sector 512
MB 39205
Cylinders 16383
Heads 16
Sectors per Track 63
Successful IO Count 0
IDE using UDMA (Active)
Total Sectors 80293248
Bytes per Sector 512
MB 39205
Cylinders 16383
Heads 16
Sectors per Track 63
Successful IO Count 45
Floppy Drives
Drive 0
Int 13h (Active)
Total Sectors 2880
Bytes per Sector 512
MB 1
Cylinders 80
Heads 2
Sectors per Track 18
Successful IO Count 1
Remote Drives
AsyncIo : 0
ConvMemoryAllocationFactoryDpmi diagnostic...
=============================================
Conventional Memory
Initial Conventional Memory Size = 390464
Current Conventional Memory Size = 255568
Allocated
1024 DpmiDjgpp.cpp:56
33504 ghost.cpp:1396
48 DiskDriveAccessExInt13.cpp:139
528 IdeDmaServerPci.cpp:127
528 IdeDmaServerPci.cpp:127
Free
64 GetDriveType.cpp:111
512 DiskDriveAccessInt13.cpp:184
32768 MsdosFile.cpp:368
DiskManager diagnostic...
=========================
Fixed Drives
Drive 128 Maxtor 6E040L0 E131LFLN
Int 13h
Total Sectors 16450560
Bytes per Sector 512
MB 8032
Cylinders 1024
Heads 255
Sectors per Track 63
Successful IO Count 0
Extended Int 13h
Total Sectors 80291135
Bytes per Sector 512
MB 39204
Successful IO Count 0
IDE using PIO
Total Sectors 80293248
Bytes per Sector 512
MB 39205
Cylinders 16383
Heads 16
Sectors per Track 63
Successful IO Count 0
IDE using UDMA (Active)
Total Sectors 80293248
Bytes per Sector 512
MB 39205
Cylinders 16383
Heads 16
Sectors per Track 63
Successful IO Count 45
Floppy Drives
Drive 0
Int 13h (Active)
Total Sectors 2880
Bytes per Sector 512
MB 1
Cylinders 80
Heads 2
Sectors per Track 18
Successful IO Count 1
The following devices do not use an IRQ:
(0x00, 0x00, 0x00): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: Host/PCI
Vendor: 0x1106, Device: 0x0204
(0x00, 0x00, 0x01): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: Host/PCI
Vendor: 0x1106, Device: 0x1204
(0x00, 0x00, 0x02): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: Host/PCI
Vendor: 0x1106, Device: 0x2204
(0x00, 0x00, 0x03): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: Host/PCI
Vendor: 0x1106, Device: 0x3204
(0x00, 0x00, 0x04): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: Host/PCI
Vendor: 0x1106, Device: 0x4204
(0x00, 0x00, 0x07): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: Host/PCI
Vendor: 0x1106, Device: 0x7204
(0x00, 0x01, 0x00): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: PCI/PCI
Vendor: 0x1106, Device: 0xb188, RoutePINS: 0x01, 0x02, 0x03, 0x05,
(0x00, 0x0f, 0x00): IRQ: 0xff, INT#: A, Link: 0x00
Class: Mass Storage, SubClass: IDE Controller
Vendor: 0x1106, Device: 0x0571
(0x00, 0x11, 0x00): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: PCI/ISA
Vendor: 0x1106, Device: 0x3227, RoutePINS: 0x01, 0x02, 0x03, 0x05,
(0x00, 0x18, 0x00): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: Host/PCI
Vendor: 0x1022, Device: 0x1100
(0x00, 0x18, 0x01): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: Host/PCI
Vendor: 0x1022, Device: 0x1101
(0x00, 0x18, 0x02): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: Host/PCI
Vendor: 0x1022, Device: 0x1102
(0x00, 0x18, 0x03): IRQ: 0x00, INT#: -, Link: 0x00
Class: Bridge, SubClass: Host/PCI
Vendor: 0x1022, Device: 0x1103
The following hard wire-ord devices share IRQ 10:
(0x00, 0x10, 0x00): IRQ: 0x0a, INT#: A, Link: 0x01
Class: Serial Bus, SubClass: USB UHCI
Vendor: 0x1106, Device: 0x3038, RoutePINS: 0x01, 0x02, 0x03, 0x05,
(0x00, 0x10, 0x01): IRQ: 0x0a, INT#: A, Link: 0x01
Class: Serial Bus, SubClass: USB UHCI
Vendor: 0x1106, Device: 0x3038, RoutePINS: 0x01, 0x02, 0x03, 0x05,
(0x01, 0x00, 0x00): IRQ: 0x0a, INT#: A, Link: 0x01
Class: Display, SubClass: VGA compatible
Vendor: 0x1106, Device: 0x3108, RoutePINS: 0x01, 0x02, 0x03, 0x05,
The following hard wire-ord devices share IRQ 5:
(0x00, 0x10, 0x02): IRQ: 0x05, INT#: B, Link: 0x02
Class: Serial Bus, SubClass: USB UHCI
Vendor: 0x1106, Device: 0x3038, RoutePINS: 0x01, 0x02, 0x03, 0x05,
(0x00, 0x10, 0x03): IRQ: 0x05, INT#: B, Link: 0x02
Class: Serial Bus, SubClass: USB UHCI
Vendor: 0x1106, Device: 0x3038, RoutePINS: 0x01, 0x02, 0x03, 0x05,
The following hard wire-ord devices share IRQ 11:
(0x00, 0x10, 0x04): IRQ: 0x0b, INT#: C, Link: 0x03
Class: Serial Bus, SubClass: USB EHCI
Vendor: 0x1106, Device: 0x3104, RoutePINS: 0x01, 0x02, 0x03, 0x05,
(0x00, 0x11, 0x05): IRQ: 0x0b, INT#: C, Link: 0x03
Class: Multimedia, SubClass: Audio
Vendor: 0x1106, Device: 0x3059, RoutePINS: 0x01, 0x02, 0x03, 0x05,
(0x00, 0x13, 0x00): IRQ: 0x0b, INT#: A, Link: 0x03
Class: Network, SubClass: Ethernet
Vendor: 0x10ec, Device: 0x8139, RoutePINS: 0x03, 0x05, 0x01, 0x02,
FilesystemManager diagnostic...
===============================
Volume 1
VolumePos: 1.2:
DriveLetter:
Description: 11.72GB Primary Disk 0 Offset 7.82GB 11.72GB Maxtor 6E040L0 E131LFLN
Type: fsfNtfsWindowsXP
Name:
Volume 2
VolumePos: 1.3:
DriveLetter:
Description: 18.74GB Primary Disk 0 Offset 19.54GB 18.74GB Maxtor 6E040L0 E131LFLN
Type: fsfNtfsWindowsXP
Name: IMAGE
FilesystemMounter diagnostic...
===============================
LfoFilesystemManager diagnostic...
==================================
Filesystem Index: 0
Filesystem Descriptor:
ID's:
ID Type: 2
ID: A:
DriveType: 2
No FilesystemInfo structure.
Filesystem has no VolumePtr
Filesystem Index: 1
Filesystem Descriptor:
ID's:
ID Type: 2
ID: C:
DriveType: 4
No FilesystemInfo structure.
Filesystem has no VolumePtr
Filesystem Index: 2
Filesystem Descriptor:
ID's:
ID Type: 1
ID: 1.1:
DriveType: 4
No FilesystemInfo structure.
Filesystem Index: 3
Filesystem Descriptor:
ID's:
ID Type: 1
ID: 1.2:
DriveType: 4
FilesystemInfo:
formatType: 8
volumeName:
Filesystem Index: 4
Filesystem Descriptor:
ID's:
ID Type: 1
ID: 1.3:
ID Type: 4
ID: IMAGE:
DriveType: 4
FilesystemInfo:
formatType: 8
volumeName: IMAGE
*********************************
'Geezwiz',
In your case, command line suggests that you use unicasting, so it should not be a multicast relate problem.
Did you get this in only one (or same model) of machines? There is a possibility that the new version of the network driver is not compatible with your network card. If that is the case, could you replace it with a older version of the driver?
Then you indicate that this only happens if the image is stored in the Console. Does it mean that if you copy the image to a network drive and run the same task, it is working? If that is the case, it is cannot be network driver related. You say that there is no firewall, but is there any antivirus products installed in the server?
Krish
Krish,
When I mean everything ,everything! I have tried unicast,multicast and direct broadcast, same issue. I thought at first it was the Realtek driver and did eveything I could with that. Then I tried another PC with a Nvidia Nic, same issue. So I gave up on the Nic being the culprit.
Let me clarify about where the image is stored. At first I had it stored on a seperate server from the ghost server (same issue) then I moved the image to the ghost server, same issue. If a patition image is stored on the PC in a second partition. The PC will ghost from the console with out any problems, so it seems to be only when the cast server needs to be used that ghost does not communicate with the cast server.
I have the antivirus disabled on the ghost server and the pc i'm troubleshooting on.
I am going to try to take a network trace today and i'll post those results.
Paul aka geezwhiz
Hi Paul,
Thanks for the details -
Everything points to something blocking only the GhostCast transmissions. A network trace would be great. If it is too big to post here, please let me know.
How do you connect the Server and the Client? Are they in the same hub or going through a switch? Is there any possibility of having a hardware firewall in between?
Krish
The client and server are on 2 seperate subnets, They are in a controlled Lab. They comunicate through a router and a switch. My Network setup has not changed except for the upgrade from GSS 1.1 to 2.0.1. I did not have the time on Friday for a trace, hopefully i can get one on tuesday.
How does the client communicate with cast server so it will start? What Port # ? Something had to change from v1.1 to v2.01 that my network is choking on?
Thanks
No, there were no major changes to the process. I cannot think of any reason why this is happening, just after the upgrade.
Basically it's port 6666 and 7777 that's required for the GhostCast server to establish the connection. After that it will use dynamic ports obtained from Windows. We have added more details in 2.0 manual (appendix L, page 569).
Is it possible to use the old GhostCast server in the same machine if you still have the install set of 1.1? Just to see actually this is a problem specific to 2.0?
I must correct myself, when i said nothing has changed I meant in my network. Originally i had 1.1 on a domain controller & like i mentioned before I had no problems. i upgraded the 1.1 to 2.0 and that's when bad things happened. I had the same cast server problem plus other issues with the clients contacting the server, the server recognizing clients, browsing the network.
I read somewhere in the knowledge base that ghost should not be installed on a DC so I figured that was why it was acting so strange. I uninstalled it off the DC and did a fresh install of 2.0 on a member server. Also did the update to 2.0.1.
Well with the member server install, all of my network and client issues went away except the contacting of the cast server.
I have a Ethereal Network trace from Ghost server to client . I have it in a .TXT or a Ethereal .cap file how would you like it?
Hi Paul,
.cap files would be great. I have send a message to you with details.
Krish
Are you trying to ghost a
Are you trying to ghost a client that has multiple NICs (IE redundancy on a server)? If so, and one is idle/disabled in Windows, it might load the correct driver, but not catch the correct NIC. May need to disable the idle NIC in the BIOS. Resolved my issue.
JCoz
Would you like to reply?
Login or Register to post your comment.