I was just reading
http://msdn2.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx about
connection pooling with SQL server and came across the follwoing:
**************
Pool Fragmentation
Pool fragmentation is a common problem in many Web applications where the
application can create a large number of pools that are not freed until the
process exits. This leaves a large number of connections open while consuming
memory, resulting in poor performance.
Pool Fragmentation Due to Integrated Security
Connections are pooled according to the connection string plus the user
identity. Therefore, if you use Basic authentication or Windows
Authentication on the Web site and an integrated security login, you get one
pool per user. Although this improves the performance of subsequent database
requests for a single user, that user cannot take advantage of connections
made by other users. It also results in at least one connection per user to
the database server. This is a side effect of a particular Web application
architecture that developers need to weigh against security and auditing
requirements.
**************
I'm not sure that I understand what this really means. Can someone help me
understand?
In our environment, each user is logging into the web based app with their
own unique id, but the app connects to the db as a single login.
Tia
--
MGWhat matters is how the connection to the database is
handled. If the site is authenticating to the database using
impersonation or the app pool identity and just using the
one login, then the connection is reused. The credentials
being used are the same.
If it were setup to use delegation and integrated security,
when user A logs in one connection is used. When user B logs
in, a different connection would be used. The credentials
being used are different as one is for user A and one is for
User B. In this scenario, you need a connection for each
user.
In terms of weighing the performance vs security and
auditing, when the same credentials are used then it's that
log in that is seen in SQL Server as the user who accessed
or modified the data. You don't know the actual user, you
only know that it was the single account used by the app.
In the second scenario, SQL Server will see the access,
modification as done by the actual logged in users.
-Sue
On Fri, 10 Aug 2007 08:57:13 -0700, Hurme
<michael.geles@.thomson.com> wrote:
>I was just reading
>http://msdn2.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx about
>connection pooling with SQL server and came across the follwoing:
>**************
>Pool Fragmentation
>Pool fragmentation is a common problem in many Web applications where the
>application can create a large number of pools that are not freed until the
>process exits. This leaves a large number of connections open while consuming
>memory, resulting in poor performance.
>Pool Fragmentation Due to Integrated Security
>Connections are pooled according to the connection string plus the user
>identity. Therefore, if you use Basic authentication or Windows
>Authentication on the Web site and an integrated security login, you get one
>pool per user. Although this improves the performance of subsequent database
>requests for a single user, that user cannot take advantage of connections
>made by other users. It also results in at least one connection per user to
>the database server. This is a side effect of a particular Web application
>architecture that developers need to weigh against security and auditing
>requirements.
>**************
>I'm not sure that I understand what this really means. Can someone help me
>understand?
>In our environment, each user is logging into the web based app with their
>own unique id, but the app connects to the db as a single login.
>Tia
Showing posts with label across. Show all posts
Showing posts with label across. Show all posts
Thursday, March 22, 2012
Connection Pool Fragmentation
I was just reading
http://msdn2.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx about
connection pooling with SQL server and came across the follwoing:
**************
Pool Fragmentation
Pool fragmentation is a common problem in many Web applications where the
application can create a large number of pools that are not freed until the
process exits. This leaves a large number of connections open while consuming
memory, resulting in poor performance.
Pool Fragmentation Due to Integrated Security
Connections are pooled according to the connection string plus the user
identity. Therefore, if you use Basic authentication or Windows
Authentication on the Web site and an integrated security login, you get one
pool per user. Although this improves the performance of subsequent database
requests for a single user, that user cannot take advantage of connections
made by other users. It also results in at least one connection per user to
the database server. This is a side effect of a particular Web application
architecture that developers need to weigh against security and auditing
requirements.
**************
I'm not sure that I understand what this really means. Can someone help me
understand?
In our environment, each user is logging into the web based app with their
own unique id, but the app connects to the db as a single login.
Tia
MG
What matters is how the connection to the database is
handled. If the site is authenticating to the database using
impersonation or the app pool identity and just using the
one login, then the connection is reused. The credentials
being used are the same.
If it were setup to use delegation and integrated security,
when user A logs in one connection is used. When user B logs
in, a different connection would be used. The credentials
being used are different as one is for user A and one is for
User B. In this scenario, you need a connection for each
user.
In terms of weighing the performance vs security and
auditing, when the same credentials are used then it's that
log in that is seen in SQL Server as the user who accessed
or modified the data. You don't know the actual user, you
only know that it was the single account used by the app.
In the second scenario, SQL Server will see the access,
modification as done by the actual logged in users.
-Sue
On Fri, 10 Aug 2007 08:57:13 -0700, Hurme
<michael.geles@.thomson.com> wrote:
>I was just reading
>http://msdn2.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx about
>connection pooling with SQL server and came across the follwoing:
>**************
>Pool Fragmentation
>Pool fragmentation is a common problem in many Web applications where the
>application can create a large number of pools that are not freed until the
>process exits. This leaves a large number of connections open while consuming
>memory, resulting in poor performance.
>Pool Fragmentation Due to Integrated Security
>Connections are pooled according to the connection string plus the user
>identity. Therefore, if you use Basic authentication or Windows
>Authentication on the Web site and an integrated security login, you get one
>pool per user. Although this improves the performance of subsequent database
>requests for a single user, that user cannot take advantage of connections
>made by other users. It also results in at least one connection per user to
>the database server. This is a side effect of a particular Web application
>architecture that developers need to weigh against security and auditing
>requirements.
>**************
>I'm not sure that I understand what this really means. Can someone help me
>understand?
>In our environment, each user is logging into the web based app with their
>own unique id, but the app connects to the db as a single login.
>Tia
http://msdn2.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx about
connection pooling with SQL server and came across the follwoing:
**************
Pool Fragmentation
Pool fragmentation is a common problem in many Web applications where the
application can create a large number of pools that are not freed until the
process exits. This leaves a large number of connections open while consuming
memory, resulting in poor performance.
Pool Fragmentation Due to Integrated Security
Connections are pooled according to the connection string plus the user
identity. Therefore, if you use Basic authentication or Windows
Authentication on the Web site and an integrated security login, you get one
pool per user. Although this improves the performance of subsequent database
requests for a single user, that user cannot take advantage of connections
made by other users. It also results in at least one connection per user to
the database server. This is a side effect of a particular Web application
architecture that developers need to weigh against security and auditing
requirements.
**************
I'm not sure that I understand what this really means. Can someone help me
understand?
In our environment, each user is logging into the web based app with their
own unique id, but the app connects to the db as a single login.
Tia
MG
What matters is how the connection to the database is
handled. If the site is authenticating to the database using
impersonation or the app pool identity and just using the
one login, then the connection is reused. The credentials
being used are the same.
If it were setup to use delegation and integrated security,
when user A logs in one connection is used. When user B logs
in, a different connection would be used. The credentials
being used are different as one is for user A and one is for
User B. In this scenario, you need a connection for each
user.
In terms of weighing the performance vs security and
auditing, when the same credentials are used then it's that
log in that is seen in SQL Server as the user who accessed
or modified the data. You don't know the actual user, you
only know that it was the single account used by the app.
In the second scenario, SQL Server will see the access,
modification as done by the actual logged in users.
-Sue
On Fri, 10 Aug 2007 08:57:13 -0700, Hurme
<michael.geles@.thomson.com> wrote:
>I was just reading
>http://msdn2.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx about
>connection pooling with SQL server and came across the follwoing:
>**************
>Pool Fragmentation
>Pool fragmentation is a common problem in many Web applications where the
>application can create a large number of pools that are not freed until the
>process exits. This leaves a large number of connections open while consuming
>memory, resulting in poor performance.
>Pool Fragmentation Due to Integrated Security
>Connections are pooled according to the connection string plus the user
>identity. Therefore, if you use Basic authentication or Windows
>Authentication on the Web site and an integrated security login, you get one
>pool per user. Although this improves the performance of subsequent database
>requests for a single user, that user cannot take advantage of connections
>made by other users. It also results in at least one connection per user to
>the database server. This is a side effect of a particular Web application
>architecture that developers need to weigh against security and auditing
>requirements.
>**************
>I'm not sure that I understand what this really means. Can someone help me
>understand?
>In our environment, each user is logging into the web based app with their
>own unique id, but the app connects to the db as a single login.
>Tia
Connection Pool Fragmentation
I was just reading
http://msdn2.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx about
connection pooling with SQL server and came across the follwoing:
**************
Pool Fragmentation
Pool fragmentation is a common problem in many Web applications where the
application can create a large number of pools that are not freed until the
process exits. This leaves a large number of connections open while consumin
g
memory, resulting in poor performance.
Pool Fragmentation Due to Integrated Security
Connections are pooled according to the connection string plus the user
identity. Therefore, if you use Basic authentication or Windows
Authentication on the Web site and an integrated security login, you get one
pool per user. Although this improves the performance of subsequent database
requests for a single user, that user cannot take advantage of connections
made by other users. It also results in at least one connection per user to
the database server. This is a side effect of a particular Web application
architecture that developers need to weigh against security and auditing
requirements.
**************
I'm not sure that I understand what this really means. Can someone help me
understand?
In our environment, each user is logging into the web based app with their
own unique id, but the app connects to the db as a single login.
Tia
--
MGWhat matters is how the connection to the database is
handled. If the site is authenticating to the database using
impersonation or the app pool identity and just using the
one login, then the connection is reused. The credentials
being used are the same.
If it were setup to use delegation and integrated security,
when user A logs in one connection is used. When user B logs
in, a different connection would be used. The credentials
being used are different as one is for user A and one is for
User B. In this scenario, you need a connection for each
user.
In terms of weighing the performance vs security and
auditing, when the same credentials are used then it's that
log in that is seen in SQL Server as the user who accessed
or modified the data. You don't know the actual user, you
only know that it was the single account used by the app.
In the second scenario, SQL Server will see the access,
modification as done by the actual logged in users.
-Sue
On Fri, 10 Aug 2007 08:57:13 -0700, Hurme
<michael.geles@.thomson.com> wrote:
>I was just reading
>http://msdn2.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx about
>connection pooling with SQL server and came across the follwoing:
>**************
>Pool Fragmentation
>Pool fragmentation is a common problem in many Web applications where the
>application can create a large number of pools that are not freed until the
>process exits. This leaves a large number of connections open while consumi
ng
>memory, resulting in poor performance.
>Pool Fragmentation Due to Integrated Security
>Connections are pooled according to the connection string plus the user
>identity. Therefore, if you use Basic authentication or Windows
>Authentication on the Web site and an integrated security login, you get on
e
>pool per user. Although this improves the performance of subsequent databas
e
>requests for a single user, that user cannot take advantage of connections
>made by other users. It also results in at least one connection per user to
>the database server. This is a side effect of a particular Web application
>architecture that developers need to weigh against security and auditing
>requirements.
>**************
>I'm not sure that I understand what this really means. Can someone help me
>understand?
>In our environment, each user is logging into the web based app with their
>own unique id, but the app connects to the db as a single login.
>Tiasqlsql
http://msdn2.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx about
connection pooling with SQL server and came across the follwoing:
**************
Pool Fragmentation
Pool fragmentation is a common problem in many Web applications where the
application can create a large number of pools that are not freed until the
process exits. This leaves a large number of connections open while consumin
g
memory, resulting in poor performance.
Pool Fragmentation Due to Integrated Security
Connections are pooled according to the connection string plus the user
identity. Therefore, if you use Basic authentication or Windows
Authentication on the Web site and an integrated security login, you get one
pool per user. Although this improves the performance of subsequent database
requests for a single user, that user cannot take advantage of connections
made by other users. It also results in at least one connection per user to
the database server. This is a side effect of a particular Web application
architecture that developers need to weigh against security and auditing
requirements.
**************
I'm not sure that I understand what this really means. Can someone help me
understand?
In our environment, each user is logging into the web based app with their
own unique id, but the app connects to the db as a single login.
Tia
--
MGWhat matters is how the connection to the database is
handled. If the site is authenticating to the database using
impersonation or the app pool identity and just using the
one login, then the connection is reused. The credentials
being used are the same.
If it were setup to use delegation and integrated security,
when user A logs in one connection is used. When user B logs
in, a different connection would be used. The credentials
being used are different as one is for user A and one is for
User B. In this scenario, you need a connection for each
user.
In terms of weighing the performance vs security and
auditing, when the same credentials are used then it's that
log in that is seen in SQL Server as the user who accessed
or modified the data. You don't know the actual user, you
only know that it was the single account used by the app.
In the second scenario, SQL Server will see the access,
modification as done by the actual logged in users.
-Sue
On Fri, 10 Aug 2007 08:57:13 -0700, Hurme
<michael.geles@.thomson.com> wrote:
>I was just reading
>http://msdn2.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx about
>connection pooling with SQL server and came across the follwoing:
>**************
>Pool Fragmentation
>Pool fragmentation is a common problem in many Web applications where the
>application can create a large number of pools that are not freed until the
>process exits. This leaves a large number of connections open while consumi
ng
>memory, resulting in poor performance.
>Pool Fragmentation Due to Integrated Security
>Connections are pooled according to the connection string plus the user
>identity. Therefore, if you use Basic authentication or Windows
>Authentication on the Web site and an integrated security login, you get on
e
>pool per user. Although this improves the performance of subsequent databas
e
>requests for a single user, that user cannot take advantage of connections
>made by other users. It also results in at least one connection per user to
>the database server. This is a side effect of a particular Web application
>architecture that developers need to weigh against security and auditing
>requirements.
>**************
>I'm not sure that I understand what this really means. Can someone help me
>understand?
>In our environment, each user is logging into the web based app with their
>own unique id, but the app connects to the db as a single login.
>Tiasqlsql
Monday, March 19, 2012
Connection issue across network
I have about 30 machines that I currently manage. I should also say, I just
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from my
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
Raymond Laubert
MCSE, MCDBA, MCT
So you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I just
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
> is the problem, I can not connect to this box from Enterprise Manager from my
> desktop. If I Remote Admin into the box everything works fine. If I try to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted my
> authenication as trusted. SQL is using the standard TCP port 1433.
> Any ideas?
> Thanks,
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can ping
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
> c.. On the client, is the firewall configured to permit access to the ports?
> d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from my
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
Raymond Laubert
MCSE, MCDBA, MCT
So you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I just
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
> is the problem, I can not connect to this box from Enterprise Manager from my
> desktop. If I Remote Admin into the box everything works fine. If I try to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted my
> authenication as trusted. SQL is using the standard TCP port 1433.
> Any ideas?
> Thanks,
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can ping
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
> c.. On the client, is the firewall configured to permit access to the ports?
> d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
Connection issue across network
I have about 30 machines that I currently manage. I should also say, I just
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from m
y
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
--
Raymond Laubert
MCSE, MCDBA, MCTSo you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and t
he server ports must be visible outside of the box. Here are a few things to
check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config
tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server
resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the C
onnectionString)
f.. Does the server show up in the list of visible servers in Server Explore
r (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does i
t lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4
562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I jus
t
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in t
he
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Her
e
> is the problem, I can not connect to this box from Enterprise Manager from
my
> desktop. If I Remote Admin into the box everything works fine. If I try
to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log
in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted m
y
> authenication as trusted. SQL is using the standard TCP port 1433.
>
> Any ideas?
>
> Thanks,
>
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can pin
g
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
--
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and
the server ports must be visible outside of the box. Here are a few things
to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Con
fig tool)
> c.. On the client, is the firewall configured to permit access to the po
rts?
> d.. Are you trying to connect to the ports or are you letting the DNS se
rver resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see t
he ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Exp
lorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and do
es it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89
-488A-9AFB-B44A6B4562BC@.microsoft.com...|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
>
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from m
y
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
--
Raymond Laubert
MCSE, MCDBA, MCTSo you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and t
he server ports must be visible outside of the box. Here are a few things to
check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config
tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server
resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the C
onnectionString)
f.. Does the server show up in the list of visible servers in Server Explore
r (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does i
t lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4
562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I jus
t
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in t
he
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Her
e
> is the problem, I can not connect to this box from Enterprise Manager from
my
> desktop. If I Remote Admin into the box everything works fine. If I try
to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log
in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted m
y
> authenication as trusted. SQL is using the standard TCP port 1433.
>
> Any ideas?
>
> Thanks,
>
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can pin
g
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
--
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and
the server ports must be visible outside of the box. Here are a few things
to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Con
fig tool)
> c.. On the client, is the firewall configured to permit access to the po
rts?
> d.. Are you trying to connect to the ports or are you letting the DNS se
rver resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see t
he ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Exp
lorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and do
es it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89
-488A-9AFB-B44A6B4562BC@.microsoft.com...|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
>
Friday, February 10, 2012
Connecting to SQL Server across VPN
I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is on
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
Thanks
Hi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
Thanks
Hi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
Connecting to SQL Server across VPN
I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is on
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
Thanks
Hi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
Thanks
Hi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
Connecting to SQL Server across VPN
I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is on
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
ThanksHi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
ThanksHi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
Connecting to SQL Server across VPN
I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is on
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
ThanksHi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
ThanksHi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
Subscribe to:
Posts (Atom)