I don't know beans about Tivoli so just going to the basics of networking, is your box setup properly for its network (IP, netmask, gateway)? Also, does the message about 1500 (port presumably) mean that something is connecting to your box on your box's port 1500 or is your box reaching out to something else using port 1500? If the former then changing your own machine's firewall settings may be valid, but if not it likely is not. Having the current firewall settings would probably be nice:
#note that these are from my SUSE-based boxes, though I imagine these should work for any Linux distro with slight changes in paths possible) sudo /usr/sbin/iptables -nvL sudo /usr/sbin/iptables-save Also to rule in/out the firewall check log files that are for the firewall. On SUSE stuff this is /var/log/firewall and is pretty clear when something is blocked using the default firewall settings. Finally, test with something like netcat. I believe RedHat uses the version with the 'nc' command (vs. the 'netcat' command): nc -zv server.byu.edu 1500 The firewalls I've worked with most return nothing at all (no ICMP packets about ports being unreachable) when the firewall is blocking something (-j DROP in iptables syntax) though that is not required since -j REJECT is also allowed and even if ICMP packets are returned something else could block those from the remote host to a network device in between, so troubleshooting isn't always an exact science. With that said, Connection Refused usually means the firewall is not in the way but there is also nothing listening on the firewall-allowed port (1500) so perhaps Tivoli is down. Hopefully it's a start. AB On Wed, Oct 6, 2010 at 16:12, Graduate Studies Web Master <gswebmas...@byu.edu> wrote: > I’m stumped and I hope someone can help. I’ve had to set up a new server > because my previous one was hacked. > > I have RHEL5 on a VPS hosted by OIT at BYU. I only have access through SSH. > My backups are supposed to record using Tivoli on another BYU server. The > problem is that we’re having TCP/IP connection problems and I can’t seem to > figure out what is wrong exactly. I’ve been googling for a couple of hours > and am still not sure where the problem is and how I can fix it. > > My client log gives me: > > ANS5216E Could not establish a TCP/IP connection with address > ‘[server].byu.edu:1500’ . The TCP/IP error is ‘Connection timed out’ > (errno=110) > ANS9020E Could not establish a session with a TSM server or client agent. > The TSM return code is -50. > ANS1017E Session rejected: TCP/IP connection failure > > The server log gives a message like this: > > ANR8213E (Linux): Socket Socket identifier aborted due to send error; > error error code. > > I’ve tried to add the ports (1500,1876,1877) to my firewall that are listed > in the tsm.sys file as being the tcpPort and webPorts respectively, but that > doesn’t seem to make any difference. > > Is there some other way to check on the TCP/IP setup in RHEL5? > > Anyone have any ideas of what I should do next? > > Thanks, > Christijan > Web developer > Graduate Studies > 105 FPH , 422-5120 > > > > -------------------- > BYU Unix Users Group > http://uug.byu.edu/ > > The opinions expressed in this message are the responsibility of their > author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. > ___________________________________________________________________ > List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list > -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
