Ghost Solution Suite

hi,

we are using Ghost 2.0.1 successfully in our lab where client and server both located in same VLAN. recently we added one more VLAN to our Lab now the systems in new VLAN are not able to connect to the ghost server in another VLAN. Multicast is enabled in new VLAN. how to make client systems in new VLAN to connect to the Server.
client in new VLAN can ping the server by name but in system tray it says Trying to locate server. in ngctw32.log file client is keep on trying for polling the server. below i am adding the ngctw32.log file from client:

----------------------------------------
C:\Program Files\Symantec\Ghost\ngctw32.exe  11.0.1.1533
9:42:18 PM Friday, August 10, 2007

Checking for Sysprep. Process id: 296, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SMSS.EXE
Checking for Sysprep. Process id: 344, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\CSRSS.EXE
Checking for Sysprep. Process id: 372, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\WINLOGON.EXE
Checking for Sysprep. Process id: 420, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SERVICES.EXE
Checking for Sysprep. Process id: 432, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\LSASS.EXE
Checking for Sysprep. Process id: 664, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 740, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 800, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 844, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 864, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 1032, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SPOOLSV.EXE
Checking for Sysprep. Process id: 1064, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\MSDTC.EXE
Checking for Sysprep. Process id: 1132, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\COMMON FILES\ARCHESTRA\AALOGGER.EXE
Checking for Sysprep. Process id: 1188, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 1208, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\COMMON FILES\ARCHESTRA\NTSERVAPP.EXE
Checking for Sysprep. Process id: 1268, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\INTEL\INTEL APPLICATION ACCELERATOR\IAANTMON.EXE
Checking for Sysprep. Process id: 1292, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\INETSRV\INETINFO.EXE
Checking for Sysprep. Process id: 1328, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\COMMON FRAMEWORK\FRAMEWORKSERVICE.EXE
Checking for Sysprep. Process id: 1368, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\VIRUSSCAN\MCSHIELD.EXE
Checking for Sysprep. Process id: 1404, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\VIRUSSCAN\VSTSKMGR.EXE
Checking for Sysprep. Process id: 1520, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\BINN\MSFTESQL.EXE
Checking for Sysprep. Process id: 1576, name: \DEVICE\HARDDISKVOLUME1\PROGRA~1\NETWOR~1\COMMON~1\NAPRDMGR.EXE
Checking for Sysprep. Process id: 1604, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\BINN\SQLSERVR.EXE
Checking for Sysprep. Process id: 1760, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL.2\OLAP\BIN\MSMDSRV.EXE
Checking for Sysprep. Process id: 1884, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 1896, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL.3\REPORTING SERVICES\REPORTSERVER\BIN\REPORTINGSERVICESSERVICE.EXE
Checking for Sysprep. Process id: 1964, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\COMMON FILES\ARCHESTRA\SLSSVC.EXE
Checking for Sysprep. Process id: 1988, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\ANALOG DEVICES\SOUNDMAX\SPKRMON.EXE
Checking for Sysprep. Process id: 2012, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\MICROSOFT SQL SERVER\90\SHARED\SQLWRITER.EXE
Checking for Sysprep. Process id: 2072, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\REALVNC\VNC4\WINVNC4.EXE
Checking for Sysprep. Process id: 2152, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 2436, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\BINN\SQLAGENT90.EXE
Checking for Sysprep. Process id: 2664, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 3160, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\EXPLORER.EXE
Checking for Sysprep. Process id: 3284, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\ALG.EXE
Checking for Sysprep. Process id: 3336, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\ANALOG DEVICES\CORE\SMAX4PNP.EXE
Checking for Sysprep. Process id: 3356, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\VIRUSSCAN\SHSTAT.EXE
Checking for Sysprep. Process id: 3380, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\COMMON FRAMEWORK\UPDATERUI.EXE
Checking for Sysprep. Process id: 3388, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\COMMON FILES\NETWORK ASSOCIATES\TALKBACK\TBMON.EXE
Checking for Sysprep. Process id: 3436, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\INTEL\INTEL APPLICATION ACCELERATOR\IAANOTIF.EXE
Checking for Sysprep. Process id: 3712, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\SYMANTEC\GHOST\NGTRAY.EXE
Checking for Sysprep. Process id: 3888, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 4024, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\WBEM\WMIPRVSE.EXE
Checking for Sysprep. Process id: 3476, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\MMC.EXE
Checking for Sysprep. Process id: 932, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\CMD.EXE
Checking for Sysprep. Process id: 3884, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\SYMANTEC\GHOST\NGCTW32.EXE
9:42:23 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:42:33 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:42:53 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:43:33 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:44:53 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:46:53 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:48:53 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:50:53 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:52:53 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:54:53 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:56:53 PM 10.91.59.148:1346 polling for bound server indlabsrv1
9:58:53 PM 10.91.59.148:1346 polling for bound server indlabsrv1

please help. Thanks in advance.

Regards,
Raghu.

Even though multicast might be enabled on the switch that is maintaining the VLAN, you also need to consider the routing connectivity between the VLANs - each VLAN is a separate subnet, so all the traffic between the two subnets needs to go either through a router (or a routing module in the switch) to be carried between the subnets, instead of being done through the normal operation of the switch.

If it's an external router, that router needs to also be configured to join multicast groups across subnets (how that's done depends on the router) and if it's an internal routing module in a managed switch there may be several ways that you can arrange for inter-VLAN multicast connectivity depending on the manufacturer and model - some managed switches have modes which simply make the allocation of switch ports to VLANs go away for multicast purposes, for instance, while others have separate routing configurations.