Remotely Connect to Sql Server

Hi
i am trying to registering the remote sql server (MMC Sql EnterPrise
Manager) which is outside our Network . i.e the machine is located at ISP.
it is giving me error SQL server does not exist or access denied.
i am specifying the IP address of remote machine to whom i want to access
remotely,
(SQL Server Properties ) under connection tab - (configuration done to
remote sql server)
i had selected the option of allowing other sql server to connect remotely
to this sql server using RPC
even i am not able register remote sql server in my local sql server.
Can anyone help me out what exactly we have to do for remote access of sql
server.
Thanks
MiteshCan you ping the SQL server?
Can you telnet to port 1433 from your side ?
Is there a firewall in between ?
Make sure you can connect on port 1433 otherwise it will not work , you
would then need to check whats blocking that port somewhere!
HTH
Dylan
"Mitesh Patel" <mitesh@.viraat.com> wrote in message
news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi
> i am trying to registering the remote sql server (MMC Sql EnterPrise
> Manager) which is outside our Network . i.e the machine is located at ISP.
> it is giving me error SQL server does not exist or access denied.
> i am specifying the IP address of remote machine to whom i want to access
> remotely,
> (SQL Server Properties ) under connection tab - (configuration done to
> remote sql server)
> i had selected the option of allowing other sql server to connect remotely
> to this sql server using RPC
> even i am not able register remote sql server in my local sql server.
> Can anyone help me out what exactly we have to do for remote access of sql
> server.
> Thanks
> Mitesh
>
>|||when i ping to ip address it is showing destination host unreachable (this
is due to internet provider had stopped ping )
yes i am able to do telnet to port 1433 after passing the telnet command at
port 1433. the telnet window shows connecting... and then telnet screen
becomes blank (might it been connected and waiting for commands )
remote server is located in data center then firewall will be there
............
Thanks
Mitesh
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:uaq5Y8U0EHA.1396@.tk2msftngp13.phx.gbl...
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work , you
> would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
ISP.[vbcol=seagreen]
access[vbcol=seagreen]
remotely[vbcol=seagreen]
sql[vbcol=seagreen]
>|||You should also make sure that it's the public IP you try to access or you
have the proper NAT settings in the Firewall in both ends. It could also be
the settings for your VPN connection (if that's what your using ) that needs
to be checked.
Regards
Steen
Dylan Kruger wrote:[vbcol=seagreen]
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work ,
> you would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...sql

Remotely Connect to Sql Server

Hi
i am trying to registering the remote sql server (MMC Sql EnterPrise
Manager) which is outside our Network . i.e the machine is located at ISP.
it is giving me error SQL server does not exist or access denied.
i am specifying the IP address of remote machine to whom i want to access
remotely,
(SQL Server Properties ) under connection tab - (configuration done to
remote sql server)
i had selected the option of allowing other sql server to connect remotely
to this sql server using RPC
even i am not able register remote sql server in my local sql server.
Can anyone help me out what exactly we have to do for remote access of sql
server.
Thanks
Mitesh
Can you ping the SQL server?
Can you telnet to port 1433 from your side ?
Is there a firewall in between ?
Make sure you can connect on port 1433 otherwise it will not work , you
would then need to check whats blocking that port somewhere!
HTH
Dylan
"Mitesh Patel" <mitesh@.viraat.com> wrote in message
news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi
> i am trying to registering the remote sql server (MMC Sql EnterPrise
> Manager) which is outside our Network . i.e the machine is located at ISP.
> it is giving me error SQL server does not exist or access denied.
> i am specifying the IP address of remote machine to whom i want to access
> remotely,
> (SQL Server Properties ) under connection tab - (configuration done to
> remote sql server)
> i had selected the option of allowing other sql server to connect remotely
> to this sql server using RPC
> even i am not able register remote sql server in my local sql server.
> Can anyone help me out what exactly we have to do for remote access of sql
> server.
> Thanks
> Mitesh
>
>
|||when i ping to ip address it is showing destination host unreachable (this
is due to internet provider had stopped ping )
yes i am able to do telnet to port 1433 after passing the telnet command at
port 1433. the telnet window shows connecting... and then telnet screen
becomes blank (might it been connected and waiting for commands )
remote server is located in data center then firewall will be there
............
Thanks
Mitesh
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:uaq5Y8U0EHA.1396@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work , you
> would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
ISP.[vbcol=seagreen]
access[vbcol=seagreen]
remotely[vbcol=seagreen]
sql
>
|||You should also make sure that it's the public IP you try to access or you
have the proper NAT settings in the Firewall in both ends. It could also be
the settings for your VPN connection (if that's what your using ) that needs
to be checked.
Regards
Steen
Dylan Kruger wrote:[vbcol=seagreen]
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work ,
> you would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...

Remotely Connect to Sql Server

Hi
i am trying to registering the remote sql server (MMC Sql EnterPrise
Manager) which is outside our Network . i.e the machine is located at ISP.
it is giving me error SQL server does not exist or access denied.
i am specifying the IP address of remote machine to whom i want to access
remotely,
(SQL Server Properties ) under connection tab - (configuration done to
remote sql server)
i had selected the option of allowing other sql server to connect remotely
to this sql server using RPC
even i am not able register remote sql server in my local sql server.
Can anyone help me out what exactly we have to do for remote access of sql
server.
Thanks
MiteshCan you ping the SQL server?
Can you telnet to port 1433 from your side ?
Is there a firewall in between ?
Make sure you can connect on port 1433 otherwise it will not work , you
would then need to check whats blocking that port somewhere!
HTH
Dylan
"Mitesh Patel" <mitesh@.viraat.com> wrote in message
news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi
> i am trying to registering the remote sql server (MMC Sql EnterPrise
> Manager) which is outside our Network . i.e the machine is located at ISP.
> it is giving me error SQL server does not exist or access denied.
> i am specifying the IP address of remote machine to whom i want to access
> remotely,
> (SQL Server Properties ) under connection tab - (configuration done to
> remote sql server)
> i had selected the option of allowing other sql server to connect remotely
> to this sql server using RPC
> even i am not able register remote sql server in my local sql server.
> Can anyone help me out what exactly we have to do for remote access of sql
> server.
> Thanks
> Mitesh
>
>|||when i ping to ip address it is showing destination host unreachable (this
is due to internet provider had stopped ping )
yes i am able to do telnet to port 1433 after passing the telnet command at
port 1433. the telnet window shows connecting... and then telnet screen
becomes blank (might it been connected and waiting for commands )
remote server is located in data center then firewall will be there
............
Thanks
Mitesh
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:uaq5Y8U0EHA.1396@.tk2msftngp13.phx.gbl...
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work , you
> would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> > Hi
> >
> > i am trying to registering the remote sql server (MMC Sql EnterPrise
> > Manager) which is outside our Network . i.e the machine is located at
ISP.
> > it is giving me error SQL server does not exist or access denied.
> >
> > i am specifying the IP address of remote machine to whom i want to
access
> > remotely,
> >
> > (SQL Server Properties ) under connection tab - (configuration done to
> > remote sql server)
> > i had selected the option of allowing other sql server to connect
remotely
> > to this sql server using RPC
> >
> > even i am not able register remote sql server in my local sql server.
> >
> > Can anyone help me out what exactly we have to do for remote access of
sql
> > server.
> >
> > Thanks
> > Mitesh
> >
> >
> >
>|||You should also make sure that it's the public IP you try to access or you
have the proper NAT settings in the Firewall in both ends. It could also be
the settings for your VPN connection (if that's what your using ) that needs
to be checked.
Regards
Steen
Dylan Kruger wrote:
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work ,
> you would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
>> Hi
>> i am trying to registering the remote sql server (MMC Sql EnterPrise
>> Manager) which is outside our Network . i.e the machine is located
>> at ISP. it is giving me error SQL server does not exist or access
>> denied.
>> i am specifying the IP address of remote machine to whom i want to
>> access remotely,
>> (SQL Server Properties ) under connection tab - (configuration
>> done to remote sql server)
>> i had selected the option of allowing other sql server to connect
>> remotely to this sql server using RPC
>> even i am not able register remote sql server in my local sql
>> server.
>> Can anyone help me out what exactly we have to do for remote access
>> of sql server.
>> Thanks
>> Mitesh

remotely attached DB ends up readonly .. why oh why oh why ..

I have what seems like a commonish problem.
I have copied my database (mdf and logfile) to a remote XP desktop machine
... when using SQL server managment express tool when I try to attach the
DB it ends up readonly.
The file permissions are not set to read only (a problem I have read)
And I've done this shrink-detach-transfer-attach with various versions of
this database at least 20 times in the last week.
But not now it would seem.
The strange thing is that if I drop this database into the sql server default
'data' directory it works fine.
This doesnt explain why the second database that sits in the original 'destination'
directory attaches just fine.
I am utterly confused - traps for new players I guess.
---
[Sam Samson] - There is no greater folly than fixed price quoting.Sam
On the source machine, did you issue sp_detach the database? Take a look at
ALTER DATABASE... SET READ_WRITE option if I remember well
"Sam Samson" <nospamsam@.nospam.com.au> wrote in message
news:ece03a7894c38c9b916d29dee90@.news.microsoft.com...
>I have what seems like a commonish problem.
> I have copied my database (mdf and logfile) to a remote XP desktop machine
> ... when using SQL server managment express tool when I try to attach the
> DB it ends up readonly.
> The file permissions are not set to read only (a problem I have read) And
> I've done this shrink-detach-transfer-attach with various versions of this
> database at least 20 times in the last week.
> But not now it would seem.
> The strange thing is that if I drop this database into the sql server
> default 'data' directory it works fine.
> This doesnt explain why the second database that sits in the original
> 'destination' directory attaches just fine.
> I am utterly confused - traps for new players I guess.
> ---
> [Sam Samson] - There is no greater folly than fixed price quoting.
>
>

remote triggers on update

I don't think this is a problem, but I am curious as to why this is happening.

I have two machines, lets call them machine A and machine B.

On machine A I have a job that runs. It has 2 steps. The first step runs replication (no problem). The 2nd step (on success of step 1) updates a row in a table via a linked server on Machine B.

So, step 2 is basically:
update b.dbname.dbo.tablename set success=1 where id=1

On machine B, the table that is updated has an update trigger on it that checks the success flag. If the success flag is 1 then it runs a stored procedure that does a bunch of stuff on machine B (this stuff takes about 10 minutes).

This all works great, however if I check the job history on Machine A, it says that step 2 (the update) takes 10 minutes.

Why is this? Shouldn't the update statement be instantaneous? It seems like the update waits for the trigger to fire before returning. Is that correct?

Like I said, its not a problem, but I was just curious as to why the job on machine A waits for the trigger on machine B to complete.

Hope this makes sense. Thanks

JeffThe trigger is part of the update, and the transaction is not complete until the trigger completes.

blindman

Remote stored procedure

I am trying to run a stored procedure on a remote server and insert the
output into a table on the local machine.
The two servers are linked and I am using the code as follows
BEGIN DISTRIBUTED TRAN
insert into ServerA.Database.dbo.drv_total
exec ServerB.master.dbo.xp_fixeddrives
COMMIT TRAN
The MSDTC is started on both machines.
I am getting this error:
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
Any thoughts?
TIA,
nivek
Hi Nivek,
Are you running on Windows 2003? If so, the following link may apply to you:
http://support.microsoft.com/default...b;en-us;329332
"The problem occurs because Microsoft Distributed Transaction Coordinator
(MS DTC) is not configured for network access. By default, the network access
settings of MS DTC are disabled on new installations of SQL Server 2000 on
computers running Windows Server 2003, Enterprise Edition. "
Best Regards,
Joe Sack
Author of "SQL Server 2000 Fast Answers..."
http://www.JoeSack.com
"nivek" wrote:

> I am trying to run a stored procedure on a remote server and insert the
> output into a table on the local machine.
> The two servers are linked and I am using the code as follows
> BEGIN DISTRIBUTED TRAN
> insert into ServerA.Database.dbo.drv_total
> exec ServerB.master.dbo.xp_fixeddrives
> COMMIT TRAN
> The MSDTC is started on both machines.
> I am getting this error:
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider 'SQLOLEDB'
> was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
>
> Any thoughts?
>
> TIA,
> nivek
>
>
sql

Remote stored procedure

I am trying to run a stored procedure on a remote server and insert the
output into a table on the local machine.
The two servers are linked and I am using the code as follows
BEGIN DISTRIBUTED TRAN
insert into ServerA.Database.dbo.drv_total
exec ServerB.master.dbo.xp_fixeddrives
COMMIT TRAN
The MSDTC is started on both machines.
I am getting this error:
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
Any thoughts?
TIA,
nivekHi Nivek,
Are you running on Windows 2003? If so, the following link may apply to you:
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332
"The problem occurs because Microsoft Distributed Transaction Coordinator
(MS DTC) is not configured for network access. By default, the network access
settings of MS DTC are disabled on new installations of SQL Server 2000 on
computers running Windows Server 2003, Enterprise Edition. "
Best Regards,
Joe Sack
Author of "SQL Server 2000 Fast Answers..."
http://www.JoeSack.com
"nivek" wrote:
> I am trying to run a stored procedure on a remote server and insert the
> output into a table on the local machine.
> The two servers are linked and I am using the code as follows
> BEGIN DISTRIBUTED TRAN
> insert into ServerA.Database.dbo.drv_total
> exec ServerB.master.dbo.xp_fixeddrives
> COMMIT TRAN
> The MSDTC is started on both machines.
> I am getting this error:
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider 'SQLOLEDB'
> was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
>
> Any thoughts?
>
> TIA,
> nivek
>
>

Remote Server Login

As a Sys Admin, I was wondering - if I have admin rights to a Win2k machine
that is hosting SQL Server 2000, do I have the ability using any
command-line tools such as OSQL or ISQL (that can be accessed remotely) to
add, delete, or change accounts
registered in SQL Server for the various databases if I don't have access to
a specific account within SQL Server?
I ask, because the question that came up was - what if we have a DBA leave
under less than amicable circumstances? Could I, someone who has admin
rights on the machine, be able to log into that machine remotely and somehow
via command line (I don't maintain active SQL clients centrally), change the
SA password, remove an account, and/or add an account with sysadmin rights,
etc?
Thanks in advance for any help -IF that person continues to have a valid login to SQL Server with
administrative priveleges, then he can do anything via OSQL he can do via
Query Analyzer or SQL Enterprise Manager..
So when someone leaves, we delete their login ( in SQL and/or Windows )
immediately and they can do us no harm..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"ScottT" <jbell@.vitria.com> wrote in message
news:10ddv86i6ng5e47@.news.supernews.com...
> As a Sys Admin, I was wondering - if I have admin rights to a Win2k
machine
> that is hosting SQL Server 2000, do I have the ability using any
> command-line tools such as OSQL or ISQL (that can be accessed remotely) to
> add, delete, or change accounts
> registered in SQL Server for the various databases if I don't have access
to
> a specific account within SQL Server?
> I ask, because the question that came up was - what if we have a DBA leave
> under less than amicable circumstances? Could I, someone who has admin
> rights on the machine, be able to log into that machine remotely and
somehow
> via command line (I don't maintain active SQL clients centrally), change
the
> SA password, remove an account, and/or add an account with sysadmin
rights,
> etc?
> Thanks in advance for any help -
>

Remote instance not listed in Available Servers in Enterprise Manager

When using the register available servers in Enterprise Manager, the
named instances on a remote machine are not listed. The unnamed
instance is listed and will register successfully.
I have tried manually typing the names of the remote NAMED instances;
then tried to authenticate and get the message "SQL server does not
exist or access denied".
Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
2 Instances
Unnamed
DEV\DB1
On the remote machine SQL Server 2000 (MSDE Edition) installed
3 Instances;
Unnamed
REM\DB1
REM\DB2
Both machines are on the same domain. All SQL server instances are
running.
I have also used the svrnetcn.exe tool to make sure the Named Pipes
and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
been changed to 1433 on all remote instances. (both machines were
rebooted)
What else can I check ?
Thanks
D> I have also used the svrnetcn.exe tool to make sure the Named Pipes
> and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
> been changed to 1433 on all remote instances. (both machines were
> rebooted)
Each instance on a machine must listen on a unique TCP port. Consequently,
all of the instances on your REM machine can't be listening on the same 1433
port. Check the errorlog file for those instances for related TCP port
binding errors and change the named instance ports, if needed.
The normal configuration is that the default (unnamed) instance listens on
1433 and named instance ports are determined dynamically. When a client
connects to a named instance, it firsts gets a list of running named
instances via a UDP 1434 request and then connects to the TCP port of the
specified instance. Make sure your firewall allows TCP 1433, UDP 1434 and
TCP traffic on the named instance ports. See
http://support.microsoft.com/kb/287932
--
Hope this helps.
Dan Guzman
SQL Server MVP
"DM" <dmcb73@.gmail.com> wrote in message
news:1190197075.363594.146870@.22g2000hsm.googlegroups.com...
> When using the register available servers in Enterprise Manager, the
> named instances on a remote machine are not listed. The unnamed
> instance is listed and will register successfully.
> I have tried manually typing the names of the remote NAMED instances;
> then tried to authenticate and get the message "SQL server does not
> exist or access denied".
> Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
> 2 Instances
> Unnamed
> DEV\DB1
> On the remote machine SQL Server 2000 (MSDE Edition) installed
> 3 Instances;
> Unnamed
> REM\DB1
> REM\DB2
> Both machines are on the same domain. All SQL server instances are
> running.
> I have also used the svrnetcn.exe tool to make sure the Named Pipes
> and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
> been changed to 1433 on all remote instances. (both machines were
> rebooted)
> What else can I check ?
> Thanks
> D
>

remote errors

How do you get remote errors to show on a different machine? We want to see
what errors our dev machine is throwing when it does so we dont have to go
through logs to try to find it.. I tried changing the customerrors to Off in
web.config but didnt seem to fix the problem, what am I missing? thanks!nevermind! didnt realize it was a system property I had to set! got it
working now
"Smokey Grindel" <nospam@.nospam.com> wrote in message
news:eKRdUnOYHHA.984@.TK2MSFTNGP04.phx.gbl...
> How do you get remote errors to show on a different machine? We want to
> see what errors our dev machine is throwing when it does so we dont have
> to go through logs to try to find it.. I tried changing the customerrors
> to Off in web.config but didnt seem to fix the problem, what am I missing?
> thanks!
>

Remote Distributor and Subscriber on same machine - is that OK?

Hi,

Server A houses the Production DB which services an OLTP system. Transactional replication is configured on this server which has two subscribers - on two separate servers (servers B and C). The Distribution database currently resides on Server A (which is also the Publisher).

Server B is on the same LAN as Server A (on the same rack). I'm considering moving the Distribution database from Server A to Server B to offload some of the processing overhead from Server A.

Are there any gotchas/performance problems associated with having the Distribution database (remote distributor) and the Subscriber on the same server (server B) in a transaction replication topology?

Please advise or point me to the appropriate documentation - I haven't found anything that addresses this specific question...thanks in advance,

Smitha

This is actually a rather popular configuration (at least the ones that I have seen) inside Microsoft as this allows you to upgrade the Distributor and Subscriber to a new release together and then use the Subscriber as a test bed for the new release while receiving continuous updates from the production system. You do need good network connectivity between the publisher and the distributor\subscriber as pulling snapshot data (or backup\restore for that matter) can easily saturate a 100Mbit Ethernet connection. So to minimize impact on the production system, you may want to get a dedicated connection between the two.

-Raymond

|||

Thanks Raymond. I shouldn't have to worry about the snapshot/backup+restore because I've used this second server as the backup files' location in the past (and still perform copy-only FULL production DB backups to this server). The restore takes a while since it reads from and writes to the same drive but this is OK for an operation that may happen 2-3 times a year.

Thanks again,

Smitha

Remote Deployment

What's the easiest way to deploy a project to a remote server? Keep in mind there won't be any machine level access to the server housing the sql server.

Your question is bit short.
If you are talking about deployment of Analysis Services project you have several ways.

1. Change your BI Dev project properties to tell it to deploy to remote machine.

2. Use Deployment utility.

3. deploy your project first to the local Analysis Server and then use Synchronization or Backup/Restore to move data and metadata to a remote server.

I am sure you can be quite creative and find other ways to deploy your solution.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Remote database access

Hi can anybody know how to connect remote database with asp.net application? Actually my database is in different machine (in different server, different location) so i want to connect that server. Every time I'm getting the fallowing message

An error has occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

Thank you,

Nagu

Hi,

Please check the article athttp://www.kodyaz.com/content/SQLServerdoesnotallowremoteconnections.aspx about this default security configuration and altering this setting

You can use the Surface Area Configuration tool in order to let remote connections.

Eralper

|||

Hi nagsline ,

First of all enable mixed mode authentication for accessing the database. If you are using an sql username and password make sure that user have access to your database.

|||Also make sure your connection string is correct ie. you have mentioned the correct system name or Ip address etc.|||I don't know if this helps but I thought I would point out that you receive this exact error also when your SQL server is stopped and you try connecting to it.

Remote connections to named instances fails on SQL 2005 cluster

I have a new SQL Server 2005 cluster with multiple named instances of SQL
Server 2005 running. From any cluster machine, I can connect to any instanc
e
of SQL Server running in the cluster. From remote machines, I can connect t
o
the default instance of SQL Server, but I can not connect to any named
instances. Help?
+ SQL Browser is running on one physical machine in the cluster
+ Surface Area Configuration has "remote clients" enabled for all instances
+ Named pipes and TCP/IP are enabled
+ DTC is running on the cluster. It is configured to allow network access
on each physical machine.
+ Windows firewall is disabled. Remote machines on same subnet as cluster
machines.
+ Client machine can ping virtual servers?
After waiting a few hours, remote connections now work
?
"Bill Q" wrote:

> I have a new SQL Server 2005 cluster with multiple named instances of SQL
> Server 2005 running. From any cluster machine, I can connect to any insta
nce
> of SQL Server running in the cluster. From remote machines, I can connect
to
> the default instance of SQL Server, but I can not connect to any named
> instances. Help?
> + SQL Browser is running on one physical machine in the cluster
> + Surface Area Configuration has "remote clients" enabled for all instance
s
> + Named pipes and TCP/IP are enabled
> + DTC is running on the cluster. It is configured to allow network access
> on each physical machine.
> + Windows firewall is disabled. Remote machines on same subnet as cluster
> machines.
> + Client machine can ping virtual servers

Remote connection to SQL Server 2005

I am unable to connect to a SQL Server 2005 instance running remotely
on a Windows 2003 Server machine behind a router. I can connect to the
instance via SQL Server Management Studio Express when I place the
server machine in the DMZ, but I cannot connect when I forward traffic
on port 1433. Note that I am able to forward Remote Desktop requests to
my server, so I know that port forwarding works in other cases.
Any suggestions? I'd rather not leave my server machine in the DMZ.
Thanks for the help.Only the default (un-named) instance listens on port 1433. If you have a
named instance or are running SQL Express, which is a named instance named
(SQLEXPRESS) you are listening on dynamic ports.
For more ideas, run through my short connectivity tutorial at
http://msdn2.microsoft.com/en-us/library/ms345318(SQL.90).aspx
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
<bostonguy@.gmail.com> wrote in message
news:1147702273.174968.231850@.i40g2000cwc.googlegroups.com...
>I am unable to connect to a SQL Server 2005 instance running remotely
> on a Windows 2003 Server machine behind a router. I can connect to the
> instance via SQL Server Management Studio Express when I place the
> server machine in the DMZ, but I cannot connect when I forward traffic
> on port 1433. Note that I am able to forward Remote Desktop requests to
> my server, so I know that port forwarding works in other cases.
> Any suggestions? I'd rather not leave my server machine in the DMZ.
> Thanks for the help.
>|||Is it recommended to use something other than port 1433 when
configuring a static port for a named instance like (SQLEXPRESS)?
Thanks,
John
Rick Byham [MS] wrote:[vbcol=seagreen]
> Only the default (un-named) instance listens on port 1433. If you have a
> named instance or are running SQL Express, which is a named instance named
> (SQLEXPRESS) you are listening on dynamic ports.
> For more ideas, run through my short connectivity tutorial at
> http://msdn2.microsoft.com/en-us/library/ms345318(SQL.90).aspx
> --
> Rick Byham
> MCDBA, MCSE, MCSA
> Documentation Manager,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> <bostonguy@.gmail.com> wrote in message
> news:1147702273.174968.231850@.i40g2000cwc.googlegroups.com...|||There is no particular reason to use a different port number. Some people
use different numbers in case there is another SQL Server installed on the
system. Some people like to make it harder for viruses or hackers that are
targeting port 1433, but using a different port doesn't confuse them that
much.
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"John" <john@.destinytours.com> wrote in message
news:1147905901.881404.59600@.j55g2000cwa.googlegroups.com...
> Is it recommended to use something other than port 1433 when
> configuring a static port for a named instance like (SQLEXPRESS)?
> Thanks,
> John
> Rick Byham [MS] wrote:
>|||Yes, I experienced this first hand when I discovered someone from
Amsterdam trying to hack into my server with repeated login attemps
(trying every few seconds).
Rick Byham [MS] wrote:[vbcol=seagreen]
> There is no particular reason to use a different port number. Some people
> use different numbers in case there is another SQL Server installed on the
> system. Some people like to make it harder for viruses or hackers that are
> targeting port 1433, but using a different port doesn't confuse them that
> much.
> --
> Rick Byham
> MCDBA, MCSE, MCSA
> Documentation Manager,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> "John" <john@.destinytours.com> wrote in message
> news:1147905901.881404.59600@.j55g2000cwa.googlegroups.com...

Remote connection to MSDE

I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist or access denied.
Any ideas?
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
|||Ok, here's what i've discovered:
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?
|||Did you restart after enabling TCP/IP? Is it a default
instance or a named instance? Can you connect locally when
on the machine with MSDE?
-Sue
On 25 Jan 2006 14:21:43 -0800, "laurin1" <laurin1@.osai.com>
wrote:

>I just did an netstat -an and I don't see the server listening on 1433.
>What am I not doing?
|||Yes. It's a named instance (SHAREPOINT). I can connect locally.
|||Make sure you aren't having firewall issues.
Can you ping the MSDE box from the other box?
Check the listening port for the MSDE instance - when you
start up MSDE, it logs what protocols, ports it is listening
on in the error log.
Try to telnet to the port it's listening on.
Verify the login being used.
And if those don't get you anywhere, you can find additional
troubleshooting steps in the following article:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On 26 Jan 2006 05:41:03 -0800, "laurin1" <laurin1@.osai.com>
wrote:

>Yes. It's a named instance (SHAREPOINT). I can connect locally.
|||I just found out that this is WMSDE, not MSDE, which can only be
connected to remotely. No matter what changes I make, the server will
not listen on 1433.
|||If it is indeed WMSDE, it only supports local connections so it will never
listen on a port. WMSDE is an OS component that can only be connected to by
selected Microsoft software running locally.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"laurin1" <laurin1@.osai.com> wrote in message
news:1138379664.059706.236830@.g14g2000cwa.googlegr oups.com...
>I just found out that this is WMSDE, not MSDE, which can only be
> connected to remotely. No matter what changes I make, the server will
> not listen on 1433.
>

Remote connection to MSDE

I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpe
n
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server do
es not
exist or access denied.
Any ideas?I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?|||Ok, here's what i've discovered:
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?|||Did you restart after enabling TCP/IP? Is it a default
instance or a named instance? Can you connect locally when
on the machine with MSDE?
-Sue
On 25 Jan 2006 14:21:43 -0800, "laurin1" <laurin1@.osai.com>
wrote:

>I just did an netstat -an and I don't see the server listening on 1433.
>What am I not doing?|||Yes. It's a named instance (SHAREPOINT). I can connect locally.|||Make sure you aren't having firewall issues.
Can you ping the MSDE box from the other box?
Check the listening port for the MSDE instance - when you
start up MSDE, it logs what protocols, ports it is listening
on in the error log.
Try to telnet to the port it's listening on.
Verify the login being used.
And if those don't get you anywhere, you can find additional
troubleshooting steps in the following article:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On 26 Jan 2006 05:41:03 -0800, "laurin1" <laurin1@.osai.com>
wrote:

>Yes. It's a named instance (SHAREPOINT). I can connect locally.|||I just found out that this is WMSDE, not MSDE, which can only be
connected to remotely. No matter what changes I make, the server will
not listen on 1433.|||If it is indeed WMSDE, it only supports local connections so it will never
listen on a port. WMSDE is an OS component that can only be connected to by
selected Microsoft software running locally.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"laurin1" <laurin1@.osai.com> wrote in message
news:1138379664.059706.236830@.g14g2000cwa.googlegroups.com...
>I just found out that this is WMSDE, not MSDE, which can only be
> connected to remotely. No matter what changes I make, the server will
> not listen on 1433.
>|||somebody on this forum "sameer" gave me a clue that
1433 is not listened on due to the "slammer" virus requiring SP1 for SQL
Server 2005...I am just begiing on this so what do I know
"Roger Wolter[MSFT]" wrote:

> If it is indeed WMSDE, it only supports local connections so it will never
> listen on a port. WMSDE is an OS component that can only be connected to
by
> selected Microsoft software running locally.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "laurin1" <laurin1@.osai.com> wrote in message
> news:1138379664.059706.236830@.g14g2000cwa.googlegroups.com...
>
>