Ghost Solution Suite

 View Only

  • 1.  Clients on different subnets

    Posted May 25, 2007 10:02 AM
    I have a weekly Image Task setup on multiple computers in one subnet (individual offices w/router at each - multicast=off on all).  Each night the task kicks off and creates an entire image of a computer and stores it on a local NAS drive.  The server timeout is setup to stop executing after 15 minutes of idle time from the client.
     
    Here is the problem:  laptops that go to another office (subnet) and are connected will start their image task at their scheduled times (like it is supposed to).  This in turn saturates the WAN links (512k on both sides). 
     
    Is their anyway to keep the console server from seeing clients in other subnets?  Is this a router issue or console issue?  Could tasks be setup to not execute if client is on different subnet?
     
    I want all traffic to stay on the local subnet.
     
    Thanks


  • 2.  RE: Clients on different subnets

    Posted May 25, 2007 10:29 AM
    I forgot mention - using Ghost Console 11.0.0.1502
     
    Thanks


  • 3.  RE: Clients on different subnets

    Posted May 25, 2007 11:17 AM
    You can try to add the -JS= switch to your clone command under options.  It will sepcify how many hops (TTL) ghost is allowed to make to find the session.
     
    Currently I have the exact opposite problem.  I WANT machines in other subnets to find the console server but I can't make that happen.  Symantec STUPIDLY requires name resolution if broadcast/igmp fail to locate the console.  They can manipulate the DOS boot partition all day long via taks initiation.  You would think putting the freaking IP address of the console server would be better than random polling.


  • 4.  RE: Clients on different subnets

    Posted May 25, 2007 02:27 PM
    I use the -split=0 command line option already.   What is the seperator to use more than one command here?