hi all [color blue] i have a situ

[ashishv]

hi all

i have a situation.
i have one AIX box which is configured as the TMR server and the endpoint Gateway, windows NT server configured as the Managed node, also with the end point gateway. there are 5 end points including the TMR server and the managed node.


the situation arised when one of the endppoint (windows 95) was hung and had to be rebooted. after it rebooted it refused to login in to the specified gateway (managed node) and was isolated. i tried to reassign the gateway to the EP but it failed to login.
i deleted the EP from the managed node and uninstalled the endpoint from windows
95. cleared the registry and rebooted. i reinstalled the EP and configured the same
gateway as the default gateway for the EP to login. it again refused. after this i checked the logs for the endpoint and also ran the debug screen. there it said that port 9495 busy. and binding to 9496 . and on this alternate port also it was not able to login.and then it restarted the initial login broadcast. after few minutes it logged in to the TMR server gateway.

now my question is :

1) why was the EP port 9495 busy. was it made busy by the OS or was it tivoli EP that
had made it busy.
2) if it is busy then how can i retieve it and also make it functional so that my EP logs
in the assigned gateway.
3) why didnt the Managed node Gateway responded to the initial login broadcast of
the EP.


any help will be appreciated as it is an urgent situation and is a test bed for the production enviornment.


Regards
Ashish Vashisht
Tivoli Certified Consultant


Ashish Vashisht
vashishtashish@yahoo.com

 

[SimonERM]

If the Endpoint was logged in then you have a file lcf.dat that is created. If this file is present then this information is used ahead of the .login file.
I'd try deleting that file, editing the text file (or use the Web interface) and try again.

 

[txtxcowboy]

what are the details of your allow_install policy?