Please help -- So stuck now -- Cant connect to sql from external source

Hi all,

I am having real problems allowing a client to connect to sql 2000
through enterprise manager.. I have tried all sorts but to no avail:

From our local network all works fine.. Using the adsl line.. Even if
i try and connect to the external IP and use login details..(As
opposed to connecting local and using windows accounts) I can ping and
telnet the server and port.

The server is behind a firewall so i opened up port 1433 and port
1434(? is it needed).. To replicate the client i took the same laptop
home that i use to connect in the office.. However using the exact
same config on my dial up at home i can ping the server but cannot
telnet onto port 1433.. I think that this is the vital missing step
but do not know hpw to resolve it..

Any ideas anyone

Cheers
Antanthonykallay@.hotmail.com (Anthony) wrote in message news:<77112a1e.0309040245.6d426db9@.posting.google.com>...
> Hi all,
> I am having real problems allowing a client to connect to sql 2000
> through enterprise manager.. I have tried all sorts but to no avail:
> From our local network all works fine.. Using the adsl line.. Even if
> i try and connect to the external IP and use login details..(As
> opposed to connecting local and using windows accounts) I can ping and
> telnet the server and port.
> The server is behind a firewall so i opened up port 1433 and port
> 1434(? is it needed).. To replicate the client i took the same laptop
> home that i use to connect in the office.. However using the exact
> same config on my dial up at home i can ping the server but cannot
> telnet onto port 1433.. I think that this is the vital missing step
> but do not know hpw to resolve it..
> Any ideas anyone
> Cheers
> Ant

This KB article explains what firewall configuration is required:

http://support.microsoft.com/defaul...kb;en-us;287932

Simon

PLEASE HELP - Remote connection to SQL Server 2005 fall over after 100 seconds

Hi,
I am remotely accessing SQL Server 2005 using an import manager,
through a windows authentication login.
I start the loading, it connects perfectly at first but at the 100
second mark I get the error
"[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server d
oes
not exist or access denied" it then reconnects and continues to load
but really slowly. So it looks like a timeout is occuring at 100
seconds
I have tried to change the connection timeout, the execution timeout
and the remote login timeout, nothing stops this happening.
The version of sql I am using is a SQL Server 2005 Evaluation edition.
Can anyone help?
Thanks
ArchanaIs there some reason you're using the ODBC driver to access SQL Server
instead of a native provider?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
<archanapatelwhite@.googlemail.com> wrote in message
news:1174608028.525589.151310@.e65g2000hsc.googlegroups.com...
> Hi,
> I am remotely accessing SQL Server 2005 using an import manager,
> through a windows authentication login.
> I start the loading, it connects perfectly at first but at the 100
> second mark I get the error
> "[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server
does
> not exist or access denied" it then reconnects and continues to load
> but really slowly. So it looks like a timeout is occuring at 100
> seconds
> I have tried to change the connection timeout, the execution timeout
> and the remote login timeout, nothing stops this happening.
> The version of sql I am using is a SQL Server 2005 Evaluation edition.
> Can anyone help?
> Thanks
> Archana
>|||Hi Bill
The loading is going through a third party import manager, they must
be setting the ODBC driver to access SQL Server.
However when the company who wrote the import manager test it in their
environment replicating what I do they have no problems and it loads
fine
Thanks
Archana