Windows DNA App Connection Problem

[krshaikh]

Hi,

I am trying to connect my windows dna based vb application to a SQL Server 2000 via Internet. The Static IP is our web server and we have couple of web sites running quiet fine on it. The problem is that the Static IP is behind wingate. It doesn't cause any problems for the web site access but for my VB application it has become a headache. I have defined a new TCP/IP port 28 in wingate and mapped it to the database server of my internal network running on IP address 192.168.0.4:1434. I have tried port 1433 but no luck. SQL Server listens to client requests on port 1434.

Wingate has not shown any errors and the service is running fine. I can't remove wingate for security reasons. After reading all the documentation I could find in MSDN this was the best I could do. I am still unable to connect my Vb application to the remote server. Please see if anybody can help.

Thanks and regards,

- krshaikh -

 

[Norris68]

If I understand you correctly, you are trying to Access a SQL server through a firewall? You will need to change the network library from the default Named Pipes to TCP/IP transport.

See Microsoft Knowledgebase article Q238949

HOWTO: Set the SQL Server Network Library in an ADO Connection String (Summary)

SQL Server allows you to use the following network libraries when establishing a connection. They are:
dbnmpntw - Win32 Named Pipes
dbmssocn - Win32 Winsock TCP/IP
dbmsspxn - Win32 SPX/IPX
dbmsvinn - Win32 Banyan Vines
dbmsrpcn - Win32 Multi-Protocol (Windows RPC)

The connection string:
"Provider=MSDASQL.1;Persist Security Info=False;User ID=sa;Extended Properties="DSN=yourdatasourcename;UID=sa;DATABASE=pubs;Network=dbmssocn";Initial Catalog=pubs"
connects to SQL Server through the MSDASQL provider using the TCP/IP network library.

This is essential if you are trying to push an ADO connection through a firewall.

 

[krshaikh]

Thanks Norris.