Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
up vote 0 down vote favorite

This is a counter-intuitive problem for me. I have a new Win 2003 server on a static IP address w.x.y.z. Tomcat 7, PostgreSQL 9.1, and Subversion are installed. All of it appears to be working fine from the server itself. We can also access the Tomcat manager, web applications, and run "svn ls svn://w.x.y.z/" from outside our network.

However, when I try from another machine in the office, phpPgAdmin and svn cannot establish connections with the server. http://w.x.y.z:5432/phppgadmin cannot connect. The svn command from above returns:

svn: E730061: Unable to connect to a repository at URL 'svn://w.x.y.z/'
svn: E730061: Can't connect to host 'w.x.y.z': No connection could be made because the target machine actively refused it.

Tomcat manager and the other web apps we have deployed work fine.

Netstat -a from the server shows this:

Proto   Local Address     Foreign Address   State
TCP     SERVERNAME:3690   SERVERNAME:0      LISTENING
TCP     SERVERNAME:5432   SERVERNAME:0      LISTENING

Windows Firewall was off, but just in case I also tried to enable it and open ports 3690 (svn) and 5432 (postgres). No change.

I don't have access to the router/switch because it just doesn't work that way in Port-au-Prince and our sysadmin is on R&R. Is there anything that might be causing the problem from the server side?

share|improve this question
Please clarify the "with static IP w.x.y.z" - is w.x.y.z actually a globally valid IPv4 address (i.e. non RFC1918), assigned directly to an interface on that machine (i.e. visible in ipconfig /all)? – themel Nov 10 '11 at 15:24
Are the server and the client connected to a firewall and/or do they get the same public IP? – duenni Nov 10 '11 at 15:31
w.x.y.z is a global IP. We can hit it directly from the US and Europe. My laptop in the office has a different public IP from the server, which I assume is the router's IP. Again, the router is a bit of a black box. We're on Haitian time here. – ChrisJ Nov 10 '11 at 15:49

1 Answer

up vote 0 down vote

If the message you get is "the target machine actively refused it, that means that you attempted to open a TCP socket, and got a message back that the port is closed. If the port is open from other locations, then there is some intervening L4 firewall/proxy that is blocking that traffic.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.