sql server connect: How do I find out whats blocking port 1433? -- sql server connect

Re: How do I find out whats blocking port 1433?

Sue Hoegemeier
3/27/2007 8:32:28 PM

How do you know it's an issue with a blocked port?
If you are receiving an error, post the exact error number
and all details of the message.

-Sue

On Tue, 27 Mar 2007 19:04:07 -0700, KenRoy
[quoted text, click to view]

Re: How do I find out whats blocking port 1433?

TheSQLGuru
3/28/2007 12:00:00 AM

Are you sure you have TCP/IP enabled (and configured for port 1433)? Try
enabling Named Pipes and specify that in an alias and try to connect with QA
that way.

You can use the DOS tracert command to check paths from one ip point to
another.

--
TheSQLGuru
President
Indicium Resources, Inc.

[quoted text, click to view]

Re: How do I find out whats blocking port 1433?

KenRoy
3/28/2007 6:56:01 AM

Yes, I am sure it is enabled for port 1433.

[quoted text, click to view]

Re: How do I find out whats blocking port 1433?

KenRoy
3/28/2007 6:56:02 AM

Tried to connect with Telnet (telnet localhost 1433) and it say's it blocked.

[quoted text, click to view]

Re: How do I find out whats blocking port 1433?

Jarrod Robinson
4/6/2007 10:33:11 AM

I have been trying to solve this problem myself over the last three days
having moved to a new dedicated server with a new host.

Old server was Win2k3 SP1
New server is Win2k3 SP2

I found that the IP Security policy was, by default, set to drop all
packets to 1433\1434.

Add the IP Security Policy snap in to MMC and you'll find it.

This change is in addition to configuring windows firewall.

Jarrod.

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server connect group.