If you are using named pipes, most likely you'll see port
TCP 139 on the server side. Firewall folks don't like
openning TCP 139. It's not exclusively used by SQL named
pipes. It's a port for NetBIOS over TCP or NetBIOS session
service.
If NetBIOS over TCP is disabled on the server side, the
port on the server side would be TCP 445 used by Server
Message Blocks. You may have difficult getting the
firewall folks openning TCP 445 as well.
Linchi
[quoted text, click to view] >-----Original Message-----
>Guys,
>
>I'm having trouble communicating with one of my SQL
Servers within my
>Windows domain. The symptoms are that I can read a DTS
package but when I
>try to execute it or save it, I get an error saying that
DBNETLIB cannot
>find the server.
>
>I believe the problem is that my firewall allows the TCP
protocol to use
>port 1433, but the Named Pipes protocol's TCP ports in
the firewall are
>blocked.
>
>My question is, what port numbers does Named Pipes use
inside the TCP stack?
>
>Thanks in advance for your help.
>
>John
>
>
>
>.
Dear John, Ray, Linchi, and Kevin,
Thanks to everyone for responding. Your input was a great help.
Regards,
John Fredrickson
[quoted text, click to view] "John Fredrickson" <jafred@bellatlantic.net> wrote in message
news:AHJJb.22082$nK2.20490@nwrddc01.gnilink.net...
> Guys,
>
> I'm having trouble communicating with one of my SQL Servers within my
> Windows domain. The symptoms are that I can read a DTS package but when I
> try to execute it or save it, I get an error saying that DBNETLIB cannot
> find the server.
>
> I believe the problem is that my firewall allows the TCP protocol to use
> port 1433, but the Named Pipes protocol's TCP ports in the firewall are
> blocked.
>
> My question is, what port numbers does Named Pipes use inside the TCP
stack?
>
> Thanks in advance for your help.
>
> John
>
>
>
