How do I open port on Terminal server not running Windows firewall

I have Windows 2003 server acting as a terminal server. I need to open up TCP and UDP ports to my LAN for ports 1433 and 1434. I already know it is rejecting these ports from my other server. I don't have Windows Firewall running but it does say something called ipnat.sys is.
What is this and is this where I need to open ports? I need some step by step help on this one.
Thanks.
Thomas AnthonySecurity AdministratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

top_rungCommented:
Maybe TCP/IP filtering...
http://support.microsoft.com/kb/816792

0
Thomas AnthonySecurity AdministratorAuthor Commented:
I tried that. Thank you.
0
top_rungCommented:
Since this is likely SQL, are you sure it is listening on the ports?  

Netstat -a

Is the server listening?

Also, portqry from the target on both ports to see if it is being filtered.  Then investigate any devices (e.g. hardware firewalls) in between the two hosts.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Coast-ITCommented:
Are you sure that Windows firewall is disabled on all servers?  This is a windows firewall error.

what server do you want to open these ports to?  Can you telnet to them internally on the LAN?  

Try and telnet from a command prompt
start>run>cmd   -  

telnet myinternalip.local 1433
telnet myinternalip.local 1434

If they go to a black screen then the ports are opened.

Then try it from outside, if you can get to it, then it is down to the fact that something is blocking it from outside.  Check port forwarding rules on the router.

We need a better explanation of what your expected end result is, eg ;

Connect to terminal server from outside or inside
open ports required on another server for access from the terminal server
ports opened up on terminal server for application



0
Jannie van der WaltCommented:
perhaps check you c:\WINDOWS\system32\drivers\etc\services file for entries:

ms-sql-s         1433/tcp                           #Microsoft-SQL-Server
ms-sql-s         1433/udp                           #Microsoft-SQL-Server
ms-sql-m         1434/tcp                           #Microsoft-SQL-Monitor
ms-sql-m         1434/udp                           #Microsoft-SQL-Monitor
0
Thomas AnthonySecurity AdministratorAuthor Commented:
I have a program that uses these ports to talk to its clients. I tried the telnet from the inside and it doesn't connect. I have tried disabling the firewall service on the server which doesn't help either.
0
Thomas AnthonySecurity AdministratorAuthor Commented:
JannieinSA,
Am I to do this on the client or the server?
0
Thomas AnthonySecurity AdministratorAuthor Commented:
JannieinSA,
Those entries are in the client file.
0
top_rungCommented:
Does Netstat -a show "listening" on the server on that port?

0
Thomas AnthonySecurity AdministratorAuthor Commented:
Good call. No it doesn't. Should that be a service of the server program I installed on the server first?
0
top_rungCommented:
"I have a program that uses these ports to talk to its clients"

This program in on the server right?  If so, it must be configured to listen on the ports and obviously the program should be running.

0
Thomas AnthonySecurity AdministratorAuthor Commented:
They are telling me that if the server is blocking those ports because of it's firewall, it won't show up as listening. Is that correct? Again, I don't have a firewall running.
0
top_rungCommented:
"if the server is blocking those ports because of it's firewall, it won't show up as listening"

I don't believe that to be true.  Netstat will give you a list of processes/programs that are using a specific port regardless of a firewall.   That is, it doesn't care if there is a firewall blocking it or not, it is merely showing you what is being used by what.  Even this MS article uses Netstat and Tasklist to identify ports if you believe the Firewall might be blocking it and you want to add an exception..

http://support.microsoft.com/kb/875357

I can't test this at the moment, so maybe someone else can chime in with a definitive answer.


So to clarify, you are saying that you see NOTHING for port 1433 when running netstat?

Try this to filter things a bit...

netstat -ano | findstr :1433


Also, you are sure there is no firewall running?  What services did you stop?   Also, when you say "it does say something called ipnat.sys is", what is "It"?  What says that ipnat.sys is running?
 

Sorry to ask some simple questions, but if you need more help, then we need to make sure we are on the same page.


0
top_rungCommented:
Also, use portqry from another machine and test it.  Download portqry.exe on a remote computer, go to a command prompt and change to the directory where portqry.exe is.  Run the following command....

portqry -n ServersIPAddress -e 1433

If you get a result that says "FILTERED", it is a firewall/blocking issue.

If you get a result that says NOT LISTENING, then their is no program on the server listening on the port.

http://www.microsoft.com/downloads/details.aspx?familyid=89811747-c74b-4638-a2d5-ac828bdc6983&displaylang=en





0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Thomas AnthonySecurity AdministratorAuthor Commented:
Thank you. You are correct. Using the portqry program I am getting a response of NOT LISTENING.
You have been extrememly helpful and very quick to respond. I am grateful for your assistance.
0
top_rungCommented:
Anytime.  Good luck and contribute back whenever possible!

good luck....
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.