Does WInServ 2003 block ports 3351 or 1583

If so, how do I make it stop?

I have a program running on this server attempting to connect to an SQL
database on another non windows machine. Everything seems to be OK, but
no TCP/IP connection is seen. I can ping it. the only thing I can find
in the KB is a reference to an older version of MSSQL not compatible
with 2003, and those ports, (whatever they are) being blocked by 2003
for "security purposes."

Are those the ports that are blocked? IF so, how do I unblock them?

I don't think any ports are blocked on Windows 2003 unless the built in ICF firewall
is enabled and event then only inbound traffic is managed. If you are using ICF you
can enable logging for it and look for dropped packets. Some processes such as RPC
can be difficult to use through a firewall. So check your firewall logs and
temporally disable the ICF firewall if it is enabled and you have other protection
from the internet. Tcp/ip filtering if enabled on a network adapter can also block
traffic. Netstat -ano can help show port use and associated processes and something
like the free TCPView is a great GUI tool for such. A packet sniffer such as Ethereal
may be needed for more deailed analysis of what is going on between the two computers
including ports being used. --- Steve

http://www.sysinternals.com/ntw2k/source/tcpview.shtml


"fred" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> If so, how do I make it stop?
>
> I have a program running on this server attempting to connect to an SQL
> database on another non windows machine. Everything seems to be OK, but
> no TCP/IP connection is seen. I can ping it. the only thing I can find
> in the KB is a reference to an older version of MSSQL not compatible
> with 2003, and those ports, (whatever they are) being blocked by 2003
> for "security purposes."
>
> Are those the ports that are blocked? IF so, how do I unblock them?
>
>
>
>

Thanx for the response, The tools you suggested may help.