ODBC error when WINGATE server is down

[dg21]

Hi All,

I need help urgent. We have sql database server and all my client have access. After installing Wingate server on a separate box, Now all my clients accessing sql server having odbc error when my wingate server is down. We wait for wingate to start before clients connect to sql server.

To give some idea, Only selected clients have internet access and proxy's IP configured to their computer. And majority of sql clients are not configured to use proxy. I don't know why they can't access sql server if wingate server is down since proxy IP is not configured on each client's network settings.They should not pass thru proxy server right?

What will I do?

Thanks

[logan]

If the clients are failing to connect to the ODBC server while WinGate is down, that indicates that the clients are connecting to ODBC through WinGate. To solve the problem, you need to ensure that connections to the ODBC server are made directly, rather than through WinGate.

How are your clients connecting through WinGate? I.e. are they using NAT, the WinGate Internet Client, or purely proxies?
What application on the client is talking to the ODBC server. Is it using a user or system DSN for instance?

[dg21]

Only selected clients are using wingate proxy. Not all my client are configured to use internet, so no wingate configuration are set to them at all. Only its local IP and DNS (IP of company domain) are set. I only put wingate IP as gateway & DNS to clients that I want to have internet access. Static IP to internet users, and DHCP to clients that doesn't have internet. I believe that wingate is pure proxy only. I didnt install WGIC on any client.

We have our own SQL database server. Each client has configured directly connected. All users are authenticated by local domain.

[logan]

In that case, I can't see how stopping the WinGate engine could prevent your clients from connecting to the ODBC server unless they were connecting through the proxy. If that was the case, you should be able to see the client conenctions to the ODBC server in WinGate's activity monitoring tab.

If you perform a tracert to the ODBC server from the client, does the results show that you are connecting directly to the ODBC server, or do they show that you are connecting through the WinGate server first?