|
|
You're in the
sql server connect
group:When will port 445 be used by SQL Server?
sql server connect:
You can have port 445 used when the connection is made
through named pipes. Named pipes will use NetBios. NetBios requests also use ports 137-139. -Sue On Wed, 23 Jun 2004 10:57:01 -0700, "Peter" [quoted text, click to view] <Peter@discussions.microsoft.com> wrote:
>I'm using Port Reporter to check what ports are being used between client machine and SQL Server machine. I cannot find any entry using port 445 except an entry related the loopback address 127.0.0.1. But I see port 139 being used between client machine and SQL Server machine.
Port 445 is used by MS Directory Services. You computer should have a
file named 'services' (no extension) that lists ports and their aliases. These give some hint as to the use of the ports. Its likely that the client uses 445 to find servers. See the following for more help: http://support.microsoft.com/default.aspx?kbid=814130 and http://support.microsoft.com/?id=287932 Lou Arnold On Wed, 23 Jun 2004 19:43:45 -0600, Sue Hoegemeier [quoted text, click to view] <Sue_H@nomail.please> wrote:
>You can have port 445 used when the connection is made >through named pipes. >Named pipes will use NetBios. NetBios requests also use >ports 137-139. > >-Sue > >On Wed, 23 Jun 2004 10:57:01 -0700, "Peter" ><Peter@discussions.microsoft.com> wrote: > >>I'm using Port Reporter to check what ports are being used between client machine and SQL Server machine. I cannot find any entry using port 445 except an entry related the loopback address 127.0.0.1. But I see port 139 being used between client machine and SQL Server machine. >
Hi Sue,
Under what situation I will see port 445 being used instead of port 139 if the only enabled protocol is Named Pipes. My understanding is that both ports are used by SQL Server using Named Pipes. Thank you, Peter [quoted text, click to view] "Sue Hoegemeier" wrote:
> You can have port 445 used when the connection is made > through named pipes. > Named pipes will use NetBios. NetBios requests also use > ports 137-139. > > -Sue > > On Wed, 23 Jun 2004 10:57:01 -0700, "Peter" > <Peter@discussions.microsoft.com> wrote: > > >I'm using Port Reporter to check what ports are being used between client machine and SQL Server machine. I cannot find any entry using port 445 except an entry related the loopback address 127.0.0.1. But I see port 139 being used between client machine and SQL Server machine. >
Hi Lou,
I'm looking for when the server will use port 445 instead of port 139. I don't know what is the differenece between these 2 ports. Thank you, Peter [quoted text, click to view] "Lou Arnold" wrote:
> Port 445 is used by MS Directory Services. You computer should have a > file named 'services' (no extension) that lists ports and their > aliases. These give some hint as to the use of the ports. > > Its likely that the client uses 445 to find servers. > > See the following for more help: > > http://support.microsoft.com/default.aspx?kbid=814130 > > and > > http://support.microsoft.com/?id=287932 > > Lou Arnold > > On Wed, 23 Jun 2004 19:43:45 -0600, Sue Hoegemeier > <Sue_H@nomail.please> wrote: > > >You can have port 445 used when the connection is made > >through named pipes. > >Named pipes will use NetBios. NetBios requests also use > >ports 137-139. > > > >-Sue > > > >On Wed, 23 Jun 2004 10:57:01 -0700, "Peter" > ><Peter@discussions.microsoft.com> wrote: > > > >>I'm using Port Reporter to check what ports are being used between client machine and SQL Server machine. I cannot find any entry using port 445 except an entry related the loopback address 127.0.0.1. But I see port 139 being used between client machine and SQL Server machine. > > >
You won't see 445 instead of 139. You'd see both.
-Sue On Fri, 25 Jun 2004 20:01:02 -0700, "Peter" [quoted text, click to view] <Peter@discussions.microsoft.com> wrote:
>Hi Sue, > >Under what situation I will see port 445 being used instead of port 139 if the only enabled protocol is Named Pipes. My understanding is that both ports are used by SQL Server using Named Pipes. > >Thank you, > >Peter > >"Sue Hoegemeier" wrote: > >> You can have port 445 used when the connection is made >> through named pipes. >> Named pipes will use NetBios. NetBios requests also use >> ports 137-139. >> >> -Sue >> >> On Wed, 23 Jun 2004 10:57:01 -0700, "Peter" >> <Peter@discussions.microsoft.com> wrote: >> >> >I'm using Port Reporter to check what ports are being used between client machine and SQL Server machine. I cannot find any entry using port 445 except an entry related the loopback address 127.0.0.1. But I see port 139 being used between client machine and SQL Server machine. >> >>
Hi Sue,
I'm using Port Reporter and TCPView to check what ports are being used. I can only find port 139 being used in communication between client and server. Port 445 is open since I can telnet to it and net config server also show NetbiosSmb as active. 1. Besides Names Pipes, do I need to enable other network libraries on client and server? 2. Which network protocols should be installed on both client and server? 3. What other ports (e.g. 135, 137,138,139,1433, 1434) besides port 445 must be opened? Thank you. [quoted text, click to view] "Sue Hoegemeier" wrote:
> You won't see 445 instead of 139. You'd see both. > > -Sue > > On Fri, 25 Jun 2004 20:01:02 -0700, "Peter" > <Peter@discussions.microsoft.com> wrote: > > >Hi Sue, > > > >Under what situation I will see port 445 being used instead of port 139 if the only enabled protocol is Named Pipes. My understanding is that both ports are used by SQL Server using Named Pipes. > > > >Thank you, > > > >Peter > > > >"Sue Hoegemeier" wrote: > > > >> You can have port 445 used when the connection is made > >> through named pipes. > >> Named pipes will use NetBios. NetBios requests also use > >> ports 137-139. > >> > >> -Sue > >> > >> On Wed, 23 Jun 2004 10:57:01 -0700, "Peter" > >> <Peter@discussions.microsoft.com> wrote: > >> > >> >I'm using Port Reporter to check what ports are being used between client machine and SQL Server machine. I cannot find any entry using port 445 except an entry related the loopback address 127.0.0.1. But I see port 139 being used between client machine and SQL Server machine. > >> > >> >
Hi Lou,
I have looked at the services. It basically lists out what port is for in a simple way. I have tried to disable File and Printer Sharing but it only blocks me from registering the server on the client machine instead of using port 445. I want to find out why I cannot just enable port 445 only to make SQL Server to communicate with the client machine. I never look into this area (port) before. But now with the coming service packs for Windows XP and Windows 2003, it is important to understand what ports need to be opened. Peter [quoted text, click to view] "Lou Arnold" wrote:
> Peter, > I refer you again to the services file similar to: > C:\WINNT\system32\drivers\etc\services > The aliases for ports 137, 138, and 139 suggest that they are used for > NetBios communications over TCP/IP. If you diable File and Printer > Sharing, these ports will not be used, since File and Printer Sharing > is done via NetBios (I believe from what I've read). > > Lou Arnold > Ottawa Canada > > On Fri, 25 Jun 2004 20:01:02 -0700, "=?Utf-8?B?UGV0ZXI=?=" > <Peter@discussions.microsoft.com> wrote: > > >Hi Sue, > > > >Under what situation I will see port 445 being used instead of port 139 if the only enabled protocol is Named Pipes. My understanding is that both ports are used by SQL Server using Named Pipes. > > > >Thank you, > > > >Peter > > > >"Sue Hoegemeier" wrote: > > > >> You can have port 445 used when the connection is made > >> through named pipes. > >> Named pipes will use NetBios. NetBios requests also use > >> ports 137-139. > >> > >> -Sue > >> > >> On Wed, 23 Jun 2004 10:57:01 -0700, "Peter" > >> <Peter@discussions.microsoft.com> wrote: > >> > >> >I'm using Port Reporter to check what ports are being used between client machine and SQL Server machine. I cannot find any entry using port 445 except an entry related the loopback address 127.0.0.1. But I see port 139 being used between client machine and SQL Server machine. > >> > >> >
Peter,
I refer you again to the services file similar to: C:\WINNT\system32\drivers\etc\services The aliases for ports 137, 138, and 139 suggest that they are used for NetBios communications over TCP/IP. If you diable File and Printer Sharing, these ports will not be used, since File and Printer Sharing is done via NetBios (I believe from what I've read). Lou Arnold Ottawa Canada On Fri, 25 Jun 2004 20:01:02 -0700, "=?Utf-8?B?UGV0ZXI=?=" [quoted text, click to view] <Peter@discussions.microsoft.com> wrote:
>Hi Sue, > >Under what situation I will see port 445 being used instead of port 139 if the only enabled protocol is Named Pipes. My understanding is that both ports are used by SQL Server using Named Pipes. > >Thank you, > >Peter > >"Sue Hoegemeier" wrote: > >> You can have port 445 used when the connection is made >> through named pipes. >> Named pipes will use NetBios. NetBios requests also use >> ports 137-139. >> >> -Sue >> >> On Wed, 23 Jun 2004 10:57:01 -0700, "Peter" >> <Peter@discussions.microsoft.com> wrote: >> >> >I'm using Port Reporter to check what ports are being used between client machine and SQL Server machine. I cannot find any entry using port 445 except an entry related the loopback address 127.0.0.1. But I see port 139 being used between client machine and SQL Server machine. >> >>
Hi Lou,
I'm testing this in Windows Firewall of Windows XP SP2 RC2. Thank you for the links but I have read all those links for the past few days to understand more about port 445 and 139. I have tried to disable NetBIOS over TCP/IP in SQL Servers residing in Windows 2000 and Windows XP. But as soon as I do that, I cannot register using Named Pipes. Thank you for your help. [quoted text, click to view] "Lou Arnold" wrote:
> To control ports, one needs a firewall. So either your Windows OS has > a built in firewall or you have one separate from the operating > system. > > Firewalls rules often allow ports to be enabled for a combination of > certain applications, for direction, for protocol type, and for a > destination port. However, I am not familiar enough with port 445 use > to tell you how to configure it. > > Here are some atricles that may help: > http://grc.com/port_445.htm > http://ntsecurity.nu/papers/port445/ > http://www.linklogger.com/TCP445.htm > http://www.petri.co.il/what_is_port_445_in_w2kxp.htm > > > On Sun, 27 Jun 2004 22:18:01 -0700, "=?Utf-8?B?cGV0ZXI=?=" > <peter@discussions.microsoft.com> wrote: > > >Hi Lou, > > > >I have looked at the services. It basically lists out what port is > >for in a simple way. I have tried to disable File and Printer Sharing > >but it only blocks me from registering the server on the client machine > >instead of using port 445. I want to find out why I cannot just enable > >port 445 only to make SQL Server to communicate > >with the client machine. I never look into this area (port) before. > >But now with the coming service packs for Windows XP and Windows > >2003, it is important to understand what ports need to be opened. > > > >Peter > > > >"Lou Arnold" wrote: > > > >> Peter, > >> I refer you again to the services file similar to: > >> C:\WINNT\system32\drivers\etc\services > >> The aliases for ports 137, 138, and 139 suggest that they are used for > >> NetBios communications over TCP/IP. If you diable File and Printer > >> Sharing, these ports will not be used, since File and Printer Sharing > >> is done via NetBios (I believe from what I've read). > >> > >> Lou Arnold > >> Ottawa Canada > >> > >> On Fri, 25 Jun 2004 20:01:02 -0700, "=?Utf-8?B?UGV0ZXI=?=" > >> <Peter@discussions.microsoft.com> wrote: > >> > >> >Hi Sue, > >> > > >> >Under what situation I will see port 445 being used instead of port 139 if the only enabled protocol is Named Pipes. My understanding is that both ports are used by SQL Server using Named Pipes. > >> > > >> >Thank you, > >> > > >> >Peter > >> > > >> >"Sue Hoegemeier" wrote: > >> > > >> >> You can have port 445 used when the connection is made > >> >> through named pipes. > >> >> Named pipes will use NetBios. NetBios requests also use > >> >> ports 137-139. > >> >> > >> >> -Sue > >> >> > >> >> On Wed, 23 Jun 2004 10:57:01 -0700, "Peter" > >> >> <Peter@discussions.microsoft.com> wrote: > >> >> > >> >> >I'm using Port Reporter to check what ports are being used between client machine and SQL Server machine. I cannot find any entry using port 445 except an entry related the loopback address 127.0.0.1. But I see port 139 being used between client machine and SQL Server machine. > >> >> > >> >> > >> > >> >
To control ports, one needs a firewall. So either your Windows OS has
a built in firewall or you have one separate from the operating system. Firewalls rules often allow ports to be enabled for a combination of certain applications, for direction, for protocol type, and for a destination port. However, I am not familiar enough with port 445 use to tell you how to configure it. Here are some atricles that may help: http://grc.com/port_445.htm http://ntsecurity.nu/papers/port445/ http://www.linklogger.com/TCP445.htm http://www.petri.co.il/what_is_port_445_in_w2kxp.htm On Sun, 27 Jun 2004 22:18:01 -0700, "=?Utf-8?B?cGV0ZXI=?=" [quoted text, click to view] <peter@discussions.microsoft.com> wrote:
>Hi Lou, > >I have looked at the services. It basically lists out what port is >for in a simple way. I have tried to disable File and Printer Sharing >but it only blocks me from registering the server on the client machine >instead of using port 445. I want to find out why I cannot just enable >port 445 only to make SQL Server to communicate >with the client machine. I never look into this area (port) before. >But now with the coming service packs for Windows XP and Windows >2003, it is important to understand what ports need to be opened. > >Peter > >"Lou Arnold" wrote: > >> Peter, >> I refer you again to the services file similar to: >> C:\WINNT\system32\drivers\etc\services >> The aliases for ports 137, 138, and 139 suggest that they are used for >> NetBios communications over TCP/IP. If you diable File and Printer >> Sharing, these ports will not be used, since File and Printer Sharing >> is done via NetBios (I believe from what I've read). >> >> Lou Arnold >> Ottawa Canada >> >> On Fri, 25 Jun 2004 20:01:02 -0700, "=?Utf-8?B?UGV0ZXI=?=" >> <Peter@discussions.microsoft.com> wrote: >> >> >Hi Sue, >> > >> >Under what situation I will see port 445 being used instead of port 139 if the only enabled protocol is Named Pipes. My understanding is that both ports are used by SQL Server using Named Pipes. >> > >> >Thank you, >> > >> >Peter >> > >> >"Sue Hoegemeier" wrote: >> > >> >> You can have port 445 used when the connection is made >> >> through named pipes. >> >> Named pipes will use NetBios. NetBios requests also use >> >> ports 137-139. >> >> >> >> -Sue >> >> >> >> On Wed, 23 Jun 2004 10:57:01 -0700, "Peter" >> >> <Peter@discussions.microsoft.com> wrote: >> >> >> >> >I'm using Port Reporter to check what ports are being used between client machine and SQL Server machine. I cannot find any entry using port 445 except an entry related the loopback address 127.0.0.1. But I see port 139 being used between client machine and SQL Server machine. >> >> >> >> >> >>
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |