win2000 box with oracle9i 184.108.40.206.0 with OEM
solaris 8 box with oracle9i 220.127.116.11.0
both databases were set up with no major problem, and i was able to discover the solaris db from OEM right after the solaris oracle installation.
due to ip conflict i changed the ip of the solaris box, and now i could not discover the solaris node from OEM. I was able to ping/telnet to the new solaris ip with no problems, and i tried tnsping and it worked too.
i restarted the solaris listener and db but i still couldn't manage the solaris db from my OEM.
still having problem with the agent....
i double-checked the agent on both boxes, which are all running smoothly. I did find that the ip in tnsnames.ora for orasol is incorrect, so i changed it, but still couldn't automatically discover the node.
can anyone offer me some directions on how to further troubleshoot this problem?
Your DNS has to resolve both forward and backward the host.
The *.q files are the queue files the agent creates when being discovered as a node from OEM. You want to make sure no old information is left over in these files, before trying to re-discover the node. That's all.