edie209 Posted June 22, 2006 Posted June 22, 2006 I need to open a port on a Windows 2003 R2 server, at the moment only 8 ports are open 53 80 88 110 135 139 445 and 1025. At first I thought easy I will do it in the Microsoft software firewall but no its turned off and still the ports are blocked. So I thought maybe tcp/ip filtering, but again even opening them wide I only get the above eight ports open. I have Macffee V8 installed and that blocks ports so I removed it completly and still the ports are blocked. Is there anywhere I may have missed? Is there maybe a registy entry? I am using Advanced port scanner v1.2 to check the ports.
OutToLunch Posted June 22, 2006 Posted June 22, 2006 Do you actually have something listening on the port you're trying to open? If you're scanning a port that's unblocked but has nothing listening on it, most freebie port scanners generally won't recognise the difference between "open but nothing listening" and closed. Only have my SBS 2003 install to hand for reference so this may be completely off, but to open the port I needed for my SSH server the route is "Routing and Remote Access" from Administrative Tools -> Server Name -> IP Routing -> NAT/Basic Firewall -> Pick the appropriate LAN interface -> "Services and Ports"
edie209 Posted June 22, 2006 Author Posted June 22, 2006 Thanks for the reply OutToLunch, unfortuanatly I don't have routing and remote access enabled on this server.
webman Posted June 22, 2006 Posted June 22, 2006 If the server does not have a firewall running at all, then any application that opens a TCP port will be open anyway. If you are running an application that should open a port that is not showing in that list, it usually indicates a problem with the program. Your portscan of the server shows that those ports are open - an application is listening on those ports.
edie209 Posted June 23, 2006 Author Posted June 23, 2006 Ok still having a problem with this server on port 25 I have trawled the web and found lots of info about checking ports etc, and I have come to the conclusion it must be blocked because I can't telnet to the port but I can to 110.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now