By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,241 Members | 799 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,241 IT Pros & Developers. It's quick & easy.

Problem accessing remote sql server

P: n/a
Hi

We had an sbs 2003 with isa 2000 server. We wre able to access a
remote sql server (hosted at our web host) just fine. We replaced the
server with a new sbs 2003 r2 with isa 2004 server and even though I
have opened port 1433 in isa 2004 we can't access the remote sql
server anymore. Where can I look for any blocks?

Many Thanks

Regards

Sep 30 '07 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Is the SQL Server installed as a default or a named instance?

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"John" <li*********@googlemail.comwrote in message
news:11**********************@w3g2000hsg.googlegro ups.com...
Hi

We had an sbs 2003 with isa 2000 server. We wre able to access a
remote sql server (hosted at our web host) just fine. We replaced the
server with a new sbs 2003 r2 with isa 2004 server and even though I
have opened port 1433 in isa 2004 we can't access the remote sql
server anymore. Where can I look for any blocks?

Many Thanks

Regards
Sep 30 '07 #2

P: n/a
Hi

I don't know as it is remotely located. I received ip and username/
password from host which worked fine on old sbs 2000 + isa 2000 server
but not on new sbs 2003 r2 + isa 2004. Anyway I can check?

Thanks

Regards

On 30 Sep, 20:50, "Tibor Karaszi"
<tibor_please.no.email_kara...@hotmail.nomail.comw rote:
Is the SQL Server installed as a default or a named instance?

--
Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi

"John" <livingus...@googlemail.comwrote in message

news:11**********************@w3g2000hsg.googlegro ups.com...
Hi
We had an sbs 2003 with isa 2000 server. We wre able to access a
remote sql server (hosted at our web host) just fine. We replaced the
server with a new sbs 2003 r2 with isa 2004 server and even though I
have opened port 1433 in isa 2004 we can't access the remote sql
server anymore. Where can I look for any blocks?
Many Thanks
Regards- Hide quoted text -

- Show quoted text -

Sep 30 '07 #3

P: n/a
John (li*********@googlemail.com) writes:
I don't know as it is remotely located. I received ip and username/
password from host which worked fine on old sbs 2000 + isa 2000 server
but not on new sbs 2003 r2 + isa 2004. Anyway I can check?
A named instance has a name like SERVER\INSTANCE. To be able to access
a named instance you need to have its port number open. And if you also
access it one the form SERVER\INSTANCE, you need access to UDP port
1434. (You can always access it as SERVER,portnum.)

May be you should ask in a forum about ISA Server (which I'm completely
ignorant of)?

You should check with you host on which port SQL Server is listening.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Sep 30 '07 #4

P: n/a
This was also posted on the microsoft.public.windows.server.sbs newsgroup

I did ask if this was SQL Server 2000 or 2005 as you mentioned Windows SBS
2003 R2. You have to enable remote access using the Surface Area
Configuration for Services and Connections

"Erland Sommarskog" <es****@sommarskog.sewrote in message
news:Xn*********************@127.0.0.1...
John (li*********@googlemail.com) writes:
>I don't know as it is remotely located. I received ip and username/
password from host which worked fine on old sbs 2000 + isa 2000 server
but not on new sbs 2003 r2 + isa 2004. Anyway I can check?

A named instance has a name like SERVER\INSTANCE. To be able to access
a named instance you need to have its port number open. And if you also
access it one the form SERVER\INSTANCE, you need access to UDP port
1434. (You can always access it as SERVER,portnum.)

May be you should ask in a forum about ISA Server (which I'm completely
ignorant of)?

You should check with you host on which port SQL Server is listening.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Sep 30 '07 #5

P: n/a
I am using the remote servers ip address, as provided by the host, instead
of server name.

Doing telnet <remote sql ip1433, the isa log registers access on port 1433
but accessing the remote sql server using sql server management studio
express to connect, isa log does not log any attempt on port 1433. I can't
figure out why the management studio is not connecting on port 1433 or how
to make it do it.

Thanks

Regards

"Erland Sommarskog" <es****@sommarskog.sewrote in message
news:Xn*********************@127.0.0.1...
John (li*********@googlemail.com) writes:
>I don't know as it is remotely located. I received ip and username/
password from host which worked fine on old sbs 2000 + isa 2000 server
but not on new sbs 2003 r2 + isa 2004. Anyway I can check?

A named instance has a name like SERVER\INSTANCE. To be able to access
a named instance you need to have its port number open. And if you also
access it one the form SERVER\INSTANCE, you need access to UDP port
1434. (You can always access it as SERVER,portnum.)

May be you should ask in a forum about ISA Server (which I'm completely
ignorant of)?

You should check with you host on which port SQL Server is listening.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Sep 30 '07 #6

P: n/a
When I try to connect to remote sql server by creating a System DSN I get
below in ISA 2004 logging. Apparently for some reason System DSN is trying
to connect on port 135 which obviously fails as remote sql server is on port
1433. How can I make System DSN to try port 1433?

Thanks

Regards

Failed Connection Attempt ...
Log type: Firewall service
Status: A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection failed
because connected host has failed to respond.
Rule: External SQL Server
Source: Local Host ( <local server external ip>:13421)
Destination: External ( <remote sql ip>:135)
Protocol: RPC (all interfaces)
"John" <li*********@googlemail.comwrote in message
news:11**********************@w3g2000hsg.googlegro ups.com...
Hi

We had an sbs 2003 with isa 2000 server. We wre able to access a
remote sql server (hosted at our web host) just fine. We replaced the
server with a new sbs 2003 r2 with isa 2004 server and even though I
have opened port 1433 in isa 2004 we can't access the remote sql
server anymore. Where can I look for any blocks?

Many Thanks

Regards

Oct 1 '07 #7

P: n/a
Have you tried running SQL Profiler to check whether or not any application
can connect to SQL Server?
"John" <Jo**@nospam.infovis.co.ukwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
>I am using the remote servers ip address, as provided by the host, instead
of server name.

Doing telnet <remote sql ip1433, the isa log registers access on port
1433 but accessing the remote sql server using sql server management
studio express to connect, isa log does not log any attempt on port 1433.
I can't figure out why the management studio is not connecting on port
1433 or how to make it do it.

Thanks

Regards

"Erland Sommarskog" <es****@sommarskog.sewrote in message
news:Xn*********************@127.0.0.1...
>John (li*********@googlemail.com) writes:
>>I don't know as it is remotely located. I received ip and username/
password from host which worked fine on old sbs 2000 + isa 2000 server
but not on new sbs 2003 r2 + isa 2004. Anyway I can check?

A named instance has a name like SERVER\INSTANCE. To be able to access
a named instance you need to have its port number open. And if you also
access it one the form SERVER\INSTANCE, you need access to UDP port
1434. (You can always access it as SERVER,portnum.)

May be you should ask in a forum about ISA Server (which I'm completely
ignorant of)?

You should check with you host on which port SQL Server is listening.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx


Oct 1 '07 #8

P: n/a
John (Jo**@nospam.infovis.co.uk) writes:
Doing telnet <remote sql ip1433, the isa log registers access on port
1433 but accessing the remote sql server using sql server management
studio express to connect, isa log does not log any attempt on port
1433. I can't figure out why the management studio is not connecting on
port 1433 or how to make it do it.
Check in SQL Configuration Manager that you have TCP/IP enabled as a client
protocol. It may be trying named pipes only.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Oct 1 '07 #9

This discussion thread is closed

Replies have been disabled for this discussion.