Tuesday, February 14, 2012
Client connect with static Port (over Dynamic)
We have a server in our DMZ which need to talk (SECURLEY) with SQL 2000 i
have done this...by configuring a really tight rule on our firewall. This
trafic only needs to be inbound to SQL.
However it would appear that though the SQL Server listenes on port the
client 1433 The clien port which is posting the info to SQL is Dynamic.
Can i specify that my Client only connect using a pre specified port which i
can then allow in my Firewall rule...
Kind Regards
Paul
Depends on the client - how the client is connecting, from
where, how many, what app, etc. You can use the client
network utility and create an alias for the server. You can
set the port in the alias you create.
Or you can specify the port in the connection string - set
the data source to the IP or server name followed by a comma
and then the port number:
Data Source=xxx.xxx.xxx.xxx,1433;
-Sue
On Fri, 2 Feb 2007 04:50:00 -0800, PK
<PK@.discussions.microsoft.com> wrote:
>Hi all
>We have a server in our DMZ which need to talk (SECURLEY) with SQL 2000 i
>have done this...by configuring a really tight rule on our firewall. This
>trafic only needs to be inbound to SQL.
>However it would appear that though the SQL Server listenes on port the
>client 1433 The clien port which is posting the info to SQL is Dynamic.
>Can i specify that my Client only connect using a pre specified port which i
>can then allow in my Firewall rule...
>Kind Regards
>Paul
Sunday, February 12, 2012
Client can not connect to SQL Express - The Solution
Hi,
When I try to connect to SQL Express from another computer I get error 26.
The setup is as follows:
Server is Windows XP Pro, Firewall turned off.
Client is Windows XP Pro, Firewall turned off.
Both computers are on the same workgroup, no domain or other servers on the network.
The server is configured for network: protocols enabled, browser running.
The client has MS SQL Server Management Studio Express installed. When I try to connect the SSMSE finds the SQL Express on the server (using the Browse for more – Network server option), but the connection fails with error 26.
When I try to connect from MS Access 2003 I get the same error.
Thank for any help
Amihy
I found this link http://www.datamasker.com/SSE2005_NetworkCfg.htm maybe this will help you out.|||Thanks for the link, it helped me understand that all my SQL settings are OK.
So I started to think about the network and at last found that NetBios over TCP\IT was disabled. It did not bother me before since the local network works with NetBEUI protocol.
Once I enabled TCP\IP over NetBios in Local Area Connection-Properties-TCP\IP properties-General-advanced-wins, The client immediatly connected to the server.
Client can not connect to SQL Express
Hi,
When I try to connect to SQL Express from another computer I get error 26.
The setup is as follows:
Server is Windows XP Pro, Firewall turned off.
Client is Windows XP Pro, Firewall turned off.
Both computers are on the same workgroup, no domain or other servers on the network.
The server is configured for network: protocols enabled, browser running.
The client has MS SQL Server Management Studio Express installed. When I try to connect the SSMSE finds the SQL Express on the server (using the Browse for more – Network server option), but the connection fails with error 26.
When I try to connect from MS Access 2003 I get the same error.
Thank for any help
Amihy
I found this link http://www.datamasker.com/SSE2005_NetworkCfg.htm maybe this will help you out.|||Thanks for the link, it helped me understand that all my SQL settings are OK.
So I started to think about the network and at last found that NetBios over TCP\IT was disabled. It did not bother me before since the local network works with NetBEUI protocol.
Once I enabled TCP\IP over NetBios in Local Area Connection-Properties-TCP\IP properties-General-advanced-wins, The client immediatly connected to the server.