asp sql server: shared

Showing posts with label shared. Show all posts

Wednesday, March 7, 2012

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

Sunday, February 12, 2012

Connecting to SQL Server using non domain account

How can I connect to SQL Server 2005 without having a domain account and thr
ough a MS Access front end that is on the main server
and shared between 20 different users? Some of the users have domain account
s and they can use the database, but those that do not
have domain accounts cannot connect. Is there a way to get this working?
Cheers,
Max.Do you have a database administrator for the SQL Server? Someone will
need to create SQL logins and grant permissions in the database.
--Mary
On Thu, 11 Jan 2007 15:14:36 -0500, "Max" <maxy_100@.yahoo.com> wrote:

>How can I connect to SQL Server 2005 without having a domain account and th
rough a MS Access front end that is on the main server
>and shared between 20 different users? Some of the users have domain accoun
ts and they can use the database, but those that do not
>have domain accounts cannot connect. Is there a way to get this working?
>Cheers,
>Max.

Connecting to SQL Server using non domain account

How can I connect to SQL Server 2005 without having a domain account and through a MS Access front end that is on the main server
and shared between 20 different users? Some of the users have domain accounts and they can use the database, but those that do not
have domain accounts cannot connect. Is there a way to get this working?
Cheers,
Max.Do you have a database administrator for the SQL Server? Someone will
need to create SQL logins and grant permissions in the database.
--Mary
On Thu, 11 Jan 2007 15:14:36 -0500, "Max" <maxy_100@.yahoo.com> wrote:
>How can I connect to SQL Server 2005 without having a domain account and through a MS Access front end that is on the main server
>and shared between 20 different users? Some of the users have domain accounts and they can use the database, but those that do not
>have domain accounts cannot connect. Is there a way to get this working?
>Cheers,
>Max.

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
>

Wednesday, March 7, 2012

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Sunday, February 12, 2012

Connecting to SQL Server using non domain account

Connecting to SQL Server using non domain account

Friday, February 10, 2012

Connecting to SQL Server across VPN

Connecting to SQL Server across VPN

asp sql server

Blog Archive

About Me