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.
Showing posts with label ive. Show all posts
Showing posts with label ive. Show all posts
Tuesday, March 27, 2012
Sunday, March 11, 2012
Connecting to DB with Static IP over the internet
Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
computer, with a static IP address? If so how is this done? I’ve done the
following:
1) setup router to forward to a port 5000
2) I setup MS SQL server to listen to this port, I check error logs, and it
is listening, I do netstat –a and it does list that it is being listened t
o.
3) I make sure the DMZ is clear for the computer that is being forward the
stuff from the internet.
4) I can use the Remote Desktop Connection to connect to that static IP
computer and it works just fine, …
5) When I try to connect to the computer through a connection string I get
the oh so informative “Invalid connection string attribute” even though
I use
the same thing with another static ip, on a win2000 server, and it works the
connection string looks like this:
User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
6) I did setup the server network utility with the port,
I am not sure what I missed, I know on the Server2000 operating system I
did go into the remote access routing utility, but I can’t find that on
Windows XP Pro,
Can anyone help me out?"ARTMIC" <ARTMIC@.discussions.microsoft.com> wrote in message
news:EFA03B8C-E304-4CB4-AC76-8AE6E73FABF6@.microsoft.com...
> Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> computer, with a static IP address? If so how is this done? I've done the
> following:
> 1) setup router to forward to a port 5000
> 2) I setup MS SQL server to listen to this port, I check error logs, and
> it
> is listening, I do netstat -a and it does list that it is being listened
> to.
> 3) I make sure the DMZ is clear for the computer that is being forward the
> stuff from the internet.
> 4) I can use the Remote Desktop Connection to connect to that static IP
> computer and it works just fine, .
> 5) When I try to connect to the computer through a connection string I get
> the oh so informative "Invalid connection string attribute" even though I
> use
> the same thing with another static ip, on a win2000 server, and it works
> the
> connection string looks like this:
> User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port
> No=5000;
> 6) I did setup the server network utility with the port,
> I am not sure what I missed, I know on the Server2000 operating system I
> did go into the remote access routing utility, but I can't find that on
> Windows XP Pro,
> Can anyone help me out?
Try equating the IP number to a name in hosts and then use that name in the
connection string.
computer, with a static IP address? If so how is this done? I’ve done the
following:
1) setup router to forward to a port 5000
2) I setup MS SQL server to listen to this port, I check error logs, and it
is listening, I do netstat –a and it does list that it is being listened t
o.
3) I make sure the DMZ is clear for the computer that is being forward the
stuff from the internet.
4) I can use the Remote Desktop Connection to connect to that static IP
computer and it works just fine, …
5) When I try to connect to the computer through a connection string I get
the oh so informative “Invalid connection string attribute” even though
I use
the same thing with another static ip, on a win2000 server, and it works the
connection string looks like this:
User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
6) I did setup the server network utility with the port,
I am not sure what I missed, I know on the Server2000 operating system I
did go into the remote access routing utility, but I can’t find that on
Windows XP Pro,
Can anyone help me out?"ARTMIC" <ARTMIC@.discussions.microsoft.com> wrote in message
news:EFA03B8C-E304-4CB4-AC76-8AE6E73FABF6@.microsoft.com...
> Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> computer, with a static IP address? If so how is this done? I've done the
> following:
> 1) setup router to forward to a port 5000
> 2) I setup MS SQL server to listen to this port, I check error logs, and
> it
> is listening, I do netstat -a and it does list that it is being listened
> to.
> 3) I make sure the DMZ is clear for the computer that is being forward the
> stuff from the internet.
> 4) I can use the Remote Desktop Connection to connect to that static IP
> computer and it works just fine, .
> 5) When I try to connect to the computer through a connection string I get
> the oh so informative "Invalid connection string attribute" even though I
> use
> the same thing with another static ip, on a win2000 server, and it works
> the
> connection string looks like this:
> User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port
> No=5000;
> 6) I did setup the server network utility with the port,
> I am not sure what I missed, I know on the Server2000 operating system I
> did go into the remote access routing utility, but I can't find that on
> Windows XP Pro,
> Can anyone help me out?
Try equating the IP number to a name in hosts and then use that name in the
connection string.
Connecting to DB with Static IP over the internet
Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
computer, with a static IP address? If so how is this done? I’ve done the
following:
1) setup router to forward to a port 5000
2) I setup MS SQL server to listen to this port, I check error logs, and it
is listening, I do netstat –a and it does list that it is being listened t
o.
3) I make sure the DMZ is clear for the computer that is being forward the
stuff from the internet.
4) I can use the Remote Desktop Connection to connect to that static IP
computer and it works just fine, …
5) When I try to connect to the computer through a connection string I get
the oh so informative “Invalid connection string attribute” even though
I use
the same thing with another static ip, on a win2000 server, and it works the
connection string looks like this:
User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
6) I did setup the server network utility with the port,
I am not sure what I missed, I know on the Server2000 operating system I
did go into the remote access routing utility, but I can’t find that on
Windows XP Pro,
Can anyone help me out?Hi
Try including the port at the end of the IP address as shown in
http://www.connectionstrings.com/
John
"ARTMIC" wrote:
> Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> computer, with a static IP address? If so how is this done? I’ve done th
e
> following:
> 1) setup router to forward to a port 5000
> 2) I setup MS SQL server to listen to this port, I check error logs, and i
t
> is listening, I do netstat –a and it does list that it is being listened
to.
> 3) I make sure the DMZ is clear for the computer that is being forward the
> stuff from the internet.
> 4) I can use the Remote Desktop Connection to connect to that static IP
> computer and it works just fine, …
> 5) When I try to connect to the computer through a connection string I get
> the oh so informative “Invalid connection string attribute” even thoug
h I use
> the same thing with another static ip, on a win2000 server, and it works t
he
> connection string looks like this:
> User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000
;
> 6) I did setup the server network utility with the port,
> I am not sure what I missed, I know on the Server2000 operating system I
> did go into the remote access routing utility, but I can’t find that on
> Windows XP Pro,
> Can anyone help me out?
>|||Hi,
Have you checked WintowsXP firewall. If it turned on, you need to configure
the exception for this port.
Yuriy
"ARTMIC" wrote:
> Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> computer, with a static IP address? If so how is this done? I’ve done th
e
> following:
> 1) setup router to forward to a port 5000
> 2) I setup MS SQL server to listen to this port, I check error logs, and i
t
> is listening, I do netstat –a and it does list that it is being listened
to.
> 3) I make sure the DMZ is clear for the computer that is being forward the
> stuff from the internet.
> 4) I can use the Remote Desktop Connection to connect to that static IP
> computer and it works just fine, …
> 5) When I try to connect to the computer through a connection string I get
> the oh so informative “Invalid connection string attribute” even thoug
h I use
> the same thing with another static ip, on a win2000 server, and it works t
he
> connection string looks like this:
> User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000
;
> 6) I did setup the server network utility with the port,
> I am not sure what I missed, I know on the Server2000 operating system I
> did go into the remote access routing utility, but I can’t find that on
> Windows XP Pro,
> Can anyone help me out?
>|||Hi
Just to check that you have seen http://support.microsoft.com/kb/287932?
John
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
>|||Thanks, i will try that, but i am pretty sure i tried all imaginable
connection strings, what gets to me is that it should work, i know the sql
server is listening to port 5000 ... i can remotely connect to that computer
over that static ip from my other computer with the Remote Desktop
Connection, so it looks ok, but why am i still having all these problems?
The funny thing is if i use the internal ip address of that computer that
connects to the router, then i can use the same connection string, (just
changing ip address) and the sql server responds, so internally it knows
about port 5000, as soon as i use the static ip, it complains about "Invalid
connection string attribute"
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
>|||Thanks, i will read through that, maybe i missed something.
i'm so frustrated by this, i did this before with win2000 server a while
back and it worked ok, but with the Win XP Pro, it is sooooooooooooo hard to
do
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Just to check that you have seen http://support.microsoft.com/kb/287932?
> John
> "John Bell" wrote:
>|||i Installed Win XP Pro on a test machine, and did not apply any updates to
that computer, as for the firewall, it is disabled when i'm in the netwrok
properties,
The only difference that i can recall from Windows server 2000 is that in
that operating system i modified the remote accesss routing settings. i can'
t
find that utility on Win XP Pro
Arghhhhh help
"Yuriy Al" wrote:
[vbcol=seagreen]
> Hi,
> Have you checked WintowsXP firewall. If it turned on, you need to configur
e
> the exception for this port.
> Yuriy
>
> "ARTMIC" wrote:
>|||Hi
Have you tried accessing this with osql or SQLPing?
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
You may want to try telneting to the port.
John
"ARTMIC" wrote:
[vbcol=seagreen]
> Thanks, i will try that, but i am pretty sure i tried all imaginable
> connection strings, what gets to me is that it should work, i know the sql
> server is listening to port 5000 ... i can remotely connect to that comput
er
> over that static ip from my other computer with the Remote Desktop
> Connection, so it looks ok, but why am i still having all these problems?
> The funny thing is if i use the internal ip address of that computer that
> connects to the router, then i can use the same connection string, (just
> changing ip address) and the sql server responds, so internally it knows
> about port 5000, as soon as i use the static ip, it complains about "Inval
id
> connection string attribute"
> "John Bell" wrote:
>|||i figured it out, i was so into the sql part that i forgot to disable dhcp,
in other words the damn internal ip address changed on me every time i
rebooted and that is why i couldn't connect, i filled in the DSN, and
internal computer iP and made sure to forward port and dmz to it and it work
s
now,
the only thing i'm wondering is do i need DMZ enabled for that internal ip?
Thanks for the help though, those suggestions made me understand the SQL2000
software a lot more, and that sure is great, i love learning new things.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried accessing this with osql or SQLPing?
> http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
> You may want to try telneting to the port.
> John
> "ARTMIC" wrote:
>|||Hi
To access the machine from the internal network without going out over the
internet your internal IP address will be needed. You should configure your
firewall/DMZ so that access to this IP address is only allowed internally.
HTH
John
"ARTMIC" wrote:
[vbcol=seagreen]
> i figured it out, i was so into the sql part that i forgot to disable dhcp
,
> in other words the damn internal ip address changed on me every time i
> rebooted and that is why i couldn't connect, i filled in the DSN, and
> internal computer iP and made sure to forward port and dmz to it and it wo
rks
> now,
> the only thing i'm wondering is do i need DMZ enabled for that internal ip
?
> Thanks for the help though, those suggestions made me understand the SQL20
00
> software a lot more, and that sure is great, i love learning new things.
>
> "John Bell" wrote:
>
computer, with a static IP address? If so how is this done? I’ve done the
following:
1) setup router to forward to a port 5000
2) I setup MS SQL server to listen to this port, I check error logs, and it
is listening, I do netstat –a and it does list that it is being listened t
o.
3) I make sure the DMZ is clear for the computer that is being forward the
stuff from the internet.
4) I can use the Remote Desktop Connection to connect to that static IP
computer and it works just fine, …
5) When I try to connect to the computer through a connection string I get
the oh so informative “Invalid connection string attribute” even though
I use
the same thing with another static ip, on a win2000 server, and it works the
connection string looks like this:
User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
6) I did setup the server network utility with the port,
I am not sure what I missed, I know on the Server2000 operating system I
did go into the remote access routing utility, but I can’t find that on
Windows XP Pro,
Can anyone help me out?Hi
Try including the port at the end of the IP address as shown in
http://www.connectionstrings.com/
John
"ARTMIC" wrote:
> Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> computer, with a static IP address? If so how is this done? I’ve done th
e
> following:
> 1) setup router to forward to a port 5000
> 2) I setup MS SQL server to listen to this port, I check error logs, and i
t
> is listening, I do netstat –a and it does list that it is being listened
to.
> 3) I make sure the DMZ is clear for the computer that is being forward the
> stuff from the internet.
> 4) I can use the Remote Desktop Connection to connect to that static IP
> computer and it works just fine, …
> 5) When I try to connect to the computer through a connection string I get
> the oh so informative “Invalid connection string attribute” even thoug
h I use
> the same thing with another static ip, on a win2000 server, and it works t
he
> connection string looks like this:
> User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000
;
> 6) I did setup the server network utility with the port,
> I am not sure what I missed, I know on the Server2000 operating system I
> did go into the remote access routing utility, but I can’t find that on
> Windows XP Pro,
> Can anyone help me out?
>|||Hi,
Have you checked WintowsXP firewall. If it turned on, you need to configure
the exception for this port.
Yuriy
"ARTMIC" wrote:
> Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> computer, with a static IP address? If so how is this done? I’ve done th
e
> following:
> 1) setup router to forward to a port 5000
> 2) I setup MS SQL server to listen to this port, I check error logs, and i
t
> is listening, I do netstat –a and it does list that it is being listened
to.
> 3) I make sure the DMZ is clear for the computer that is being forward the
> stuff from the internet.
> 4) I can use the Remote Desktop Connection to connect to that static IP
> computer and it works just fine, …
> 5) When I try to connect to the computer through a connection string I get
> the oh so informative “Invalid connection string attribute” even thoug
h I use
> the same thing with another static ip, on a win2000 server, and it works t
he
> connection string looks like this:
> User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000
;
> 6) I did setup the server network utility with the port,
> I am not sure what I missed, I know on the Server2000 operating system I
> did go into the remote access routing utility, but I can’t find that on
> Windows XP Pro,
> Can anyone help me out?
>|||Hi
Just to check that you have seen http://support.microsoft.com/kb/287932?
John
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
>|||Thanks, i will try that, but i am pretty sure i tried all imaginable
connection strings, what gets to me is that it should work, i know the sql
server is listening to port 5000 ... i can remotely connect to that computer
over that static ip from my other computer with the Remote Desktop
Connection, so it looks ok, but why am i still having all these problems?
The funny thing is if i use the internal ip address of that computer that
connects to the router, then i can use the same connection string, (just
changing ip address) and the sql server responds, so internally it knows
about port 5000, as soon as i use the static ip, it complains about "Invalid
connection string attribute"
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
>|||Thanks, i will read through that, maybe i missed something.
i'm so frustrated by this, i did this before with win2000 server a while
back and it worked ok, but with the Win XP Pro, it is sooooooooooooo hard to
do
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Just to check that you have seen http://support.microsoft.com/kb/287932?
> John
> "John Bell" wrote:
>|||i Installed Win XP Pro on a test machine, and did not apply any updates to
that computer, as for the firewall, it is disabled when i'm in the netwrok
properties,
The only difference that i can recall from Windows server 2000 is that in
that operating system i modified the remote accesss routing settings. i can'
t
find that utility on Win XP Pro
Arghhhhh help
"Yuriy Al" wrote:
[vbcol=seagreen]
> Hi,
> Have you checked WintowsXP firewall. If it turned on, you need to configur
e
> the exception for this port.
> Yuriy
>
> "ARTMIC" wrote:
>|||Hi
Have you tried accessing this with osql or SQLPing?
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
You may want to try telneting to the port.
John
"ARTMIC" wrote:
[vbcol=seagreen]
> Thanks, i will try that, but i am pretty sure i tried all imaginable
> connection strings, what gets to me is that it should work, i know the sql
> server is listening to port 5000 ... i can remotely connect to that comput
er
> over that static ip from my other computer with the Remote Desktop
> Connection, so it looks ok, but why am i still having all these problems?
> The funny thing is if i use the internal ip address of that computer that
> connects to the router, then i can use the same connection string, (just
> changing ip address) and the sql server responds, so internally it knows
> about port 5000, as soon as i use the static ip, it complains about "Inval
id
> connection string attribute"
> "John Bell" wrote:
>|||i figured it out, i was so into the sql part that i forgot to disable dhcp,
in other words the damn internal ip address changed on me every time i
rebooted and that is why i couldn't connect, i filled in the DSN, and
internal computer iP and made sure to forward port and dmz to it and it work
s
now,
the only thing i'm wondering is do i need DMZ enabled for that internal ip?
Thanks for the help though, those suggestions made me understand the SQL2000
software a lot more, and that sure is great, i love learning new things.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried accessing this with osql or SQLPing?
> http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
> You may want to try telneting to the port.
> John
> "ARTMIC" wrote:
>|||Hi
To access the machine from the internal network without going out over the
internet your internal IP address will be needed. You should configure your
firewall/DMZ so that access to this IP address is only allowed internally.
HTH
John
"ARTMIC" wrote:
[vbcol=seagreen]
> i figured it out, i was so into the sql part that i forgot to disable dhcp
,
> in other words the damn internal ip address changed on me every time i
> rebooted and that is why i couldn't connect, i filled in the DSN, and
> internal computer iP and made sure to forward port and dmz to it and it wo
rks
> now,
> the only thing i'm wondering is do i need DMZ enabled for that internal ip
?
> Thanks for the help though, those suggestions made me understand the SQL20
00
> software a lot more, and that sure is great, i love learning new things.
>
> "John Bell" wrote:
>
Thursday, March 8, 2012
Connecting to a SQL DB
Hi,
I have a server with MSSQL Server installed there in which I've deployed my
DB.
I've also deployed an app (programmed with C# in .net) which access that DB.
Is there any chance to access that DB without installing the SQL Client?
It is very urgent.
Many thx.
SqlClient is part of the .NET Framework -- there is no separate
install and you can't uninstall the Framework when you're using C#.
However, I'm curious as to why you have a compelling need to uninstall
it.
--Mary
On Fri, 31 Mar 2006 00:56:02 -0800, Oscar
<Oscar@.discussions.microsoft.com> wrote:
>Hi,
>I have a server with MSSQL Server installed there in which I've deployed my
>DB.
>I've also deployed an app (programmed with C# in .net) which access that DB.
>Is there any chance to access that DB without installing the SQL Client?
>It is very urgent.
>Many thx.
I have a server with MSSQL Server installed there in which I've deployed my
DB.
I've also deployed an app (programmed with C# in .net) which access that DB.
Is there any chance to access that DB without installing the SQL Client?
It is very urgent.
Many thx.
SqlClient is part of the .NET Framework -- there is no separate
install and you can't uninstall the Framework when you're using C#.
However, I'm curious as to why you have a compelling need to uninstall
it.
--Mary
On Fri, 31 Mar 2006 00:56:02 -0800, Oscar
<Oscar@.discussions.microsoft.com> wrote:
>Hi,
>I have a server with MSSQL Server installed there in which I've deployed my
>DB.
>I've also deployed an app (programmed with C# in .net) which access that DB.
>Is there any chance to access that DB without installing the SQL Client?
>It is very urgent.
>Many thx.
Wednesday, March 7, 2012
Connecting to a remote SQL Server
I am trying to connect to a SQL Server that is located in my home office from
remote office location. I've tried to setup a connection using Enterprise
Mgr, but it is not working. Can someone provide the steps if any to help?
Thanks
Sonya,
Have you tried registering the server using the IP address?
HTH
Jerry
"Sonya" <Sonya@.discussions.microsoft.com> wrote in message
news:4AE2C68B-3B14-4A88-A38F-716276A824EC@.microsoft.com...
>I am trying to connect to a SQL Server that is located in my home office
>from
> remote office location. I've tried to setup a connection using Enterprise
> Mgr, but it is not working. Can someone provide the steps if any to help?
> Thanks
|||Yes but it didn't find it. I can ping it, I tried to see if registered my
laptop db svr but it didn't.
"Sonya" wrote:
> I am trying to connect to a SQL Server that is located in my home office from
> remote office location. I've tried to setup a connection using Enterprise
> Mgr, but it is not working. Can someone provide the steps if any to help?
> Thanks
|||Sonya wrote:[vbcol=seagreen]
> Yes but it didn't find it. I can ping it, I tried to see if registered my
> laptop db svr but it didn't.
> "Sonya" wrote:
You'll most likely have Firewalls in between the 2 servers, so you need
to make sure that these allow SQL Server communication. If both
servers/pc's are installed with default settings, it will be port 1433
that is used. You can check this fairly easy by doing a telnet command
to the server (in a cmd prompt type "telnet YourRemoteServerIpAdresse
1433"). If you get to a blank screen, you have contact to the server on
that port. If the port it blocked you'll get an error message after a
short while telling you that the host could not be reached (...I can't
remember the exact message...).
Regards
Steen
remote office location. I've tried to setup a connection using Enterprise
Mgr, but it is not working. Can someone provide the steps if any to help?
Thanks
Sonya,
Have you tried registering the server using the IP address?
HTH
Jerry
"Sonya" <Sonya@.discussions.microsoft.com> wrote in message
news:4AE2C68B-3B14-4A88-A38F-716276A824EC@.microsoft.com...
>I am trying to connect to a SQL Server that is located in my home office
>from
> remote office location. I've tried to setup a connection using Enterprise
> Mgr, but it is not working. Can someone provide the steps if any to help?
> Thanks
|||Yes but it didn't find it. I can ping it, I tried to see if registered my
laptop db svr but it didn't.
"Sonya" wrote:
> I am trying to connect to a SQL Server that is located in my home office from
> remote office location. I've tried to setup a connection using Enterprise
> Mgr, but it is not working. Can someone provide the steps if any to help?
> Thanks
|||Sonya wrote:[vbcol=seagreen]
> Yes but it didn't find it. I can ping it, I tried to see if registered my
> laptop db svr but it didn't.
> "Sonya" wrote:
You'll most likely have Firewalls in between the 2 servers, so you need
to make sure that these allow SQL Server communication. If both
servers/pc's are installed with default settings, it will be port 1433
that is used. You can check this fairly easy by doing a telnet command
to the server (in a cmd prompt type "telnet YourRemoteServerIpAdresse
1433"). If you get to a blank screen, you have contact to the server on
that port. If the port it blocked you'll get an error message after a
short while telling you that the host could not be reached (...I can't
remember the exact message...).
Regards
Steen
Connecting to a remote OLE DB
Hey, all. I've mainly worked with MySQL databases before. I'm working on an (old) ASP page that uses this connection string:
strConnect ="Provider=SQLOLEDB; Data Source=SQL1.MYDBSERVER.NET; Initial Catalog=...; User ID=...; Password=..."It works fine on the production server, but the local copy fails if I try to access the Products page (which uses the database), with this error:
Microsoft OLE DB Providerfor SQL Server (0x80004005)
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
/html/products.asp, line 19
Similarly, if I plug the connection info into Tools/Connect to Database in Visual Studio, I get:
Connection failed:
SQLState:'08001'SQL Server Error: 17[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied.
Am I doing something wrong? Do I need more info from the hosting provider to connect remotely? Or is the database not accepting remote connections at all?
Thanks in advance for your help!
It might be that you do not have permission to access it or it might be that database is old (version 7.0) and that you cannot connect from Management studio. Check it with hosting provider.
Connecting to a MSDE server in Internet
Hi !!
I would like to connect to a SQL Server (MSDE edition) that's in Internet,
using Enterprise Manager either Query Analizer. For these I've configured
the client tool as:
Server Alias: INET_SERVER
Net: TCP/IP
Connection parameters:
Server name: [DNS_NAME]\[REMOTE_SERVER_NAME]\[INSTANCE_NAME]
Port number: 1433
Althought I've tried to configure the server name in different ways, I
haven't found the successful way to do it.
I don't think it's a firewall problem. In theory I've successfull disabled.
Thanks !!
Josep.
You can check to see if it's a firewall or port blocking issue or not by
using TELNET and seeing if it can connect. Type this from a command
prompt (replace INET_SERVER with your server name).
telnet INET_SERVER 1433
If the telnet session fails to connect, you have a firewall issue or are
not using the correct port or host name - when I try to connect to
something that is blocked by a firewall, the error reported for me was
"could not open connection to the host on port xxxx: Connect failed".
If you get a screen that appears to be the start of the connected
session, you can be sure you have actually opened a port to another
machine. You won't be able to do anything meaningful from this telnet
session, but it rules out firewall, port, or hostname issues. Close it
and use the same settings to connect with Query Analyzer or Enterprise
Manager.
Good luck,
Tony Sebion
"Josep" <hola@.microsoft.com> wrote in message
news:#1fFelMxFHA.700@.TK2MSFTNGP11.phx.gbl:
> Hi !!
> I would like to connect to a SQL Server (MSDE edition) that's in Internet,
> using Enterprise Manager either Query Analizer. For these I've configured
> the client tool as:
> Server Alias: INET_SERVER
> Net: TCP/IP
> Connection parameters:
> Server name: [DNS_NAME]\[REMOTE_SERVER_NAME]\[INSTANCE_NAME]
> Port number: 1433
> Althought I've tried to configure the server name in different ways, I
> haven't found the successful way to do it.
> I don't think it's a firewall problem. In theory I've successfull disabled.
>
> Thanks !!
> Josep.
|||Well, it seems I didn't unblock the port successfully. So, my work is to
find how this router works... where else I've to configure the ports... but
I like to know that's not an SQL Server problem :-)
Thank you Tony for explaining me this very fast way, and easy, to know if a
port is blocked or not :D
Josep.
"Tony Sebion" <tony@.sebion.com> escribi en el mensaje
news:3q2bkiFcpoaaU1@.individual.net...
> You can check to see if it's a firewall or port blocking issue or not by
> using TELNET and seeing if it can connect. Type this from a command
> prompt (replace INET_SERVER with your server name).
> telnet INET_SERVER 1433
> If the telnet session fails to connect, you have a firewall issue or are
> not using the correct port or host name - when I try to connect to
> something that is blocked by a firewall, the error reported for me was
> "could not open connection to the host on port xxxx: Connect failed".
> If you get a screen that appears to be the start of the connected session,
> you can be sure you have actually opened a port to another machine. You
> won't be able to do anything meaningful from this telnet session, but it
> rules out firewall, port, or hostname issues. Close it and use the same
> settings to connect with Query Analyzer or Enterprise Manager.
> Good luck,
> Tony Sebion
> "Josep" <hola@.microsoft.com> wrote in message
> news:#1fFelMxFHA.700@.TK2MSFTNGP11.phx.gbl:
>
|||Josep,
did you can do it? I have the same problem here. I think is not due to
firewall, all those ports are opened. (1433TCP; 1434UDP!)
Thank you,
Leo-
"Josep" <hola@.microsoft.com> escribi en el mensaje
news:%231$1wmaxFHA.4032@.TK2MSFTNGP15.phx.gbl...
> Well, it seems I didn't unblock the port successfully. So, my work is to
> find how this router works... where else I've to configure the ports...
> but I like to know that's not an SQL Server problem :-)
> Thank you Tony for explaining me this very fast way, and easy, to know if
> a port is blocked or not :D
> Josep.
>
> "Tony Sebion" <tony@.sebion.com> escribi en el mensaje
> news:3q2bkiFcpoaaU1@.individual.net...
>
I would like to connect to a SQL Server (MSDE edition) that's in Internet,
using Enterprise Manager either Query Analizer. For these I've configured
the client tool as:
Server Alias: INET_SERVER
Net: TCP/IP
Connection parameters:
Server name: [DNS_NAME]\[REMOTE_SERVER_NAME]\[INSTANCE_NAME]
Port number: 1433
Althought I've tried to configure the server name in different ways, I
haven't found the successful way to do it.
I don't think it's a firewall problem. In theory I've successfull disabled.
Thanks !!
Josep.
You can check to see if it's a firewall or port blocking issue or not by
using TELNET and seeing if it can connect. Type this from a command
prompt (replace INET_SERVER with your server name).
telnet INET_SERVER 1433
If the telnet session fails to connect, you have a firewall issue or are
not using the correct port or host name - when I try to connect to
something that is blocked by a firewall, the error reported for me was
"could not open connection to the host on port xxxx: Connect failed".
If you get a screen that appears to be the start of the connected
session, you can be sure you have actually opened a port to another
machine. You won't be able to do anything meaningful from this telnet
session, but it rules out firewall, port, or hostname issues. Close it
and use the same settings to connect with Query Analyzer or Enterprise
Manager.
Good luck,
Tony Sebion
"Josep" <hola@.microsoft.com> wrote in message
news:#1fFelMxFHA.700@.TK2MSFTNGP11.phx.gbl:
> Hi !!
> I would like to connect to a SQL Server (MSDE edition) that's in Internet,
> using Enterprise Manager either Query Analizer. For these I've configured
> the client tool as:
> Server Alias: INET_SERVER
> Net: TCP/IP
> Connection parameters:
> Server name: [DNS_NAME]\[REMOTE_SERVER_NAME]\[INSTANCE_NAME]
> Port number: 1433
> Althought I've tried to configure the server name in different ways, I
> haven't found the successful way to do it.
> I don't think it's a firewall problem. In theory I've successfull disabled.
>
> Thanks !!
> Josep.
|||Well, it seems I didn't unblock the port successfully. So, my work is to
find how this router works... where else I've to configure the ports... but
I like to know that's not an SQL Server problem :-)
Thank you Tony for explaining me this very fast way, and easy, to know if a
port is blocked or not :D
Josep.
"Tony Sebion" <tony@.sebion.com> escribi en el mensaje
news:3q2bkiFcpoaaU1@.individual.net...
> You can check to see if it's a firewall or port blocking issue or not by
> using TELNET and seeing if it can connect. Type this from a command
> prompt (replace INET_SERVER with your server name).
> telnet INET_SERVER 1433
> If the telnet session fails to connect, you have a firewall issue or are
> not using the correct port or host name - when I try to connect to
> something that is blocked by a firewall, the error reported for me was
> "could not open connection to the host on port xxxx: Connect failed".
> If you get a screen that appears to be the start of the connected session,
> you can be sure you have actually opened a port to another machine. You
> won't be able to do anything meaningful from this telnet session, but it
> rules out firewall, port, or hostname issues. Close it and use the same
> settings to connect with Query Analyzer or Enterprise Manager.
> Good luck,
> Tony Sebion
> "Josep" <hola@.microsoft.com> wrote in message
> news:#1fFelMxFHA.700@.TK2MSFTNGP11.phx.gbl:
>
|||Josep,
did you can do it? I have the same problem here. I think is not due to
firewall, all those ports are opened. (1433TCP; 1434UDP!)
Thank you,
Leo-
"Josep" <hola@.microsoft.com> escribi en el mensaje
news:%231$1wmaxFHA.4032@.TK2MSFTNGP15.phx.gbl...
> Well, it seems I didn't unblock the port successfully. So, my work is to
> find how this router works... where else I've to configure the ports...
> but I like to know that's not an SQL Server problem :-)
> Thank you Tony for explaining me this very fast way, and easy, to know if
> a port is blocked or not :D
> Josep.
>
> "Tony Sebion" <tony@.sebion.com> escribi en el mensaje
> news:3q2bkiFcpoaaU1@.individual.net...
>
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
>
>
Friday, February 24, 2012
Connecting on the Server
Hi,
I've SQL 2000 Server installed in a Windows 2000 Server.
On the Server When I try to connect to the instance it
gives me the error "invalid identifier". I've tried to
reconfigure the connection but it never works.
On the WorkStations where I've installed the client tools
i can connect by the entreprise manager with no problem.
Can anyone give some clues why this appends!
Thanks in advance.
What is the EXACT error you get and what are you doing when you get it
(what tool, what connection parameters, etc.)? What version of MDAC is on
the client machines (note that older versions of cannot connect to named
instances without a workaround).
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
I've SQL 2000 Server installed in a Windows 2000 Server.
On the Server When I try to connect to the instance it
gives me the error "invalid identifier". I've tried to
reconfigure the connection but it never works.
On the WorkStations where I've installed the client tools
i can connect by the entreprise manager with no problem.
Can anyone give some clues why this appends!
Thanks in advance.
What is the EXACT error you get and what are you doing when you get it
(what tool, what connection parameters, etc.)? What version of MDAC is on
the client machines (note that older versions of cannot connect to named
instances without a workaround).
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, February 17, 2012
Connecting an existing database to Management Studio
Hello,
I use visual studio express 2005, and just downloaded Management Studio Express. (I have SQL Express).
I've already created my projects and created database tables and everything but I do not know how to connect an existing database to management studio. Can someone tell me how to connect an existing database to management studio?
Thanks,
Computergirl
Here are few links that can help you
http://technet.microsoft.com/en-us/library/ms167593.aspx
http://technet.microsoft.com/en-us/library/ms170681.aspx
Tuesday, February 14, 2012
connect using a non-interactive user
Hi,
I've been searching the web for some time, without any luck ...
Is it possible to connect to a SQL Server using a domain account that is
marked as a non-interactive user ?
Thanks,
Marc
"Marc Nemegeer" <nemegeermATdelaware.be.NOSPAM> wrote in message
news:eOPNDNg$EHA.4028@.TK2MSFTNGP15.phx.gbl...
> I've been searching the web for some time, without any luck ...
> Is it possible to connect to a SQL Server using a domain account that is
> marked as a non-interactive user ?
Where are you setting that option, on the server local security option, or
through group policy? Seems like it should be easy to test...
Steve
I've been searching the web for some time, without any luck ...
Is it possible to connect to a SQL Server using a domain account that is
marked as a non-interactive user ?
Thanks,
Marc
"Marc Nemegeer" <nemegeermATdelaware.be.NOSPAM> wrote in message
news:eOPNDNg$EHA.4028@.TK2MSFTNGP15.phx.gbl...
> I've been searching the web for some time, without any luck ...
> Is it possible to connect to a SQL Server using a domain account that is
> marked as a non-interactive user ?
Where are you setting that option, on the server local security option, or
through group policy? Seems like it should be easy to test...
Steve
Sunday, February 12, 2012
Connect to SQL Server from Workgroup Computer
I have been using Windows XP SP 2 and SQL Server 2000 Developer's edition on
one computer and it has worked fine. For testing, I've installed Query
Analyzer on a 2nd, workgroup computer. I know the network itself is
working. Files and printers are shared and working.
The problem is that ODBC and Query Analyzer on computer 2 cannot connect to
the SQL Server on computer 1.
The message returned is "SQL Server does not exist or access denied".
I suspect SQL Server is not hearing the connection request.
The user name I am using (Windows authentication) is MST, and this name has
a login ( COMP!\MST). When I try to login from computer2, I suppose the
login is COMP2\MST ? At any rate, I cannot add this login to SQL server.
Using SQL authentication, I can log in on computer 1 via Query Analyzer with
a different user name and password, but I receive the message above when I
try to log in via QA from computer 2.
Can anyone point me in the right direction to solving this?
Thanks
Mike Thomas
Solved this one myself, but it does not make much sense.
On the client computer, I opened Client Network Utility and in the Alias >
Edit tab changed the name of the 'Server Alias' to something different from
the 'Server Name'. Now, I can at least connect using SQL Authetication.
Next hurdle is Windows authentication.
Mike Thomas
"Mike Thomas" <mike@.ease.com> wrote in message
news:%23JP%23NjbFFHA.2052@.TK2MSFTNGP09.phx.gbl...
>I have been using Windows XP SP 2 and SQL Server 2000 Developer's edition
>on one computer and it has worked fine. For testing, I've installed Query
>Analyzer on a 2nd, workgroup computer. I know the network itself is
>working. Files and printers are shared and working.
> The problem is that ODBC and Query Analyzer on computer 2 cannot connect
> to the SQL Server on computer 1.
> The message returned is "SQL Server does not exist or access denied".
> I suspect SQL Server is not hearing the connection request.
> The user name I am using (Windows authentication) is MST, and this name
> has a login ( COMP!\MST). When I try to login from computer2, I suppose
> the login is COMP2\MST ? At any rate, I cannot add this login to SQL
> server.
> Using SQL authentication, I can log in on computer 1 via Query Analyzer
> with a different user name and password, but I receive the message above
> when I try to log in via QA from computer 2.
> Can anyone point me in the right direction to solving this?
> Thanks
> Mike Thomas
>
one computer and it has worked fine. For testing, I've installed Query
Analyzer on a 2nd, workgroup computer. I know the network itself is
working. Files and printers are shared and working.
The problem is that ODBC and Query Analyzer on computer 2 cannot connect to
the SQL Server on computer 1.
The message returned is "SQL Server does not exist or access denied".
I suspect SQL Server is not hearing the connection request.
The user name I am using (Windows authentication) is MST, and this name has
a login ( COMP!\MST). When I try to login from computer2, I suppose the
login is COMP2\MST ? At any rate, I cannot add this login to SQL server.
Using SQL authentication, I can log in on computer 1 via Query Analyzer with
a different user name and password, but I receive the message above when I
try to log in via QA from computer 2.
Can anyone point me in the right direction to solving this?
Thanks
Mike Thomas
Solved this one myself, but it does not make much sense.
On the client computer, I opened Client Network Utility and in the Alias >
Edit tab changed the name of the 'Server Alias' to something different from
the 'Server Name'. Now, I can at least connect using SQL Authetication.
Next hurdle is Windows authentication.
Mike Thomas
"Mike Thomas" <mike@.ease.com> wrote in message
news:%23JP%23NjbFFHA.2052@.TK2MSFTNGP09.phx.gbl...
>I have been using Windows XP SP 2 and SQL Server 2000 Developer's edition
>on one computer and it has worked fine. For testing, I've installed Query
>Analyzer on a 2nd, workgroup computer. I know the network itself is
>working. Files and printers are shared and working.
> The problem is that ODBC and Query Analyzer on computer 2 cannot connect
> to the SQL Server on computer 1.
> The message returned is "SQL Server does not exist or access denied".
> I suspect SQL Server is not hearing the connection request.
> The user name I am using (Windows authentication) is MST, and this name
> has a login ( COMP!\MST). When I try to login from computer2, I suppose
> the login is COMP2\MST ? At any rate, I cannot add this login to SQL
> server.
> Using SQL authentication, I can log in on computer 1 via Query Analyzer
> with a different user name and password, but I receive the message above
> when I try to log in via QA from computer 2.
> Can anyone point me in the right direction to solving this?
> Thanks
> Mike Thomas
>
Connect to SQL Server from Client Using Windows Authentication
On a newly installed workgroup computer, the client, I've been able to
establish connections to the SQL Server on a different computer using SQL
authentication via ODBC and Query Analyzer.
Now I am trying to figure out how to connect with WIndows authentication.
On the client computer (PCMAX04), when I try to login to SQL Server via QA,
the error reads "Login failed for user DELLJAN2005\Guest" even though I am
logged in to the client computer as MST.
DELLJAN2005 is the name of the SQL Server and the computer on which it is
installed.
In SQL Server, there is a login named "DELLJAN2005\MST".
How can it arrange it so that when I log on from the client computer using
Windows authentication, SQL Server interprets the login as being for "MST"?
Many thanks,
Mike Thomas
You don't mention the specific operating systems involved.
With XP home, authentication is done using the guest account
as simple file sharing is always enabled on XP Home. You
could hit the issue with XP Pro if simple file sharing is
used. It's optional but is the default with XP Pro. How you
address the issue depends somewhat on what specific
operating systems are involved. Refer to the following for
more info:
SQL Server clients are authenticated as guests if Simple
File Sharing is enabled
http://support.microsoft.com/?id=831133
-Sue
On Fri, 18 Feb 2005 09:38:43 -0500, "Mike Thomas"
<mike@.ease.com> wrote:
>On a newly installed workgroup computer, the client, I've been able to
>establish connections to the SQL Server on a different computer using SQL
>authentication via ODBC and Query Analyzer.
>Now I am trying to figure out how to connect with WIndows authentication.
>On the client computer (PCMAX04), when I try to login to SQL Server via QA,
>the error reads "Login failed for user DELLJAN2005\Guest" even though I am
>logged in to the client computer as MST.
>DELLJAN2005 is the name of the SQL Server and the computer on which it is
>installed.
>In SQL Server, there is a login named "DELLJAN2005\MST".
>How can it arrange it so that when I log on from the client computer using
>Windows authentication, SQL Server interprets the login as being for "MST"?
>Many thanks,
>Mike Thomas
>
>
>
>
establish connections to the SQL Server on a different computer using SQL
authentication via ODBC and Query Analyzer.
Now I am trying to figure out how to connect with WIndows authentication.
On the client computer (PCMAX04), when I try to login to SQL Server via QA,
the error reads "Login failed for user DELLJAN2005\Guest" even though I am
logged in to the client computer as MST.
DELLJAN2005 is the name of the SQL Server and the computer on which it is
installed.
In SQL Server, there is a login named "DELLJAN2005\MST".
How can it arrange it so that when I log on from the client computer using
Windows authentication, SQL Server interprets the login as being for "MST"?
Many thanks,
Mike Thomas
You don't mention the specific operating systems involved.
With XP home, authentication is done using the guest account
as simple file sharing is always enabled on XP Home. You
could hit the issue with XP Pro if simple file sharing is
used. It's optional but is the default with XP Pro. How you
address the issue depends somewhat on what specific
operating systems are involved. Refer to the following for
more info:
SQL Server clients are authenticated as guests if Simple
File Sharing is enabled
http://support.microsoft.com/?id=831133
-Sue
On Fri, 18 Feb 2005 09:38:43 -0500, "Mike Thomas"
<mike@.ease.com> wrote:
>On a newly installed workgroup computer, the client, I've been able to
>establish connections to the SQL Server on a different computer using SQL
>authentication via ODBC and Query Analyzer.
>Now I am trying to figure out how to connect with WIndows authentication.
>On the client computer (PCMAX04), when I try to login to SQL Server via QA,
>the error reads "Login failed for user DELLJAN2005\Guest" even though I am
>logged in to the client computer as MST.
>DELLJAN2005 is the name of the SQL Server and the computer on which it is
>installed.
>In SQL Server, there is a login named "DELLJAN2005\MST".
>How can it arrange it so that when I log on from the client computer using
>Windows authentication, SQL Server interprets the login as being for "MST"?
>Many thanks,
>Mike Thomas
>
>
>
>
Subscribe to:
Posts (Atom)