Ghost Solution Suite

I am getting this error when I click the Accept Connections button in GhostCast.
Ghost Server Suite 2.5 (new just downloaded 3-27-09)
"An error occourred during GhostCast Transmission"

I've seen a couple other questions on this, but I haven't seen a solution yet. I've been searching for 2 days now. I am an IT expert, (just not in Ghost... yet, although I've used it on and off since its original versions.) so be as technical as you need to be with your replies.

Here's the log file:

Log Level All
2471156438 GhostSrv 11.5.0.2113
           Thu Mar 26 20:57:56 2009

           Server is in image dump mode - will force client into unicast mode
           Initialising RML
2471156454 rml_get_local_interfaces found these IP addresses:
              192.168.1.5
              192.168.0.100
           RML Initialised
           RML socket send buffer size set to 1831680
           Setting UDP socket receive buffer size to 60102
           UDP socket receive buffer size set to 60102
           RML socket receive buffer size set to 57240
2471156469 Throttle value:0 mb/min
           Length of tick in seconds:0.001000
           Ticks per throttle bucket:15
           Throttle byte count limit[0] = 0
           Throttle byte count limit[1] = 0
           Throttle byte count limit[2] = 0
           Throttle byte count limit[3] = 0
           Throttle byte count limit[4] = 0
           Throttle byte count limit[5] = 0
           Throttle byte count limit[6] = 0
           Throttle byte count limit[7] = 0
           Throttle value:0 mb/min
           Length of tick in seconds:0.001000
           Ticks per throttle bucket:15
           Throttle byte count limit[0] = 0
           Throttle byte count limit[1] = 0
           Throttle byte count limit[2] = 0
           Throttle byte count limit[3] = 0
           Throttle byte count limit[4] = 0
           Throttle byte count limit[5] = 0
           Throttle byte count limit[6] = 0
           Throttle byte count limit[7] = 0
           RML socket send buffer size set to 4194304
           Server multicast address set to 224.77.214.136
           Throttle value:0 mb/min
           Length of tick in seconds:0.001000
           Ticks per throttle bucket:15
           Throttle byte count limit[0] = 0
           Throttle byte count limit[1] = 0
           Throttle byte count limit[2] = 0
           Throttle byte count limit[3] = 0
           Throttle byte count limit[4] = 0
           Throttle byte count limit[5] = 0
           Throttle byte count limit[6] = 0
           Throttle byte count limit[7] = 0
           Bound RML socket to 0.0.0.0:20364
           Setting multicast scope to 16
           State was 0, now 1
           Bound TCP socket to 0.0.0.0:20365
           gh_bind failed: Permission denied.

           RML Statistics

System:
OS Name Microsoft(R) Windows(R) Server 2003 for Small Business Server
Version 5.2.3790 Service Pack 2 Build 3790
System Manufacturer Dell Computer Corporation
System Model PowerEdge 4400
Processor x86 Family 6 Model 8 Stepping 6 GenuineIntel ~993 Mhz
Processor x86 Family 6 Model 8 Stepping 6 GenuineIntel ~993 Mhz
BIOS Version/Date Dell Computer Corporation A11, 8/8/2003
SMBIOS Version 2.3
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Hardware Abstraction Layer Version = "5.2.3790.3959 (srv03_sp2_rtm.070216-1710)"
Total Physical Memory 3,071.49 MB
Available Physical Memory 147.73 MB
Total Virtual Memory 5.44 GB
Available Virtual Memory 660.37 MB

Name [00000007] NETGEAR GA311 Gigabit Adapter
Adapter Type Ethernet 802.3
IP Address 192.168.1.5
IP Subnet 255.255.255.0
Default IP Gateway Not Available
Driver c:\windows\system32\drivers\ga311nd5.sys (5.608.1009.2003, 65.13 KB (66,688 bytes), 9/1/2007 11:40 AM)
 
Name [00000008] NETGEAR GA311 Gigabit Adapter
Adapter Type Ethernet 802.3
IP Address 192.168.0.100
IP Subnet 255.255.255.0
Default IP Gateway 192.168.0.1
Driver c:\windows\system32\drivers\ga311nd5.sys (5.608.1009.2003, 65.13 KB (66,688 bytes), 9/1/2007 11:40 AM)


According to the log, it appears at the end that there is some problem with binding TCP to a stack, but I don't know what the problem is, or which stack it is binding to. Possibly a missing protocol on the NIC? Or maybe Microsoft's update, that came out last year, to DNS that is supposed to lock down all the ports? 

I don't know why it is trying to bind to 0.0.0.0? Shouldn't it bind to the NIC's IPs? 

There are Dual NICs in a Windows 2003 SBS box. One is the "outside" with the address of 192.168.0.100 the other is the "inside" with and address of 192.168.1.5.

All internal systems are on the 192.168.1.x network.

There is no firewall on this server.

Ghostcast is running while logged in as administrator.

There appears to be nothing bound to the 20365 port in netstat -a.

It doesn't matter what settings I put in the GhostCast server. I still get this error.

Tried changing the wattcp.cfg file to have the primary NIC as the IP. No help there. Not sure of all the possible settings in this file.

I hope I provided enoug information. Anyone have an answer or a suggestion?

