Connecting to SQL Server 2000 thru a VPN?

Is this even possible?
I'm coding a VB.NET WinForms app and an ASP.NET app that will access a MS
SQL 2000 Server. I've been told that when I move into a "production"
environment that I must go thru a VPN. I'm no VPN expert, but this doesn't
make much sense to me especially since the remote clients running my VB.NET
WinForms app may not have teh VPN setup.
If VPN can be used as a tunnel to access a SQL 2000 Server, can someone tell
me what needs to be in place on the client side and what would I use for a
connection string to get to the SQL 2000 Server thru the VPN.
I can't find any info on MSDN that even mentions how to connect to a SQL
2000 Server thru VPN.
Thanks, Rob.
Hi Rob,
The VPN session needs to be established prior to executing your VB.NET
app. There's not a specific connection string to do this.
Here's a sample kb article on how to setup a VPN with our firewall server ,
ISA Server.
837355 How to configure a VPN server by using Internet Security and
http://support.microsoft.com/?id=837355
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connecting to SQL 2005 Server via VPN

Hi all,
I am unable to connect to SQL2005 server using the Management Studio. i can
however connect to SQL2000 using EM. Has anyone else encoutered this issue?
if so could you please share the solution? what is ti that i need to enable
on the firewall?
Thanks
JoresIs SQL Server 2005 enabled for remote connections?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"joresm" <joresm@.hotmail.com> wrote in message
news:ODgXkoKaGHA.1220@.TK2MSFTNGP02.phx.gbl...
> Hi all,
> I am unable to connect to SQL2005 server using the Management Studio. i
> can however connect to SQL2000 using EM. Has anyone else encoutered this
> issue? if so could you please share the solution? what is ti that i need
> to enable on the firewall?
> Thanks
> Jores
>|||Yes, it is enabled and the Browser sevice is also running. i canconnect to
it using the query analyzer. the only problem is with Management studio.
Thanks
Jores
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uBvNIgLaGHA.1348@.TK2MSFTNGP05.phx.gbl...
> Is SQL Server 2005 enabled for remote connections?
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "joresm" <joresm@.hotmail.com> wrote in message
> news:ODgXkoKaGHA.1220@.TK2MSFTNGP02.phx.gbl...
>|||Hi I have experienced this problem also. Spent best part of a day trying to
resolve this to no avail. We have a VPN connection to our data center. The
database server has an instance of SQL 2000 which runs fine locally and
remotely from my desk. Recently we installed SQL 2005 and want to migrate
stuff to this new named instance. I can connect to the database fine locally
(on the database server itself and from other colocated machines (via
ADO.net). However I cannot access SQL 2005 over the VPN connection using
either ADO.net test app or SQL Management Studio. Is there some kind of port
blocking going on?
I don't know anything about Named Pipes, but I've tried the SQL
Configuration tool as suggested in some articles and have tried setting the
port to 1433 and turning of SQL 2000 to no avail. Would the VPN somehow be
blocking some ports - it appears that way, but my administrator assures me
that I should have full spectrum of ports available. WHATS GOING ON' Is the
SQL browser getting blocked or what? What button do I need to push to get
access to my database server from my development machine located over the
VPN?
Thanks Rob
"joresm" wrote:

> Yes, it is enabled and the Browser sevice is also running. i canconnect to
> it using the query analyzer. the only problem is with Management studio.
> Thanks
> Jores
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uBvNIgLaGHA.1348@.TK2MSFTNGP05.phx.gbl...
>
>

Connecting to SQL 2005 Server via VPN

Hi all,
I am unable to connect to SQL2005 server using the Management Studio. i can
however connect to SQL2000 using EM. Has anyone else encoutered this issue?
if so could you please share the solution? what is ti that i need to enable
on the firewall?
Thanks
JoresIs SQL Server 2005 enabled for remote connections?
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"joresm" <joresm@.hotmail.com> wrote in message
news:ODgXkoKaGHA.1220@.TK2MSFTNGP02.phx.gbl...
> Hi all,
> I am unable to connect to SQL2005 server using the Management Studio. i
> can however connect to SQL2000 using EM. Has anyone else encoutered this
> issue? if so could you please share the solution? what is ti that i need
> to enable on the firewall?
> Thanks
> Jores
>|||Yes, it is enabled and the Browser sevice is also running. i canconnect to
it using the query analyzer. the only problem is with Management studio.
Thanks
Jores
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uBvNIgLaGHA.1348@.TK2MSFTNGP05.phx.gbl...
> Is SQL Server 2005 enabled for remote connections?
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "joresm" <joresm@.hotmail.com> wrote in message
> news:ODgXkoKaGHA.1220@.TK2MSFTNGP02.phx.gbl...
>> Hi all,
>> I am unable to connect to SQL2005 server using the Management Studio. i
>> can however connect to SQL2000 using EM. Has anyone else encoutered this
>> issue? if so could you please share the solution? what is ti that i need
>> to enable on the firewall?
>> Thanks
>> Jores
>|||Hi I have experienced this problem also. Spent best part of a day trying to
resolve this to no avail. We have a VPN connection to our data center. The
database server has an instance of SQL 2000 which runs fine locally and
remotely from my desk. Recently we installed SQL 2005 and want to migrate
stuff to this new named instance. I can connect to the database fine locally
(on the database server itself and from other colocated machines (via
ADO.net). However I cannot access SQL 2005 over the VPN connection using
either ADO.net test app or SQL Management Studio. Is there some kind of port
blocking going on?
I don't know anything about Named Pipes, but I've tried the SQL
Configuration tool as suggested in some articles and have tried setting the
port to 1433 and turning of SQL 2000 to no avail. Would the VPN somehow be
blocking some ports - it appears that way, but my administrator assures me
that I should have full spectrum of ports available. WHATS GOING ON' Is the
SQL browser getting blocked or what? What button do I need to push to get
access to my database server from my development machine located over the
VPN?
Thanks Rob
"joresm" wrote:
> Yes, it is enabled and the Browser sevice is also running. i canconnect to
> it using the query analyzer. the only problem is with Management studio.
> Thanks
> Jores
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uBvNIgLaGHA.1348@.TK2MSFTNGP05.phx.gbl...
> > Is SQL Server 2005 enabled for remote connections?
> >
> > --
> > Hilary Cotter
> > Director of Text Mining and Database Strategy
> > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> >
> > This posting is my own and doesn't necessarily represent RelevantNoise's
> > positions, strategies or opinions.
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> > Looking for a FAQ on Indexing Services/SQL FTS
> > http://www.indexserverfaq.com
> >
> >
> >
> > "joresm" <joresm@.hotmail.com> wrote in message
> > news:ODgXkoKaGHA.1220@.TK2MSFTNGP02.phx.gbl...
> >> Hi all,
> >> I am unable to connect to SQL2005 server using the Management Studio. i
> >> can however connect to SQL2000 using EM. Has anyone else encoutered this
> >> issue? if so could you please share the solution? what is ti that i need
> >> to enable on the firewall?
> >>
> >> Thanks
> >> Jores
> >>
> >
> >
>
>sqlsql

Connecting to SBS SQL via Remote VPN (VB Application)

Hi,
Dont really know if this is the place to ask but here goes...
I have written a VB application that talks to various SQL2000 Tables. But i
need to expand the VB App to work on a laptop thats remotely connected by VP
N.
Even though the laptop is connected via VPN and can use server applications
it cannot see the SQL server? and produces (can find it errors).
Is there anything i need to do to the sql server to allow outside
connections or to the ISA firewall etc etc.
Any help will be appreciated.
Regards
TIMIf you know that your VPN connection is working correctly, then next try
connecting to the database server using it's IP and port as the data source:
http://www.carlprothman.net/Default...derForSQLServer
If that doesn't work, then speak with your DBA and/or network admin. Perhaps
the following is relevent to your situation:
How To Use ADO to Connect to a SQL Server That Is Behind a Firewall
http://support.microsoft.com/defaul...b;en-us;Q269882
INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/defaul...b;EN-US;q287932
"TIM" <TIM@.discussions.microsoft.com> wrote in message
news:C10D5F9D-F628-4B57-9EF3-707C9E621DA9@.microsoft.com...
> Hi,
> Dont really know if this is the place to ask but here goes...
> I have written a VB application that talks to various SQL2000 Tables. But
> i
> need to expand the VB App to work on a laptop thats remotely connected by
> VPN.
> Even though the laptop is connected via VPN and can use server
> applications
> it cannot see the SQL server? and produces (can find it errors).
> Is there anything i need to do to the sql server to allow outside
> connections or to the ISA firewall etc etc.
> Any help will be appreciated.
> Regards
> TIMsqlsql

Connecting to Remote SQL server - time out expired?

Hello

Im connecting to a remote SQL Server in Enterprise Manager Via VPN,

we checked the connection and everything but still o cant connect

to the remote server, Error message says "Time Out Expired",

we checked the firewall config, ADSL connection and it's all Ok

what seems to be the problem here??Hello

Im connecting to a remote SQL Server in Enterprise Manager Via VPN,

we checked the connection and everything but still o cant connect

to the remote server, Error message says "Time Out Expired",

we checked the firewall config, ADSL connection and it's all Ok

what seems to be the problem here??

There are oh so many possibilities...

1. Can you telnet to the remote server on the correct port?
2. Is there another firewall at the other end (I assume so since it's a VPN)? If so, can you verify that the traffic is getting beyond that firewall?
3. Are both firewalls set to handle the "hand-off" that occurs when incoming traffic on port 1433 is handed off to a negotiated port? This is usually automatic, but on some older firewalls, it must be manually configured.
4. Are you using hostname or IP address to connect? If hostname, what is the name resolution service running (I assume DNS)? If DNS, are you sure about the IP Address resolution?
5. Are you NAT'ing the internal IP addresses? Are the NATs configured correctly.

Look at your firewall logs carefully (hopefully there's a nice GUI to help you). The answer is likely in there somewhere. It may not be easy to find, but it's in there.

Regards,

hmscott

Connecting to local instance with firewall client enabled

I'm running SQL Server 2000 SP3 on my XP Pro laptop and everything
works fine without firewall client enabled. When I VPN in to the
network and enable the ISA server firewall client, I can't connect to
my local instance using Enterprise Manager or Query Analyzer, although
I can connect to another instance running on a server on the network.
If I'm VPNed in and I don't enable firewall client, I can still
connect to the local instance. And interestingly my ASP.NET
application (running locally) can still connect to the local SQL
Server instance once I changed the server name in web.config from
localhost to chris-laptop.
Any help would be greatly appreciated, as I really need to have
firewall client enabled and access to my databases through query
analyser at the same time.
Thanks
Chris BettertonIf you specifiy the ip address that SQL Server is listening on when
attempting to connect via Query Analyzer, does it allow you to connect?
If it does then you can use the SQL CLient Network Utility to create an
alias that points the server name to the ip address. This would let you
connect using the server name.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hadn't thought of that, 127.0.0.1 works fine so I can use the alias
approach. Thanks for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Connecting to local instance with firewall client enabled

I'm running SQL Server 2000 SP3 on my XP Pro laptop and everything
works fine without firewall client enabled. When I VPN in to the
network and enable the ISA server firewall client, I can't connect to
my local instance using Enterprise Manager or Query Analyzer, although
I can connect to another instance running on a server on the network.
If I'm VPNed in and I don't enable firewall client, I can still
connect to the local instance. And interestingly my ASP.NET
application (running locally) can still connect to the local SQL
Server instance once I changed the server name in web.config from
localhost to chris-laptop.
Any help would be greatly appreciated, as I really need to have
firewall client enabled and access to my databases through query
analyser at the same time.
Thanks
Chris Betterton
If you specifiy the ip address that SQL Server is listening on when
attempting to connect via Query Analyzer, does it allow you to connect?
If it does then you can use the SQL CLient Network Utility to create an
alias that points the server name to the ip address. This would let you
connect using the server name.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hadn't thought of that, 127.0.0.1 works fine so I can use the alias
approach. Thanks for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Connecting to a second instance via VPN

Hi,

I have two SQL SERVER Instances on the computer I am trying to connect to via VPN:
1) TEST
2. TEST/INST2

I can connect to the first with no problems.

When I am trying to connect to the second (with the Enterprise Manager/Query Analyzer and even with isql) - I get the following message:
"SQL SERVER does not exists or access denied".

I use the SQL SERVER user and password to connect (as login sa).

How can I connect to the second instance?

Thanks in advance.you have to make sure that tcp/it is enabled on the server. can you use remote desktop or some other remote access tool to connect to the box? check to see if the service for the named instance is running (this should have been the first suggestion)|||Sorry, I had the instance name wrong...

Thanks for your answer anyway!

Connecting through VPN fails

Hi all!
At work, I've no problems connecting to our testserver. From home I have
problems. I use VPN to get inside our firewall, and everything else works as
expected. Whether I try to connect to my testdata from my application, or I
try to connect using SQL Query Analyzer, I get the same errormessage (pasted
in here):
Unable to connect to server OSS24DBTEST:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
The servers is set up to use both Sql server and Windows authentication.
Anyone that have a clue where to start?
I'm a newbe using SQL server 2000
Thanks
AT
Hi,
Hope you have solved it in the meantime.
I do the same with a Checkpoint VPN connection over ADSL and this works well.
Will a straight (no VPN) connection work? (Use port 1433/1434). Be sure to
have this port open.
If this works, try to see if there is a portblocking vehickle at the other
side in the VPN router, if this is OK you really have a problem.
Besides, I was pleasantly surprised with the speed of the results working
over VPN.
I saw no degradation in performance with the direct connection.
Good luck,
"A.Taurus" wrote:

> Hi all!
> At work, I've no problems connecting to our testserver. From home I have
> problems. I use VPN to get inside our firewall, and everything else works as
> expected. Whether I try to connect to my testdata from my application, or I
> try to connect using SQL Query Analyzer, I get the same errormessage (pasted
> in here):
> Unable to connect to server OSS24DBTEST:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
> The servers is set up to use both Sql server and Windows authentication.
> Anyone that have a clue where to start?
> I'm a newbe using SQL server 2000
> Thanks
> AT
>
>

Connecting through VPN fails

Hi all!
At work, I've no problems connecting to our testserver. From home I have
problems. I use VPN to get inside our firewall, and everything else works as
expected. Whether I try to connect to my testdata from my application, or I
try to connect using SQL Query Analyzer, I get the same errormessage (pasted
in here):
Unable to connect to server OSS24DBTEST:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
The servers is set up to use both Sql server and Windows authentication.
Anyone that have a clue where to start?
I'm a newbe using SQL server 2000
Thanks
AT
When you use VPN, you log onto the domain from home, right? Otherwise, it
won't work.
When I use VPN, I often Remote Desktop into a machine at the office, and log
onto the domain there.
Jeff
"A.Taurus" <nospam@.spam.no> wrote in message
news:cl6d9f$slu$1@.services.kq.no...
> Hi all!
> At work, I've no problems connecting to our testserver. From home I have
> problems. I use VPN to get inside our firewall, and everything else works
as
> expected. Whether I try to connect to my testdata from my application, or
I
> try to connect using SQL Query Analyzer, I get the same errormessage
(pasted
> in here):
> Unable to connect to server OSS24DBTEST:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
> The servers is set up to use both Sql server and Windows authentication.
> Anyone that have a clue where to start?
> I'm a newbe using SQL server 2000
> Thanks
> AT
>
>

Connecting through VPN fails

Hi all!
At work, I've no problems connecting to our testserver. From home I have
problems. I use VPN to get inside our firewall, and everything else works as
expected. Whether I try to connect to my testdata from my application, or I
try to connect using SQL Query Analyzer, I get the same errormessage (pasted
in here):
Unable to connect to server OSS24DBTEST:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
The servers is set up to use both Sql server and Windows authentication.
Anyone that have a clue where to start?
I'm a newbe using SQL server 2000
Thanks
ATWhen you use VPN, you log onto the domain from home, right? Otherwise, it
won't work.
When I use VPN, I often Remote Desktop into a machine at the office, and log
onto the domain there.
Jeff
"A.Taurus" <nospam@.spam.no> wrote in message
news:cl6d9f$slu$1@.services.kq.no...
> Hi all!
> At work, I've no problems connecting to our testserver. From home I have
> problems. I use VPN to get inside our firewall, and everything else works
as
> expected. Whether I try to connect to my testdata from my application, or
I
> try to connect using SQL Query Analyzer, I get the same errormessage
(pasted
> in here):
> Unable to connect to server OSS24DBTEST:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
> The servers is set up to use both Sql server and Windows authentication.
> Anyone that have a clue where to start?
> I'm a newbe using SQL server 2000
> Thanks
> AT
>
>

Connecting through VPN fails

Hi all!
At work, I've no problems connecting to our testserver. From home I have
problems. I use VPN to get inside our firewall, and everything else works as
expected. Whether I try to connect to my testdata from my application, or I
try to connect using SQL Query Analyzer, I get the same errormessage (pasted
in here):
Unable to connect to server OSS24DBTEST:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
The servers is set up to use both Sql server and Windows authentication.
Anyone that have a clue where to start?
I'm a newbe using SQL server 2000
Thanks
ATHi,
Hope you have solved it in the meantime.
I do the same with a Checkpoint VPN connection over ADSL and this works well
.
Will a straight (no VPN) connection work? (Use port 1433/1434). Be sure to
have this port open.
If this works, try to see if there is a portblocking vehickle at the other
side in the VPN router, if this is OK you really have a problem.
Besides, I was pleasantly surprised with the speed of the results working
over VPN.
I saw no degradation in performance with the direct connection.
Good luck,
"A.Taurus" wrote:

> Hi all!
> At work, I've no problems connecting to our testserver. From home I have
> problems. I use VPN to get inside our firewall, and everything else works
as
> expected. Whether I try to connect to my testdata from my application, or
I
> try to connect using SQL Query Analyzer, I get the same errormessage (past
ed
> in here):
> Unable to connect to server OSS24DBTEST:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
> The servers is set up to use both Sql server and Windows authentication.
> Anyone that have a clue where to start?
> I'm a newbe using SQL server 2000
> Thanks
> AT
>
>

Connecting client to SQL Server via Cisco VPN

We are having one client PC running Win XP. SQL Server has been set to
Windows Authentication, TCP/IP 1433, Windows 2003 (!).
Via Cisco VPN we are making a connection. IAS has been configurated, so the
local user profile doesn't matter. The server recognizes the user that is
part of the domain that has been defined at the server. So far so good.
When the user tries to connect via any client software (Enterprise Manager,
Query Analyzer, Access DAP) it sometimes fails. To do this test we used:
osql -l -S <hostname> -E
We have used several providers (dail-in, ADSL etc) and some of them works
fine, some not. You would probably say: use the one that works fine, but this
is not satisfying. Some client users are connected to a local network (no
dail in) and do also have the same problem.
The message we got is:
Login failed user '(null)'. Reason: not associated with trusted SQL Server
connection
I have seen at one of the Microsoft pages that we have to set the local
policies correct at the server where the domain has been defined (in case of
Windows 2003). We have done so. No results.
We first thought that it was a problem at the client, but since we have
proved that the same PC can connect to SQL it seems to be a networking
problem. We have also tried Named Pipes as a protocal but we did not succeed.
Since 50% of our clients are not able to connect (this is a world wide
application) we have serious problems. If anyone has any suggestion please
help us.
Thanks in advance
Jeroen
"Jeroen" <Jeroen@.discussions.microsoft.com> wrote in message
news:A750B079-A4AF-4B44-9A84-2E6A227B4029@.microsoft.com...
> We are having one client PC running Win XP. SQL Server has been set to
> Windows Authentication, TCP/IP 1433, Windows 2003 (!).
> Via Cisco VPN we are making a connection. IAS has been configurated, so
the
> local user profile doesn't matter. The server recognizes the user that is
> part of the domain that has been defined at the server. So far so good.
> When the user tries to connect via any client software (Enterprise
Manager,
> Query Analyzer, Access DAP) it sometimes fails. To do this test we used:
> osql -l -S <hostname> -E
> We have used several providers (dail-in, ADSL etc) and some of them works
> fine, some not. You would probably say: use the one that works fine, but
this
> is not satisfying. Some client users are connected to a local network (no
> dail in) and do also have the same problem.
> The message we got is:
> Login failed user '(null)'. Reason: not associated with trusted SQL Server
> connection
> I have seen at one of the Microsoft pages that we have to set the local
> policies correct at the server where the domain has been defined (in case
of
> Windows 2003). We have done so. No results.
> We first thought that it was a problem at the client, but since we have
> proved that the same PC can connect to SQL it seems to be a networking
> problem. We have also tried Named Pipes as a protocal but we did not
succeed.
> Since 50% of our clients are not able to connect (this is a world wide
> application) we have serious problems. If anyone has any suggestion please
> help us.
There are a number of areas that these clients could be failing... name
resolution, TCP ports being blocked, etc.. Perhaps this troubleshooting
guide will help:
How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/kb/827422
Steve
|||Thanks Steve,
The article helped us to get better focus on the issue. Instead of 50% of
the clients, almost all of them cannot connect when the try to establish a
connection via their local LAN.
We are almost sure that port 1433 is the problem. Since we got 3 dial in
providers 1 of them doesn't work. We have seen that NETSTAT -an shows us that
1433 is the problem. We have asked the provider and they have confirmed that
they give a random range of ports available.
Now the local LAN's... We have asked them to open port 1433 ingoing and
outgoing. But it still doesn't solve our problem. The VPN connection is
established via port 80 and this goes fine from any local LAN.
Windows authentication is chosen for a single point of entry. Some people do
not recommend this, but it is supported by Microsoft...
We are really lost, maybe someone has other ideas, maybe we can trace
somehow what goes wrong.
Regards,
Jeroen
"Steve Thompson" wrote:

> "Jeroen" <Jeroen@.discussions.microsoft.com> wrote in message
> news:A750B079-A4AF-4B44-9A84-2E6A227B4029@.microsoft.com...
> the
> Manager,
> this
> of
> succeed.
> There are a number of areas that these clients could be failing... name
> resolution, TCP ports being blocked, etc.. Perhaps this troubleshooting
> guide will help:
> How to troubleshoot connectivity issues in SQL Server 2000
> http://support.microsoft.com/kb/827422
> Steve
>
>

Connecting client to SQL Server via Cisco VPN

We are having one client PC running Win XP. SQL Server has been set to
Windows Authentication, TCP/IP 1433, Windows 2003 (!).
Via cisco VPN we are making a connection. IAS has been configurated, so the
local user profile doesn't matter. The server recognizes the user that is
part of the domain that has been defined at the server. So far so good.
When the user tries to connect via any client software (Enterprise Manager,
Query Analyzer, Access DAP) it sometimes fails. To do this test we used:
osql -l -S <hostname> -E
We have used several providers (dail-in, ADSL etc) and some of them works
fine, some not. You would probably say: use the one that works fine, but thi
s
is not satisfying. Some client users are connected to a local network (no
dail in) and do also have the same problem.
The message we got is:
Login failed user '(null)'. Reason: not associated with trusted SQL Server
connection
I have seen at one of the Microsoft pages that we have to set the local
policies correct at the server where the domain has been defined (in case of
Windows 2003). We have done so. No results.
We first thought that it was a problem at the client, but since we have
proved that the same PC can connect to SQL it seems to be a networking
problem. We have also tried Named Pipes as a protocal but we did not succeed
.
Since 50% of our clients are not able to connect (this is a world wide
application) we have serious problems. If anyone has any suggestion please
help us.
Thanks in advance
Jeroen"Jeroen" <Jeroen@.discussions.microsoft.com> wrote in message
news:A750B079-A4AF-4B44-9A84-2E6A227B4029@.microsoft.com...
> We are having one client PC running Win XP. SQL Server has been set to
> Windows Authentication, TCP/IP 1433, Windows 2003 (!).
> Via cisco VPN we are making a connection. IAS has been configurated, so
the
> local user profile doesn't matter. The server recognizes the user that is
> part of the domain that has been defined at the server. So far so good.
> When the user tries to connect via any client software (Enterprise
Manager,
> Query Analyzer, Access DAP) it sometimes fails. To do this test we used:
> osql -l -S <hostname> -E
> We have used several providers (dail-in, ADSL etc) and some of them works
> fine, some not. You would probably say: use the one that works fine, but
this
> is not satisfying. Some client users are connected to a local network (no
> dail in) and do also have the same problem.
> The message we got is:
> Login failed user '(null)'. Reason: not associated with trusted SQL Server
> connection
> I have seen at one of the Microsoft pages that we have to set the local
> policies correct at the server where the domain has been defined (in case
of
> Windows 2003). We have done so. No results.
> We first thought that it was a problem at the client, but since we have
> proved that the same PC can connect to SQL it seems to be a networking
> problem. We have also tried Named Pipes as a protocal but we did not
succeed.
> Since 50% of our clients are not able to connect (this is a world wide
> application) we have serious problems. If anyone has any suggestion please
> help us.
There are a number of areas that these clients could be failing... name
resolution, TCP ports being blocked, etc.. Perhaps this troubleshooting
guide will help:
How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/kb/827422
Steve|||Thanks Steve,
The article helped us to get better focus on the issue. Instead of 50% of
the clients, almost all of them cannot connect when the try to establish a
connection via their local LAN.
We are almost sure that port 1433 is the problem. Since we got 3 dial in
providers 1 of them doesn't work. We have seen that NETSTAT -an shows us tha
t
1433 is the problem. We have asked the provider and they have confirmed that
they give a random range of ports available.
Now the local LAN's... We have asked them to open port 1433 ingoing and
outgoing. But it still doesn't solve our problem. The VPN connection is
established via port 80 and this goes fine from any local LAN.
Windows authentication is chosen for a single point of entry. Some people do
not recommend this, but it is supported by Microsoft...
We are really lost, maybe someone has other ideas, maybe we can trace
somehow what goes wrong.
Regards,
Jeroen
"Steve Thompson" wrote:

> "Jeroen" <Jeroen@.discussions.microsoft.com> wrote in message
> news:A750B079-A4AF-4B44-9A84-2E6A227B4029@.microsoft.com...
> the
> Manager,
> this
> of
> succeed.
> There are a number of areas that these clients could be failing... name
> resolution, TCP ports being blocked, etc.. Perhaps this troubleshooting
> guide will help:
> How to troubleshoot connectivity issues in SQL Server 2000
> http://support.microsoft.com/kb/827422
> Steve
>
>

Connect to SQL Server through VPN

Hi
I've recently configured a VPN between 2 locations, using 3Com Internet Firewall 25.
It seems to be working fine, but i can't connect to a remote sql server. I've tried to do this from the managemente console, the query analyzer and a VB Application (ODBC) and i always get the same message: "The server does not exist or access denied". I'm trying to reach the server using its ip address, wich i can succesfully ping, and SQL authentication method.

If anyone has any idea, i will be really thankfull!You need to verify that port TCP 1433 and port UDP 1434 are open.

Also check for port TCP 135, that should be open if you need to make distributed queries|||Can you help us!!!!

Connect to SQL Server from machine not in domain

I am attempting to connect to a SQL Server that is in a domain that I
have a VPN connection to. I am receiving the Error: "Login failed for
user '(null)'. Reason: Not associated with a trusted SQL Server
connection. (Microsoft SQL Server, Error: 18452)
I errantly had expected that by mapping a drive to one of the shares
on the SQL Server that I am attempting to connect to, that I would be
able to connect ok using Integrated Windows Authentication. I have
even renamed my local UID/pwd to match that on the domain that owns
the SQL Server I am attempting to connect to.
Thoughts?Hi
If you have granted login to that user or a domain group on the domain where
the sql server is (where the user is a member) , then you should be able to
log in even though the user is in a different domain. If you can't grant the
login and if you can't change the way the domains trust each other, then you
will need to ue SQL Authentication.
John
"brandor" wrote:
> I am attempting to connect to a SQL Server that is in a domain that I
> have a VPN connection to. I am receiving the Error: "Login failed for
> user '(null)'. Reason: Not associated with a trusted SQL Server
> connection. (Microsoft SQL Server, Error: 18452)
> I errantly had expected that by mapping a drive to one of the shares
> on the SQL Server that I am attempting to connect to, that I would be
> able to connect ok using Integrated Windows Authentication. I have
> even renamed my local UID/pwd to match that on the domain that owns
> the SQL Server I am attempting to connect to.
> Thoughts?
>