Ghost Solution Suite

Ghost solution 2.5.  Testing file transfer task from the console returns failed error code:1 with the following errors in the log on the client.

5:48:26 PM 192.168.3.12:1346 TCP connecting to  192.168.3.111:1347
Received message #\Session{ Status = #true }
Received message #\WarnShutdown{ Timeout = 10, Cancel = 0, Shutdown = 1, Platform = DOS }
Received message #\Open{ What = File, Mode = Write, Name = "C:/IE8-Setup-Full.exe", UDMMode = 2, Port = 4486 }
5:48:26 PM starting RML, creating socket
5:48:26 PM 192.168.3.12:1346 disconnecting from 192.168.3.111:1347
Connecting to RML session
netlog: ..\..\ghost\src\rml\RMLStack.cpp:3025: gh_setsockopt failed: The requested address is not valid in its context.

netlog: ..\..\ghost\src\rml\RMLStack.cpp:3058: gh_setsockopt failed: The requested address is not valid in its context.

5:48:46 PM 192.168.3.12:1346 sending status to  192.168.3.111:1347
5:48:46 PM 192.168.3.12:1346 acknowledged by    192.168.3.111:1347
5:48:46 PM 192.168.3.12:1346 TCP connecting to  192.168.3.111:1347
Received message #\Session{ Status = #true }
Received message #\Open{ What = File, Mode = Write, Name = "C:/IE8-Setup-Full.exe", UDMMode = 2, Port = 4486 }
Received message #\taskInProgess{ Cancel = 1 }
Received message #\PreventLoginTask{ DisableLogin = 0 }
Received message #\Shutdown{ Name = () }
5:48:46 PM 192.168.3.12:1346 disconnecting from 192.168.3.111:1347

Console is used to succesefully image and backup worksations without a problem.  The console and the client are on the same subnet and the firewall is disabled during running the task.  Trying unicast had the same effect.  Please respond if you have any input on this.

Hi,

This is an error I haven't seen before, but it looks like a client side issue rather than a network issue. What is the client OS? You said Firewall is off during the task execution. How did you turn it off? 

Krish

Thanks for replying.  Console is running on Server 2003 R2 clients are on XP sp2.

Creating and restoring images works perfectly.  Tryed reinstalling the console, problem persists.

Thanks for your help?

Hi,

This should be happening from the client side, not from server side. So changing the Server would not help. It looks like something is blocking the client from using the port given by Windows. 

Could you try sending the file using folder transfer instead of file transfer? Folder transfer uses a different mechanism than file transfer. Chances are that it will work, but it is always a unicast so you would not get the benefit of multicast. However, it will eliminate the possibility of any other error except the port issue. 
 

Krish

Krish.  Thanks again.  Folder transfer works. From what i am able to understand i am having an issue with multicast.  My question is would it be related to my network equipment then?

Thank you.

Hi,

OK-that's good. But I don't think this is anything to do with your equipment. Even if they do not support multicast, unicast should work. You do not have any issues in cloning, which again proves that the network is all right.

This must be something at the client OS. Something must be interfering with the process. Do you have any network related apps installed in this machine? Even with the firewall, file transfer should work since client adds itself to the exception list. Could you try it in a different machine with difference apps installed?

Krish

Krish.  Thanks again.  And you were right.  After reviewing the logs i realized that a manual IGMP level=1 was set in the registry under

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

Which will send but not recieve multicast trafic. and after setting it to default 2 which is equivalent to deleting it all at once file transfer task works again.  However while trying to resolve the issue i did to use unicast to file transfer task and failed.

In either case.  Thank you very much for you help.  I should send a botle of your favorite to you in Symantec.

:-)

Good to hear that it is resolved, and thanks for the update. I haven't seen this setting before.

Unicasting and multicasting share lot of code, and this setting might have stopped unicast too.

Krish