Dan

I've had a ton of problems with using multicast with Ghost in the 2 places I've worked that used this.  The first place I was at I had no control over the configuration of the switches and there were multiple VLANs configured for the network.  The problem there was that the admin port was not enabled on the particular VLAN that I was using Ghost and so Multicast traffic was not enabled.

The second place I worked was the same situation where I had no control over the switches and again Multicast was not enabled because of multiple VLANs on the network.  I have yet to convince them to enable it for my VLAN and so I'm forced to use Unicast.  Obviously this means that I can't feasibly Ghost an entire lab of 30 computers unless I want it to take 2 to 3 days.  Nevermind that we have 5 labs in total.

Same error even when forced to unicast or directed broadcast. Maybe I'm missing something on my protocol stack for it to bind to? I checked the switch too. Nothing filtering multicast. I am making an assumption that a bind issue is somehow related to trying to bind the protocol port to the existing stack. Seem like a reasonable assumption?  

Dan

Tried the GhostCast server on another PC (Windows 2000 sp4) and it works there. Therefore the problem is in my 2003 SBS box. Possibly because there are 2 NICs in it, but more likely because of the KB that was supposed to fix an issue with available ports in DNS. Researching further to find out why I cannot bind.

dh

dan.hoyer

I noticed in the log that you are running Ghost version 11.5.0.2113. You should run LiveUpdate to get you to 11.5.0.2165. You will need to run LiveUpdate three times and the version change is reflected only in Ghost Explorer.

Also is there any activity on the client side? Is there an error code generated on the client side? Errors are usually six numerical digits log and may be accompanied by some text.

The solution is: 
http://support.microsoft.com/kb/956189/
and/or here: 

http://support.microsoft.com/kb/956188/

The problem is cause by: 
Domain Name System (DNS) security update 953230 (MS08-037)

If you install this update, DNS will take over the ports in the range where GhostCast wants to set up its UDP connections. (6666-6669)

So to fix it do this: (disclaimer - if you hose your registry its your fault!)

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. Right-click ReservedPorts, and then click Modify.
4. Type the range of ports that you want to reserve. FOR GHOSTCAST USE 6666-6669
   
   Notes

• You must type the range of ports in the following format:
  xxxx-yyyy
  Do not replace the existing values. Instead, add the additional values.
  To specify a single port, use the same value for x and for y. For example, to specify port 4000, type 4000-4000.
• If you specify the continuous ports separately and if one port is reserved and is not used, the next port is not reserved correctly, and the port is used.
• ISA Server settings only apply to Small Business Server 2000 or to Windows Small Business Server 2003 Premium Edition.
   

Click OK.
RESTART DNS OR RESTART YOUR SERVER

Now... how did I find this??? No thanks goes to the GhostCast Log Errors!!!

Here's the original log:
           Bound RML socket to 0.0.0.0:20364
           Setting multicast scope to 16
           State was 0, now 1
           Bound TCP socket to 0.0.0.0:20365
           gh_bind failed: Permission denied.

So it appeared that the second TCP bind failed! WRONG. Here's a copy from a working server:
           Bound RML socket to 0.0.0.0:3400
           Setting multicast scope to 16
           State was 0, now 1
           Bound TCP socket to 0.0.0.0:3401
           Bound UDP socket to 0.0.0.0:6666

An AH-HA moment! The error was on binding UDP not TCP! And somewhere in the back of my mind I remembered this problem previously trying to bind to UDP. Looked it up on MS support site and there it was! WOO  HOO!

I should give myself a cookie for this one!

Anyone have a job for an IT Guru with 25 years experience? 

Dan

Thanks already updated. Saw that I hadn't done the LiveUpdate after I posted my message. That didn't help. I did post the solution though.

Dan


dan.hoyer

I noticed in the log that you are running Ghost version 11.5.0.2113. You should run LiveUpdate to get you to 11.5.0.2165. You will need to run LiveUpdate three times and the version change is reflected only in Ghost Explorer.

Also is there any activity on the client side? Is there an error code generated on the client side? Errors are usually six numerical digits log and may be accompanied by some text.

Just to re-iterate. The original problem was that GhostCast would not start listening when Accept Connections was clicked. It immediately displayed an error of: "An error occourred during GhostCast Transmission" when the button was clicked.

dan.hoyer

I would like to make a kb article out of this issue. What is the specific error code that you are receiving? Thank you.

As I recall there wasn't a specific error number. That was part of the problem. It was a pop-up box that came up over GhostCast that had the error message in it, and an OK button. And now I cannot repeat the problem. (I am guessing that DNS has chosen to bind a different range of ports)

So here's how I tested it. 1) Downloaded UDP Test Tool. 2) Bound to host port 6666. 3) Started GhostCast 4) Configured GhostCast for a Create image session setting the Session Name and Image File. 5) Clicked Accept Clients
The error is this:

<TITLE BAR>Symantec GhostCast Server
<BIG RED CIRCLE WITH A WHITE X>
  An error occurred during GhostCast transmission.
  If this error persists, plese contact technical support and have GhostCast server and client error logs available.
                       <OK BUTTON>

And then there is the log information provided previously.

Dan