I've got a stumper of one here.
And I'll cut it just for you.
I've been fighting with my company's Ghost Console for the past week, and I need some help, because I've got what I think is a stumper. It's got me stumped, at least.
The issue is that we have an office that has a lab of 13 machines that we re-image remotely on a regular basis (or did until it stopped working earlier this week). The server that runs the show is at a different office some 5 miles distant across a Metro Ethernet / DS3 connection.
The server is at 10.10.128.x, the machines are at 10.20.10.x. Pings, network traffic goes just peachy. Also, the remote client install goes fine as well. What happens is that the server will initate a task (either image creation or clone) and it will sit and time out. The clients appear to just sit there and do absolutely zilch. It's like they don't catch the signal to start the task.
I was able to initally duplicate the problem on a single test machine back at the facility where the server lives, but I thought I had it fixed by completely removing the machine from the console, removing the tasks it was associated with, and then re-adding it from scratch (including reinstalling the client). This appeared to work just peachy, but I can't get the machines I've removed to show back up in the console.
Anyone know of a way to either manually add machines to the console, or to force it to re-discover all the machines on the network?
::puts on flame-resistant suit and digs out the whips::
EDIT:::: It looks like a multicast over WAN, combined with the machines not wanting to report back to the server across said WAN link, possibly using the same multi-cast method. I'd asked one of the BNAFH* to look at it, and we'll see what happens.
*- Bastard Network Admins From Hell. DOn't piss them off, or they will route all your traffic through SimonNet. :)
I've been fighting with my company's Ghost Console for the past week, and I need some help, because I've got what I think is a stumper. It's got me stumped, at least.
The issue is that we have an office that has a lab of 13 machines that we re-image remotely on a regular basis (or did until it stopped working earlier this week). The server that runs the show is at a different office some 5 miles distant across a Metro Ethernet / DS3 connection.
The server is at 10.10.128.x, the machines are at 10.20.10.x. Pings, network traffic goes just peachy. Also, the remote client install goes fine as well. What happens is that the server will initate a task (either image creation or clone) and it will sit and time out. The clients appear to just sit there and do absolutely zilch. It's like they don't catch the signal to start the task.
I was able to initally duplicate the problem on a single test machine back at the facility where the server lives, but I thought I had it fixed by completely removing the machine from the console, removing the tasks it was associated with, and then re-adding it from scratch (including reinstalling the client). This appeared to work just peachy, but I can't get the machines I've removed to show back up in the console.
Anyone know of a way to either manually add machines to the console, or to force it to re-discover all the machines on the network?
::puts on flame-resistant suit and digs out the whips::
EDIT:::: It looks like a multicast over WAN, combined with the machines not wanting to report back to the server across said WAN link, possibly using the same multi-cast method. I'd asked one of the BNAFH* to look at it, and we'll see what happens.
*- Bastard Network Admins From Hell. DOn't piss them off, or they will route all your traffic through SimonNet. :)
