Connecting Dynamic Port from Client

Hi all
I tried to connect to MSDE_SP3a using dynamic port from client machine
1.I set 0 to the port in server machine, using ServerNetworkUtility
2.I restart MSDE, and I see that port is configured new value(like 1500)
3.Now I boot isql utility from Client machine(installed SQL-DMO), and I send
'isql -S Server -U *** -P ***'
4.But that's failed!!!
I cheked:
1.I have already checked that TCP/IP is enabled in ClientNetworkUtility
2.And port number is DIFFERENT from the one coufigured in server
machine(like 1433)
3.I understand that UDP1434 negotiate with server machine about MSDE
listening port
4.So, I think that client machine may resolve port in dynamic
5.I cheked that WindowsFirewall is off
6.I cheked that UDP negotiation by Portqry.exe, and Portqry.exe returned
correct infomation
7.And I set the same port number as server machine to client machine, and
that was successful...
How can I make 'Dynamic port negotiation' successful?
and sorry for my poor English...
hi,
"Atchy" <bakedmind@.hotmail.com> ha scritto nel messaggio
news:%23snAFxKpEHA.3488@.TK2MSFTNGP12.phx.gbl
> Hi all
> I tried to connect to MSDE_SP3a using dynamic port from client machine
> 1.I set 0 to the port in server machine, using ServerNetworkUtility
> 2.I restart MSDE, and I see that port is configured new value(like
> 1500)
> 3.Now I boot isql utility from Client machine(installed SQL-DMO), and
> I send 'isql -S Server -U *** -P ***'
> 4.But that's failed!!!
> I cheked:
> 1.I have already checked that TCP/IP is enabled in
> ClientNetworkUtility
> 2.And port number is DIFFERENT from the one coufigured in server
> machine(like 1433)
> 3.I understand that UDP1434 negotiate with server machine about MSDE
> listening port
> 4.So, I think that client machine may resolve port in dynamic
> 5.I cheked that WindowsFirewall is off
> 6.I cheked that UDP negotiation by Portqry.exe, and Portqry.exe
> returned correct infomation
> 7.And I set the same port number as server machine to client machine,
> and that was successful...
> How can I make 'Dynamic port negotiation' successful?
> and sorry for my poor English...
dynamic port redirection is a feature that requires MDAC stack 2.6 at least
at the client level as well.. on the server this is not a problem as the
service pack 3a installs MDAC 2.7.1, but please check the client...
the service listening on UDP 1434 on the server (not on the clients) will
provide automatic redirection to the required port for each installed
instance, actually a small delay for named instance is due for that
overhead...
I'm not sure of the causes of your problem, but please, running regedit,
verify that the
HKLM\SOFTWARE\Microsoft\Microsoft SQL
Server\InstanceName\MSSQLServer\SuperSocketNetLib\ Tcp
TcpPort
and TcpDynamicPorts
have the same value...
if TcpDynamicPorts is blank then the port is static and not dynamic...
have you tried setting a fixed static port and creating an Alias (client
side) with Client Network Utilty (cliconfg.exe) pointing to that (fixed
port) MSDE instance?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||> dynamic port redirection is a feature that requires MDAC stack 2.6 at
> least
> at the client level as well.. on the server this is not a problem as the
> service pack 3a installs MDAC 2.7.1, but please check the client...
> the service listening on UDP 1434 on the server (not on the clients) will
> provide automatic redirection to the required port for each installed
> instance, actually a small delay for named instance is due for that
> overhead...
> I'm not sure of the causes of your problem, but please, running regedit,
> verify that the
> HKLM\SOFTWARE\Microsoft\Microsoft SQL
> Server\InstanceName\MSSQLServer\SuperSocketNetLib\ Tcp
> TcpPort
> and TcpDynamicPorts
> have the same value...
> if TcpDynamicPorts is blank then the port is static and not dynamic...
> have you tried setting a fixed static port and creating an Alias (client
> side) with Client Network Utilty (cliconfg.exe) pointing to that (fixed
> port) MSDE instance?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
I thank your response
I found the MS article:
823938 :How to use static and dynamic port allocation in SQL Server 2000
http://support.microsoft.com/default.aspx?kbid=823938
Dynamic port allocation
Only named instances of SQL Server can use the dynamic port allocation
process
That's mean normal instance(NOT named instance) of MSDE can not use dynamic
ports allocation?
I tried and failed in normal instance network
And I tried named instance network and that's successed...
The conclusion:
Normal instance of MSDE is not supported dymamic port allocation
That's really!?
|||hi,
"Atchy" <bakedmind@.hotmail.com> ha scritto nel messaggio
news:uMd$YBjpEHA.2636@.TK2MSFTNGP09.phx.gbl
> I found the MS article:
> 823938 :How to use static and dynamic port allocation in SQL Server
> 2000 http://support.microsoft.com/default.aspx?kbid=823938
> ----
--
> Dynamic port allocation
> Only named instances of SQL Server can use the dynamic port allocation
> process
> ----
--
> That's mean normal instance(NOT named instance) of MSDE can not use
> dynamic ports allocation?
> I tried and failed in normal instance network
> And I tried named instance network and that's successed...
> The conclusion:
> Normal instance of MSDE is not supported dymamic port allocation
> That's really!?
why should it be else?
dynamic redirection has been established as more instances (up to 16) can be
installed on the same server and, if the DEFAULT instance is listening on
TCP 1433, there should be a way to set connections without requiring an
Alias to be defined on the client side (each client) and defining a static
alternate port server side...
this is no more a viable solution on Windows XP sp2 as the Windows Firewall
requires a better security policy, so static redirection is again the way to
go, opening the desired port and defining Alias on the client side
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply