I had Director 4.1 installed, and it worked great for a while but then I noticed that newly installed agents could not be discovered by the server. According to the documentation server-agent communication is done on port 14247, which was not opened when the agent was installed on the machines. Upgrading server and agents to 4.12 didnt help. Has anyone even had this problem
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
IBM Director server not finding some agents
- Thread starter wezel
- Start date
If the Agents are not in the same logical subnet as the Director Server, you should define Relay Agents via Discovery Preferences > IP Discovery, selecting an Agent system that is usually running. By default, the Director Server only discovers Agents in the local subnet. If you have a lot of network activity, you may also consider increasing the network timeout setting in Network Driver Configuration (TWGIPCCF.EXE) on the Agent and the Director Server. Changes here require a restart of the Director Agent (net stop/net start TWGIPC.EXE). 30 - 45 seconds is usually sufficient, and you don't want to increase it too much, since the Director server will wait this long for every command to execute. While in Network Driver Configuration, make sure you enabled an interface for the Agent.
- Status
