Michael Kizer
Oct 18th, 2000, 12:25 PM
I've got an application (VB 6) that uses a SQL Server database via an ODBC connection. Well, actually the VB app connects data bound components to an Access 97 database which has links to the ODBC DSN fro the SQL Server database (don't ask, I didn't write it, I just inhereted it).
The problem is that this application works fine from most locations in our network, but fails to connect at a few others. No error message is given, it just constantly pops up the SQL Server login dialog.
I checked the connectivity to the database through the ODBC control panel applet, and that works fine. What would be different about testing the ODBC connection via the control panel applet and from a VB app?
I thought it may be some sort of router or firewall issue, but apparently port 1433 (what the ODBC applet reports that it uses for SQL Server) is open. Maybe ODBC uses another port in addition to 1433?
Any suggestions?
The problem is that this application works fine from most locations in our network, but fails to connect at a few others. No error message is given, it just constantly pops up the SQL Server login dialog.
I checked the connectivity to the database through the ODBC control panel applet, and that works fine. What would be different about testing the ODBC connection via the control panel applet and from a VB app?
I thought it may be some sort of router or firewall issue, but apparently port 1433 (what the ODBC applet reports that it uses for SQL Server) is open. Maybe ODBC uses another port in addition to 1433?
Any suggestions?