check whether server is pin-gable from BSA or not. Please check the firewall on appserver as well as Target server, stop the service of firewall and test it again.
Revert with the logs so that we can Identify the issue.
1 of 1 people found this helpful
1.Login not allowed for user -> look in the rscd log on the target server. the role:user you are connecting from in bsa to the target is not mapped properly to a local user on the target. the rscd log will show what local user you are mapped to for the role:user.
2.Connectioon timed out - verify the appserver can connect to the target via agentinfo, started from the appserver. could be the rscd isn't running, could be some network issue.
pinging the target from the appserver only shows you the appserver can resolve the target, icmp may be blocked but that doesn't mean other ports aren't open.
Hi Abhishek Sir,
Thanks for your quick reply.
1. Login not allowed for user : For this we checked with the rscd.log file and removed the Role associated in already created Automation Principal and different rsc configuration files (Exports,users,users.local,secure).
Also checked with the log on as a batch job and deny log on as a batch job in local security policies.
Above Error is now resolved.
2.Connection time out : For this issue I checked with the telnet and also It is not pin-gable.I raised the same with the client .They are checking at their end for the same.
Please provide me your suggestions on this.
Why do you think that being able to ping the target will resolve the connectivity problem ? does the rscd use icmp ?
I suggested use ping just to check whether the server is reachable or not, as I am addicted to this as a part of troubleshooting.
The only thing a ping tells you is if the appserver can resolve the target and if icmp is allowed