Registering a remote instance of MSDE

Hi..
I have been trying to register a remote instance..but have no success.
The MSDE instance is behind a firewall...So in the firewall im doing a port
fowarding.
The port that i have setup for forwarding is 1433 (TCP), is that correct?
i have installed the MSDE just like this:
setup SAPWD="MyPass" INSTANCENAME="MSDE" DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
Is there anything wrong?
Why i cant register that instance in my machine?
Thanks
hi Marcos,
Marcos Lommez wrote:
> Hi..
> I have been trying to register a remote instance..but have no success.
> The MSDE instance is behind a firewall...So in the firewall im doing
> a port fowarding.
> The port that i have setup for forwarding is 1433 (TCP), is that
> correct?
> i have installed the MSDE just like this:
> setup SAPWD="MyPass" INSTANCENAME="MSDE" DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> Is there anything wrong?
> Why i cant register that instance in my machine?
TCP 1433 should be wrong as you installed a named instance...
Microsoft only got 1 unique TCP/IP port for SQL Server
assigned by IANA, port TCP/IP 1433... but named instances never listen to
that port that is "reserved" for default instances... so Microsoft embedded
an additional service in order to allow dynamic ports assignemen/resolution
for named instance, and the MDAC stack has been modified as well to
integrate this feature (MDAC 2.6 and above)
for named instance you have 2 options... dynamic (default) or fixed static
port assignement..
loosely speaking, for dynamic port, when the specified instance starts, it
always searches for an unused port (actually it always uses the very same
port, if free)... the SQL Server Resolution Service, listening on UDP 1434
port, intercepts all remote connections to the instances, asks the instance
for it's used port, and redirects all connections to that specific port,
adding some little overhead to the traffic...
again, very very loosely speaking, the client makes a query, which is
reloaded by the MDAC stack to the appropriate network protocol [we are
talking about TCP/IP], that intiates the connection over a random tcp port
greater than 1024 to destination port; the listener service is the first
hand-shaker and intercepts the foreign call, queries the instance for it's
used port and negotiates a TCP/IP port for the 2 end points...
for a static assigned port, the listener on UDP 1434 port is not required,
but you have to map a server alias on each remote client pointing to the
correct fixed assigned port.. and again, the client intiates the connection
over a random tcp port greater than 1024 to destination port (say 1059). The
Subscriber should be allowed to make inbound (ANY) connections to
{say 1059} on a random port. The Publisher should be allowed to establish
outgoing connections to the subscriber from (ANY) to {say 1059}...
for Windows XP sp2 integrated Firewall closes all ports, you have to add an
exception for that in order to allow external access,
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
http://support.microsoft.com/?id=841249 ,
http://support.microsoft.com/default.aspx?kbid=839980
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks so much Andrea...
In my case the solution is to use a fixed port.
But how do i set a specific port to use?
Im using MSDE 2000 running on Win2k Server
Thanks again
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escreveu na mensagem
news:47np01Fg9pf2U1@.individual.net...
> hi Marcos,
> Marcos Lommez wrote:
> TCP 1433 should be wrong as you installed a named instance...
> Microsoft only got 1 unique TCP/IP port for SQL Server
> assigned by IANA, port TCP/IP 1433... but named instances never listen to
> that port that is "reserved" for default instances... so Microsoft
embedded
> an additional service in order to allow dynamic ports
assignemen/resolution
> for named instance, and the MDAC stack has been modified as well to
> integrate this feature (MDAC 2.6 and above)
> for named instance you have 2 options... dynamic (default) or fixed static
> port assignement..
> loosely speaking, for dynamic port, when the specified instance starts, it
> always searches for an unused port (actually it always uses the very same
> port, if free)... the SQL Server Resolution Service, listening on UDP 1434
> port, intercepts all remote connections to the instances, asks the
instance
> for it's used port, and redirects all connections to that specific port,
> adding some little overhead to the traffic...
> again, very very loosely speaking, the client makes a query, which is
> reloaded by the MDAC stack to the appropriate network protocol [we are
> talking about TCP/IP], that intiates the connection over a random tcp port
> greater than 1024 to destination port; the listener service is the first
> hand-shaker and intercepts the foreign call, queries the instance for it's
> used port and negotiates a TCP/IP port for the 2 end points...
> for a static assigned port, the listener on UDP 1434 port is not required,
> but you have to map a server alias on each remote client pointing to the
> correct fixed assigned port.. and again, the client intiates the
connection
> over a random tcp port greater than 1024 to destination port (say 1059).
The
> Subscriber should be allowed to make inbound (ANY) connections to
> {say 1059} on a random port. The Publisher should be allowed to establish
> outgoing connections to the subscriber from (ANY) to {say 1059}...
> for Windows XP sp2 integrated Firewall closes all ports, you have to add
an
> exception for that in order to allow external access,
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
> http://support.microsoft.com/?id=841249 ,
> http://support.microsoft.com/default.aspx?kbid=839980
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Marcos,
Marcos Lommez wrote:
> Thanks so much Andrea...
> In my case the solution is to use a fixed port.
> But how do i set a specific port to use?
> Im using MSDE 2000 running on Win2k Server
just run the Server Network Utility (svrnetcn.exe), select the TCP/IP
protocol and access it's properties.. the port currently use is there...
just type the port you want to use and confirm...
then you can access the registry value
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SuperSocketNetLib\Tcp
(for a default instance)
or
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\InstanceName\MSSQLServer\SuperSocketNetLib\ Tcp (for a named instance)
and check the
TcpDynamicPorts ...
it's value should be empty...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea Montanari wrote:
> hi Marcos,
> Marcos Lommez wrote:
> just run the Server Network Utility (svrnetcn.exe), select the TCP/IP
> protocol and access it's properties.. the port currently use is
> there... just type the port you want to use and confirm...
> then you can access the registry value
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SuperSocketNetLib\Tcp
> (for a default instance)
> or
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\InstanceName\MSSQLServer\SuperSocketNetLib\ Tcp (for a named
> instance) and check the
> TcpDynamicPorts ...
> it's value should be empty...
http://support.microsoft.com/default...b;en-us;823938
:-D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply