Rudi Ahlers
2008-Aug-09 23:25 UTC
[CentOS-virt] can't access irc server on xen domU, please help
Hi all, I'm running a CentOS 5.2 server with a FC8 xen domU guest, and an irc server on the FC8 domU guest. For some odd reason, I can't access the irc server on the xen domU guest.>From FC8, when I run netstat -a, I can see irc is listening:netstat -a Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:ircd *:* LISTEN tcp 0 0 *:6668 *:* LISTEN tcp 0 0 *:6669 *:* LISTEN tcp 0 0 *:ftp *:* LISTEN tcp 0 0 192.168.10.:afs3-fileserver *:* LISTEN tcp 0 0 localhost.localdomain:smtp *:* LISTEN tcp 0 0 192.168.10.13:ftp 196-209-84-62-tpr-esr:49615 ESTABLISHED tcp 0 0 *:http *:* LISTEN tcp 0 0 *:ssh *:* LISTEN and running nmap on the localhost looks promising as well: netstat -a Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:ircd *:* LISTEN tcp 0 0 *:6668 *:* LISTEN tcp 0 0 *:6669 *:* LISTEN tcp 0 0 *:ftp *:* LISTEN tcp 0 0 196.34.136.:afs3-fileserver *:* LISTEN tcp 0 0 localhost.localdomain:smtp *:* LISTEN tcp 0 0 196.34.136.55:ftp 196-209-84-62-tpr-esr:49615 ESTABLISHED tcp 0 0 *:http *:* LISTEN tcp 0 0 *:ssh *:* LISTEN Yet, from the outside (either from another PC, or the dom0 itself), I can't connect to the irc ports. I've even disabled iptables on the dom0 altogether, but stil can't connect to it. The only open ports are: PORT STATE SERVICE 80/tcp open http 443/tcp closed https 7001/tcp closed afs3-callback 8000/tcp closed http-alt 8080/tcp closed http-proxy 8081/tcp closed blackice-icecap How do I get this to work? -- Kind Regards Rudi Ahlers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20080810/3daeb9ee/attachment-0004.html>
Rudi Ahlers
2008-Aug-10 06:41 UTC
[CentOS] can't access irc server on xen domU, please help
Hi all, I'm running a CentOS 5.2 server with a FC8 xen domU guest, and an irc server on the FC8 domU guest. For some odd reason, I can't access the irc server on the xen domU guest.>From FC8, when I run netstat -a, I can see irc is listening:netstat -a Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:ircd *:* LISTEN tcp 0 0 *:6668 *:* LISTEN tcp 0 0 *:6669 *:* LISTEN tcp 0 0 *:ftp *:* LISTEN tcp 0 0 192.168.10.:afs3-fileserver *:* LISTEN tcp 0 0 localhost.localdomain:smtp *:* LISTEN tcp 0 0 192.168.10.13:ftp 196-209-84-62-tpr-esr:49615 ESTABLISHED tcp 0 0 *:http *:* LISTEN tcp 0 0 *:ssh *:* LISTEN and running nmap on the localhost looks promising as well: netstat -a Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:ircd *:* LISTEN tcp 0 0 *:6668 *:* LISTEN tcp 0 0 *:6669 *:* LISTEN tcp 0 0 *:ftp *:* LISTEN tcp 0 0 196.34.136.:afs3-fileserver *:* LISTEN tcp 0 0 localhost.localdomain:smtp *:* LISTEN tcp 0 0 196.34.136.55:ftp 196-209-84-62-tpr-esr:49615 ESTABLISHED tcp 0 0 *:http *:* LISTEN tcp 0 0 *:ssh *:* LISTEN Yet, from the outside (either from another PC, or the dom0 itself), I can't connect to the irc ports. I've even disabled iptables on the dom0 altogether, but stil can't connect to it. The only open ports are: PORT STATE SERVICE 80/tcp open http 443/tcp closed https 7001/tcp closed afs3-callback 8000/tcp closed http-alt 8080/tcp closed http-proxy 8081/tcp closed blackice-icecap How do I get this to work? P.S. Sorry for the cross-post, for those of you who are on the centos-virt list as well, I just find that this list is being used more. -- Kind Regards Rudi Ahlers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20080810/6c1f67b8/attachment.html>
Kai Schaetzl
2008-Aug-10 11:31 UTC
[CentOS] can't access irc server on xen domU, please help
Rudi Ahlers wrote on Sun, 10 Aug 2008 08:41:55 +0200:> The only open ports are: > PORT STATE SERVICE > 80/tcp open http > 443/tcp closed https > 7001/tcp closed afs3-callback > 8000/tcp closed http-alt > 8080/tcp closed http-proxy > 8081/tcp closed blackice-icecapCompare that with your lists above. It doesn't fit at all, e.g. there is no https on your other lists. Looks very much like a dns or IP address problem - the latter test is not against the same target although you think it is. Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com