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

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" <livingusman@googlemail.com> wrote in message
news:1191178805.326969.194010@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
>

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.co m> wrote:
> 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.com> wrote in message
>
> news:1191178805.326969.194010@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 -

John (livingusman@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, esquel@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

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" <esquel@sommarskog.se> wrote in message
news:Xns99BC1E65262FYazorman@127.0.0.1...
> John (livingusman@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, esquel@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

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" <livingusman@googlemail.com> wrote in message
news:1191178805.326969.194010@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
>