Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

not able to connect to web server outside domain

Status
Not open for further replies.

wile666

IS-IT--Management
Jun 13, 2005
70
US
I have recently setup an ftp site on one of my servers. I can access it from within the network, but when I try from my home computer it will not connect. The server also hosts our intranet and I cannot access it either. I'm using IE 7 at home and tried the "diagnoise problem". It says the server is there but not accepting connection. That it may be a firewall issue on the server.
The server is behind a router firewall and I have verified with roadrunner that for the external address ports 80, 443, 21, 20 are all open and being forwarded to that internal server. There are no firewalls installed on the server itself. I have made sure that NAT is not installed for RRAS. I have other servers that I can access web services from outside the network.
 
You can use z'shields up" from the Gibson Research Center to initiate a port scan from the internet to verify the ports required are accessed.

Go to the server in question, launch a web browser, go to
locate Shields Up and follow directions.
report back your findings.

Jesse Hamrick
 
The problem with online port scans is that they scan the router ip. I have several computers that have static ip addresses setup through NAT by roadrunner. the port scanners do not test the public static address of my server.
 
I haven't tried from the command line yet. i'll try tonight.
the IE settings are enabled for passive FTP.
 
Sounds like your router doesn't know to send the incoming port 21 to your server and so when you ping it you will hit your routers IP as you stated before. Check to make sure that port forwarding is enable for port 21. Checking from cmd prompt will only confirm what you already know.
 
PS: Sorry forgot to add this in above, from the command line try performing a trace route, it will allow you to see where the problem occurs.
 
I talked with our isp and it seems they forwarded the ports but did not make changes to the firewall. it works fine now.
thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top