RE: Remote Connection Problems via Cisco VPN over high speed inter

Your's was the first response to my post, so no one has helped me out yet and
I haven't resolved the problem other than going to older versions of the VPN
client (which causes other problems).

My ultimate solution is that I'm in the process of re-writing the
application in .NET which bypasses the problem by not using ODBC.
Unfortunately this will take some time before the full capability of my
application is ported.

Hopefully someone will have a solution that we can actually implement rather
than work around. Nice to know that I'm not the only one with the problem.
--
Ray


"Tigermikefl" wrote:

> We are having something similar. Did you find any answers? We upgraded
> using cisco vpn 4.6. vpn 5000 was working before.
> --
> Mike
>
> If data falls in the woods and nobody is there to see it ....... ?
>
>
> "rklaassen" wrote:
>
> > ODBC application cannot connect to the SQL Server database.
> > Error received: [Microsoft][ODBC SQL Server Driver]Timeout expired.
> > Error # is 20085 (which from articles on MSDN is a Remote Access Server
> > error).
> >
> > This problem occurs only for Remote Users connecting through our Cisco VPN
> > on a fast Internet connection. Dialup connections work fine. Sometimes
> > repeated attempts will eventually connect, but some users can't connect at
> > all. ALL other network functions (Outlook, file shares, intranet sites, etc)
> > work fine though the VPN connection -- only the ODBC application doesn't
> > work.
> >
> > This problem started several months ago so possibly some security update may
> > have affected these users. But we haven't found anything to rectify the
> > problem.
> >
> > The application accesses a SQL Server 7 database running on Windows NT4
> > server but the problem has been duplicated on a SQL Server 2000 database
> > running on Windows 2000 server. Clients are Windows 2000 and Windows XP
> > (with applicable service packs and security updates).
> >
> > I would appreciate any suggestions/help/solutions to the above problem.
> > Users are a bit angry about using dialup for the ERP app, while they can do
> > everything else at high speed.
> > --
> > Ray
.

Relevant Pages

  • Re: How to connect a workstation to SQL Server 2005 thru ODBC?
    ... and open the port in the Windows XP ... Welcome to the Getting Started with the Database Engine tutorial. ... Connecting to the Database Engine ... Either SQL Server Management Studio or Management Studio Express. ...
    (microsoft.public.sqlserver.connect)
  • Re: Cannot connect a remote sql server
    ... I too have written quite a bit about connecting. ... Hitchhiker's Guide to Visual Studio and SQL Server ... such as the server's firewall, SQL Server's remote connection setting, ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.adonet)
  • Use Single Sign on to connect to sql server
    ... connection in an excel file that connects using an odc file connecting using ... The logon account information that you configure here must match the logon ... Name: SQL Server ... If I'm connecting using a sql username, do i need to use the domain piece ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: Problem connectin SQL Server 2005
    ... > Have you configured the SQL Server 2005 to allow remote connections? ... > Welcome to the Getting Started with the Database Engine tutorial. ... Connecting to the Database Engine ... > Configuring a Fixed Port ...
    (microsoft.public.sqlserver.connect)
  • Re: Problem connectin SQL Server 2005
    ... Have you configured the SQL Server 2005 to allow remote connections? ... Welcome to the Getting Started with the Database Engine tutorial. ... Connecting to the Database Engine ... Configuring a Fixed Port ...
    (microsoft.public.sqlserver.connect)
Loading