I'm running SQL Server 2005 RTM on my laptop (Dell Latitude D810) but
cannot connect to Reporting Services Server. When I try to connect to
it using SQL Server Management Studio (using windows authentication) I
get the following Error message...
TITLE: Connect to Server
--
Cannot connect to {ServerName}.
--
ADDITIONAL INFORMATION:
The attempt to connect to the report server failed. Check your
connection information and that the report server is a compatible
version. (Microsoft.SqlServer.Management.UI.RSClient)
--
The request failed with HTTP status 404: Object Not Found.
(Microsoft.SqlServer.Management.UI.RSClient)
I have visual studio 2005 on the machine (which I installed after the
SQL Server install) and have .NET Framework version 2.0.50727.42.
The OS is windows XP Professional.
Anyone know what I will need to do to connect to the server?Simon Worth wrote:
> I'm running SQL Server 2005 RTM on my laptop (Dell Latitude D810) but
> cannot connect to Reporting Services Server. When I try to connect to
> it using SQL Server Management Studio (using windows authentication) I
> get the following Error message...
> TITLE: Connect to Server
> --
> Cannot connect to {ServerName}.
> --
> ADDITIONAL INFORMATION:
> The attempt to connect to the report server failed. Check your
> connection information and that the report server is a compatible
> version. (Microsoft.SqlServer.Management.UI.RSClient)
> --
> The request failed with HTTP status 404: Object Not Found.
> (Microsoft.SqlServer.Management.UI.RSClient)
> I have visual studio 2005 on the machine (which I installed after the
> SQL Server install) and have .NET Framework version 2.0.50727.42.
> The OS is windows XP Professional.
> Anyone know what I will need to do to connect to the server?
I'm still having issues with this - if anyone can offer any insight it
would still be greatly appreciated.|||Hi,
I am also having the same problem,
and it seems that at least a few people in this newsgroup are having the
same problem.
Somebody please help us with this!|||I resolved the issue, at least for my machine. My IIS is ver. 5.1, and the
URLScan did not allow POST verb. Once I listed POST as an allowed verb in
URLScan.ini, I could successfully connect to the report manager.
For anybody having problem, as below, I suggest you check your URLScan
settings.
The problems are :
1) When you navigate to http://<localhost>/<reports>, you get, "The attempt
to connect to the report server failed. Check your connection information
and that the report server is a compatible version.
(Microsoft.SqlServer.Management.UI.RSClient)".
2) You cannot connect to your reporting services instance through the
Management Studio.
Showing posts with label fails. Show all posts
Showing posts with label fails. Show all posts
Thursday, March 22, 2012
Connecting to Reporting Services Server Fails
Originally posted on Reporting Services newsgroup - Then on Setup - no
answer there though, so I thought I'd try the Server group as well.
I've looked through documentation and can't find an answer there, and
nothing on the web that seemed to apply either. I'm hoping someone can
give me a push in the right direction.
I'm running SQL Server 2005 RTM on my laptop (Dell Latitude D810) but
cannot connect to Reporting Services Server. When I try to connect to
it using SQL Server Management Studio (using windows authentication) I
get the following Error message...
TITLE: Connect to Server
--
Cannot connect to {ServerName}.
ADDITIONAL INFORMATION:
The attempt to connect to the report server failed. Check your
connection information and that the report server is a compatible
version. (Microsoft.SqlServer.Management.UI.RSClient)
The request failed with HTTP status 404: Object Not Found.
(Microsoft.SqlServer.Management.UI.RSClient)
I have visual studio 2005 on the machine (which I installed after the
SQL Server install) and have .NET Framework version 2.0.50727.42.
The OS is Windows XP Professional.
Anyone know what I will need to do to connect to the server?Hi,
Did u configure the virtual directories for tht instance on which
reporting services are running if not configure it first.After
configuring it check it out wether it works or not and I am facing here
a diffrent problem with some unknown exceptions rising that is:
"The underlying connection was closed: An unexpected error occurred on
a receive. (Microsoft.SqlServer.Management.UI.RSClient)
Unable to read data from the transport connection: An established
connection was aborted by the software in your host machine. (System)
An established connection was aborted by the software in your host
machine (System)."
So, can u able to guide me through this problem,if it is it will be a
great help for ur friend from ur side.
Thanks and regards
- vishwas R
VISHWAS R
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message2000026.html
answer there though, so I thought I'd try the Server group as well.
I've looked through documentation and can't find an answer there, and
nothing on the web that seemed to apply either. I'm hoping someone can
give me a push in the right direction.
I'm running SQL Server 2005 RTM on my laptop (Dell Latitude D810) but
cannot connect to Reporting Services Server. When I try to connect to
it using SQL Server Management Studio (using windows authentication) I
get the following Error message...
TITLE: Connect to Server
--
Cannot connect to {ServerName}.
ADDITIONAL INFORMATION:
The attempt to connect to the report server failed. Check your
connection information and that the report server is a compatible
version. (Microsoft.SqlServer.Management.UI.RSClient)
The request failed with HTTP status 404: Object Not Found.
(Microsoft.SqlServer.Management.UI.RSClient)
I have visual studio 2005 on the machine (which I installed after the
SQL Server install) and have .NET Framework version 2.0.50727.42.
The OS is Windows XP Professional.
Anyone know what I will need to do to connect to the server?Hi,
Did u configure the virtual directories for tht instance on which
reporting services are running if not configure it first.After
configuring it check it out wether it works or not and I am facing here
a diffrent problem with some unknown exceptions rising that is:
"The underlying connection was closed: An unexpected error occurred on
a receive. (Microsoft.SqlServer.Management.UI.RSClient)
Unable to read data from the transport connection: An established
connection was aborted by the software in your host machine. (System)
An established connection was aborted by the software in your host
machine (System)."
So, can u able to guide me through this problem,if it is it will be a
great help for ur friend from ur side.
Thanks and regards
- vishwas R
VISHWAS R
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message2000026.html
Connecting to Reporting Services Server Fails
Originally posted on Reporting Services newsgroup - Then on Setup - no
answer there though, so I thought I'd try the Server group as well.
I've looked through documentation and can't find an answer there, and
nothing on the web that seemed to apply either. I'm hoping someone can
give me a push in the right direction.
I'm running SQL Server 2005 RTM on my laptop (Dell Latitude D810) but
cannot connect to Reporting Services Server. When I try to connect to
it using SQL Server Management Studio (using windows authentication) I
get the following Error message...
TITLE: Connect to Server
--
Cannot connect to {ServerName}.
--
ADDITIONAL INFORMATION:
The attempt to connect to the report server failed. Check your
connection information and that the report server is a compatible
version. (Microsoft.SqlServer.Management.UI.RSClient)
--
The request failed with HTTP status 404: Object Not Found.
(Microsoft.SqlServer.Management.UI.RSClient)
I have visual studio 2005 on the machine (which I installed after the
SQL Server install) and have .NET Framework version 2.0.50727.42.
The OS is windows XP Professional.
Anyone know what I will need to do to connect to the server?Hi,
Did u configure the virtual directories for tht instance on which
reporting services are running if not configure it first.After
configuring it check it out wether it works or not and I am facing here
a diffrent problem with some unknown exceptions rising that is:
"The underlying connection was closed: An unexpected error occurred on
a receive. (Microsoft.SqlServer.Management.UI.RSClient)
Unable to read data from the transport connection: An established
connection was aborted by the software in your host machine. (System)
An established connection was aborted by the software in your host
machine (System)."
So, can u able to guide me through this problem,if it is it will be a
great help for ur friend from ur side.
Thanks and regards
- vishwas R
VISHWAS R
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message2000026.html
answer there though, so I thought I'd try the Server group as well.
I've looked through documentation and can't find an answer there, and
nothing on the web that seemed to apply either. I'm hoping someone can
give me a push in the right direction.
I'm running SQL Server 2005 RTM on my laptop (Dell Latitude D810) but
cannot connect to Reporting Services Server. When I try to connect to
it using SQL Server Management Studio (using windows authentication) I
get the following Error message...
TITLE: Connect to Server
--
Cannot connect to {ServerName}.
--
ADDITIONAL INFORMATION:
The attempt to connect to the report server failed. Check your
connection information and that the report server is a compatible
version. (Microsoft.SqlServer.Management.UI.RSClient)
--
The request failed with HTTP status 404: Object Not Found.
(Microsoft.SqlServer.Management.UI.RSClient)
I have visual studio 2005 on the machine (which I installed after the
SQL Server install) and have .NET Framework version 2.0.50727.42.
The OS is windows XP Professional.
Anyone know what I will need to do to connect to the server?Hi,
Did u configure the virtual directories for tht instance on which
reporting services are running if not configure it first.After
configuring it check it out wether it works or not and I am facing here
a diffrent problem with some unknown exceptions rising that is:
"The underlying connection was closed: An unexpected error occurred on
a receive. (Microsoft.SqlServer.Management.UI.RSClient)
Unable to read data from the transport connection: An established
connection was aborted by the software in your host machine. (System)
An established connection was aborted by the software in your host
machine (System)."
So, can u able to guide me through this problem,if it is it will be a
great help for ur friend from ur side.
Thanks and regards
- vishwas R
VISHWAS R
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message2000026.html
Monday, March 19, 2012
Connecting to named instance in Management Studio fails
I have a remote server with a default instance of Sql 2000 and a named
instance of Sql 2005. Whenever I try to connect to the named instance
in Management Studio, it ALWAYS connects to the default instance. I am
specifying the connection as ServerName\InstanceName. It seems like it
is ignoring the instance name in the connection request. I have tried
creating an alias, but it does not change the behavior. One special
note - due to our network structure we must use fully qualified domain
names when connecting to remote servers. The my local server and my
remote server are in different sub-domains:
local server = ServerA.HQ.domain.com
remote server = ServerX.Remote.domain.com
One interesting observation is that I am able to connect to the remote
server from a different db server in the same sub-domain without any
problems. i.e. ServerY.remote.domain.com can connect to
ServerX.remote.domain.com.
I know there was a bug in MDAC that was similar to this, but it was
supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
the SQLNI code?check with your network admin. it seems there is firewall rule on udp 1434.
also, try to specify the tcp as part of your connection string.
e.g.
sqlcmd -S"ServerX.Remote.domain.com,tcp#"
-oj
"kmart" <kevmart@.gmail.com> wrote in message
news:1146849746.958318.194980@.v46g2000cwv.googlegroups.com...
>I have a remote server with a default instance of Sql 2000 and a named
> instance of Sql 2005. Whenever I try to connect to the named instance
> in Management Studio, it ALWAYS connects to the default instance. I am
> specifying the connection as ServerName\InstanceName. It seems like it
> is ignoring the instance name in the connection request. I have tried
> creating an alias, but it does not change the behavior. One special
> note - due to our network structure we must use fully qualified domain
> names when connecting to remote servers. The my local server and my
> remote server are in different sub-domains:
> local server = ServerA.HQ.domain.com
> remote server = ServerX.Remote.domain.com
> One interesting observation is that I am able to connect to the remote
> server from a different db server in the same sub-domain without any
> problems. i.e. ServerY.remote.domain.com can connect to
> ServerX.remote.domain.com.
> I know there was a bug in MDAC that was similar to this, but it was
> supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
> the SQLNI code?
>
instance of Sql 2005. Whenever I try to connect to the named instance
in Management Studio, it ALWAYS connects to the default instance. I am
specifying the connection as ServerName\InstanceName. It seems like it
is ignoring the instance name in the connection request. I have tried
creating an alias, but it does not change the behavior. One special
note - due to our network structure we must use fully qualified domain
names when connecting to remote servers. The my local server and my
remote server are in different sub-domains:
local server = ServerA.HQ.domain.com
remote server = ServerX.Remote.domain.com
One interesting observation is that I am able to connect to the remote
server from a different db server in the same sub-domain without any
problems. i.e. ServerY.remote.domain.com can connect to
ServerX.remote.domain.com.
I know there was a bug in MDAC that was similar to this, but it was
supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
the SQLNI code?check with your network admin. it seems there is firewall rule on udp 1434.
also, try to specify the tcp as part of your connection string.
e.g.
sqlcmd -S"ServerX.Remote.domain.com,tcp#"
-oj
"kmart" <kevmart@.gmail.com> wrote in message
news:1146849746.958318.194980@.v46g2000cwv.googlegroups.com...
>I have a remote server with a default instance of Sql 2000 and a named
> instance of Sql 2005. Whenever I try to connect to the named instance
> in Management Studio, it ALWAYS connects to the default instance. I am
> specifying the connection as ServerName\InstanceName. It seems like it
> is ignoring the instance name in the connection request. I have tried
> creating an alias, but it does not change the behavior. One special
> note - due to our network structure we must use fully qualified domain
> names when connecting to remote servers. The my local server and my
> remote server are in different sub-domains:
> local server = ServerA.HQ.domain.com
> remote server = ServerX.Remote.domain.com
> One interesting observation is that I am able to connect to the remote
> server from a different db server in the same sub-domain without any
> problems. i.e. ServerY.remote.domain.com can connect to
> ServerX.remote.domain.com.
> I know there was a bug in MDAC that was similar to this, but it was
> supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
> the SQLNI code?
>
Connecting to named instance in Management Studio fails
I have a remote server with a default instance of Sql 2000 and a named
instance of Sql 2005. Whenever I try to connect to the named instance
in Management Studio, it ALWAYS connects to the default instance. I am
specifying the connection as ServerName\InstanceName. It seems like it
is ignoring the instance name in the connection request. I have tried
creating an alias, but it does not change the behavior. One special
note - due to our network structure we must use fully qualified domain
names when connecting to remote servers. The my local server and my
remote server are in different sub-domains:
local server = ServerA.HQ.domain.com
remote server = ServerX.Remote.domain.com
One interesting observation is that I am able to connect to the remote
server from a different db server in the same sub-domain without any
problems. i.e. ServerY.remote.domain.com can connect to
ServerX.remote.domain.com.
I know there was a bug in MDAC that was similar to this, but it was
supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
the SQLNI code?check with your network admin. it seems there is firewall rule on udp 1434.
also, try to specify the tcp as part of your connection string.
e.g.
sqlcmd -S"ServerX.Remote.domain.com,tcp#"
-oj
"kmart" <kevmart@.gmail.com> wrote in message
news:1146849746.958318.194980@.v46g2000cwv.googlegroups.com...
>I have a remote server with a default instance of Sql 2000 and a named
> instance of Sql 2005. Whenever I try to connect to the named instance
> in Management Studio, it ALWAYS connects to the default instance. I am
> specifying the connection as ServerName\InstanceName. It seems like it
> is ignoring the instance name in the connection request. I have tried
> creating an alias, but it does not change the behavior. One special
> note - due to our network structure we must use fully qualified domain
> names when connecting to remote servers. The my local server and my
> remote server are in different sub-domains:
> local server = ServerA.HQ.domain.com
> remote server = ServerX.Remote.domain.com
> One interesting observation is that I am able to connect to the remote
> server from a different db server in the same sub-domain without any
> problems. i.e. ServerY.remote.domain.com can connect to
> ServerX.remote.domain.com.
> I know there was a bug in MDAC that was similar to this, but it was
> supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
> the SQLNI code?
>
instance of Sql 2005. Whenever I try to connect to the named instance
in Management Studio, it ALWAYS connects to the default instance. I am
specifying the connection as ServerName\InstanceName. It seems like it
is ignoring the instance name in the connection request. I have tried
creating an alias, but it does not change the behavior. One special
note - due to our network structure we must use fully qualified domain
names when connecting to remote servers. The my local server and my
remote server are in different sub-domains:
local server = ServerA.HQ.domain.com
remote server = ServerX.Remote.domain.com
One interesting observation is that I am able to connect to the remote
server from a different db server in the same sub-domain without any
problems. i.e. ServerY.remote.domain.com can connect to
ServerX.remote.domain.com.
I know there was a bug in MDAC that was similar to this, but it was
supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
the SQLNI code?check with your network admin. it seems there is firewall rule on udp 1434.
also, try to specify the tcp as part of your connection string.
e.g.
sqlcmd -S"ServerX.Remote.domain.com,tcp#"
-oj
"kmart" <kevmart@.gmail.com> wrote in message
news:1146849746.958318.194980@.v46g2000cwv.googlegroups.com...
>I have a remote server with a default instance of Sql 2000 and a named
> instance of Sql 2005. Whenever I try to connect to the named instance
> in Management Studio, it ALWAYS connects to the default instance. I am
> specifying the connection as ServerName\InstanceName. It seems like it
> is ignoring the instance name in the connection request. I have tried
> creating an alias, but it does not change the behavior. One special
> note - due to our network structure we must use fully qualified domain
> names when connecting to remote servers. The my local server and my
> remote server are in different sub-domains:
> local server = ServerA.HQ.domain.com
> remote server = ServerX.Remote.domain.com
> One interesting observation is that I am able to connect to the remote
> server from a different db server in the same sub-domain without any
> problems. i.e. ServerY.remote.domain.com can connect to
> ServerX.remote.domain.com.
> I know there was a bug in MDAC that was similar to this, but it was
> supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
> the SQLNI code?
>
Connecting to named instance fails for Enterprise Manager but works with Query Analyzer
Hi,
We have just had a 64-bit SQL Server 2000 cluster installed in our
network and I am having difficulties connecting to it.
The named instance I am trying to access is 192.168.0.108\DX
I can connect to it from a machine on the same subnet using Enterprise
Manager, but not from a machine on another subnet (192.168.14.0), when
attempiting EM just stops responding. The weird thing is that I can
connect using Query Analyzer, but not EM (obviously using the same
connection details).
Does anybody have any suggestions to what might be causing this
behaviour?
The client computer I use is a Windows XP Professional with SP2 and
client connectivity tools for SQL Server 2000. I have tried disabling
the firewall, which didn't help. I can connect to another SQL Server
(default instance, 32-bit, non-clustered) on the other network with
EM.
Regards,
Ville Tuomola
Have you tried pinging the server when you can't connect?
Have you checked the registration/connection properties for
the server in Enterprise Manager? Are you sure you aren't
just getting a login timeout? You can increase the login
timeout from the menu go to Tools then Options. On the
Advanced tab, increase the login timeout to a value higher
than the default 4 seconds.
-Sue
On 7 Oct 2004 01:11:35 -0700, vtuomola@.gmail.com (Ville
Tuomola) wrote:
>Hi,
>We have just had a 64-bit SQL Server 2000 cluster installed in our
>network and I am having difficulties connecting to it.
>The named instance I am trying to access is 192.168.0.108\DX
>I can connect to it from a machine on the same subnet using Enterprise
>Manager, but not from a machine on another subnet (192.168.14.0), when
>attempiting EM just stops responding. The weird thing is that I can
>connect using Query Analyzer, but not EM (obviously using the same
>connection details).
>Does anybody have any suggestions to what might be causing this
>behaviour?
>The client computer I use is a Windows XP Professional with SP2 and
>client connectivity tools for SQL Server 2000. I have tried disabling
>the firewall, which didn't help. I can connect to another SQL Server
>(default instance, 32-bit, non-clustered) on the other network with
>EM.
>Regards,
>Ville Tuomola
We have just had a 64-bit SQL Server 2000 cluster installed in our
network and I am having difficulties connecting to it.
The named instance I am trying to access is 192.168.0.108\DX
I can connect to it from a machine on the same subnet using Enterprise
Manager, but not from a machine on another subnet (192.168.14.0), when
attempiting EM just stops responding. The weird thing is that I can
connect using Query Analyzer, but not EM (obviously using the same
connection details).
Does anybody have any suggestions to what might be causing this
behaviour?
The client computer I use is a Windows XP Professional with SP2 and
client connectivity tools for SQL Server 2000. I have tried disabling
the firewall, which didn't help. I can connect to another SQL Server
(default instance, 32-bit, non-clustered) on the other network with
EM.
Regards,
Ville Tuomola
Have you tried pinging the server when you can't connect?
Have you checked the registration/connection properties for
the server in Enterprise Manager? Are you sure you aren't
just getting a login timeout? You can increase the login
timeout from the menu go to Tools then Options. On the
Advanced tab, increase the login timeout to a value higher
than the default 4 seconds.
-Sue
On 7 Oct 2004 01:11:35 -0700, vtuomola@.gmail.com (Ville
Tuomola) wrote:
>Hi,
>We have just had a 64-bit SQL Server 2000 cluster installed in our
>network and I am having difficulties connecting to it.
>The named instance I am trying to access is 192.168.0.108\DX
>I can connect to it from a machine on the same subnet using Enterprise
>Manager, but not from a machine on another subnet (192.168.14.0), when
>attempiting EM just stops responding. The weird thing is that I can
>connect using Query Analyzer, but not EM (obviously using the same
>connection details).
>Does anybody have any suggestions to what might be causing this
>behaviour?
>The client computer I use is a Windows XP Professional with SP2 and
>client connectivity tools for SQL Server 2000. I have tried disabling
>the firewall, which didn't help. I can connect to another SQL Server
>(default instance, 32-bit, non-clustered) on the other network with
>EM.
>Regards,
>Ville Tuomola
Thursday, March 8, 2012
Connecting to an alias fails
Created a new alias with the SQL Server client network utility. With
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-KevinError message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegroups.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-KevinError message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegroups.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
Connecting to an alias fails
Created a new alias with the SQL Server client network utility. With
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-Kevin
Error message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegrou ps.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-Kevin
Error message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegrou ps.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>
Wednesday, March 7, 2012
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
>
>
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
>
>
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
>
>
Saturday, February 25, 2012
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
>
>
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
>
>
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
>
>
Subscribe to:
Posts (Atom)