Clients not showing in console
Updated: 21 May 2010 | 13 comments
Hello there,
I recently installed GSS 2.0 on a small network here (about 6 servers, under 100 workstations), and successfully deployed the client remotely to all machines. However, no matter what I do, I cannot get the clients to appear in the console - not in the default or in any of the other machine groups I've created. I've tried rebooting, setting up a WINS server and connecting all clients/servers to it (helped with another problem on a different network), and reinstalling the client.
The clients themselves all say they're connected and being managed by the server (in the system tray icon), but they're not showing up in the console.
Thanks in advance,
MT3 Green, US Navy
Discussion Filed Under:
Comments
Multicasting
The issue here is that multicast traffic needs to be allowed over your routers and switches. The console and client communicate via multicast. Here is an article on how Ghost communicates:
How the Ghost Console and Client communicate over the network
http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2002101612025325
WINS
1.2.2. Method 2: WINS
Details of this method are shown below for your interest. However, this method relies on a WINS infrastructure existing and working between the networks in question.
We have a working WINS server, and all of the clients are registered on it (this is how we have it set up on another network and GSS works fine). And I'm still not sure how the server would be able to do a remote client install via the domain, and a client would see the server ("managed by servername at xxx.xxx.xxx.xxx), but then not see the client in the machine groups.
V/R,
MT3 Duncan R. Green, US Navy
Multicasting
Duncan,
WINS is a fallback method when multicasting isn't available, and may not work on all networks. Multicasting is really what we need there for client/console communication to work. the remote client install feature does not use this communication method, instead using a simple Windows file transfer and then executes the command with supplied administrative credentials.
Multicasting and Ports
Okay, we'll try and get multicasting to work. Due to the nature of our institution, we do not have control over our routers, though - they are administratred remotely.
From that document, it looks like we're going to need to enable mutlicasting in the router/switch IOS, and open ports 1024-4999, 6666, and 7777, correct?
V/R,
MT3 Duncan R. Green, US Navy
That is correct. Or at least
That is correct. Or at least allow exceptions for GhostSrv.exe and ngctw32.exe, if that is possible.
Some clients
Perhaps I should clarify - some clients are showing, but only a few of them. Everyone is on the same subnet, we're not running DHCP, the IP Addresses are all static, and I haven't changed any configuration settings.
The clients that are showing seem to be doing so without the WINS, because they still report, do tasks, etc, when the WINS server is off. This makes me think that IGMP, Multicasting, etc are on and working.
And now I've got another interesting symptom - one of the clients that is showing is shifting. It's name, mac address, IP address - everything - change each time I execute a refresh. It changes to a completely different machine each time, seemingly picking a random machine from the entire network's worth of machines that are not already in the client.
V/R,
MT3 Duncan R. Green, US Navy
LICENSE
If your getting some clients to appear in the console after a refresh it could be your being limited by the license.
License
I checked the license in the console and it's saying that we have something like 100 used out of 8,000 or so - we have plenty of licenses :P
V/R,
MT3 Duncan R. Green, US Navy
Resolution?
Did you ever resolve this issue? I am having the exact same issue on my network. Any input would help. thanks
Machine model?
Duncan, what model of machines are shifting? Are these all the same model?
Resolution?
I to have just developed this problem. Until now I had no issue with the 180 or so machines behind a single DC. Now as I build new ones (never been cliented before) they refuse to show up in Defualt group. Clients say they are connected and managed. Console does not see them in Default or Network?
Server 2k3 r2, XP Pro Clients, Single subnet, Functioning correctly for 18 months. Various hardware sets on clients. Existing Console clients are solid and performing correctly. Only adding new or deleting then rebuilding old machines present with this problem. Liscence is fine.
This is my first post in here, I will continu to browse and link back if I stumble on a solution.
Rogue console?
saltyp,
Are there any other machines (besides your primary Ghost Console machine) that host a Ghost Console? If more than one console is on a given network, this can cause issues. You can check the server name/ip address a client is connected to by mousing over the client icon.
single GSS installation
Just the one console installed on a single DC. No others within the Domain or on the same LAN regardless of subnets. After today (just home from work) the issue may be a DHCP one not related to GSS at all. Will learn more tomorrow and post back. Today I added two laptops to the domain and started get "this Ip address already exists...blah blah" The whole domain is a class A address pool with no subnets and all clients are DHCP with reserve ranges for NAS, printers etc. I suspect the two problems may be linked (no complaints from users....YET!)
Thanks for the response.
Would you like to reply?
Login or Register to post your comment.