Re: Problem accessing remote sql server

Tech-Archive recommends: Fix windows errors by optimizing your registry

Port 135 is RPC and not TCP Pipe. Use the default on the TCP pipe with
SQLServer. I don't have a box in front of me to give you the exact wording
but it is very straight forward and 1433 is the default.
When you create a new SystemDNS you have 2 tabs (Data Source and TCPIP).
Under the data source you enter the connection name (something that make
sense to you), the userID and the password.
Under the TCP/IP tab you enter the database name, alias, hostIP and port
number.

--
Claus
"John" <John@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:u3Lq3g8AIHA.4880@xxxxxxxxxxxxxxxxxxxxxxx
I get below. 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)

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:%23mjx9S8AIHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
Admin/ODBC Connections, select new System DSN with TCP Pipe (follow the
Wizard).

--
Claus
"John" <John@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uTi9gr7AIHA.5328@xxxxxxxxxxxxxxxxxxxxxxx
sorry no ideas how to do it.

Thanks

Regards

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:OSr1Jp7AIHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
Have you tried if you get through with a System DSN connection?

--
Claus
"John" <John@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eULVwd7AIHA.748@xxxxxxxxxxxxxxxxxxxxxxx
Don't know as it is remote but I assume its 2005.

I have just noticed that doing telnet <remote sql ip> 1433, 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.

Regards

"bass_player [SBS-MVP]" <bass_player@xxxxxxxx> wrote in message
news:uqqxh86AIHA.288@xxxxxxxxxxxxxxxxxxxxxxx
I can't help but asking, is this a SQL Server 2000 or 2005?

"John" <livingusman@xxxxxxxxxxxxxx> wrote in message
news:1191178656.948293.234510@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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















.

Relevant Pages

  • Re: Problem accessing remote sql server
    ... The studio works because it uses that DSN you created. ... Under the TCP/IP tab you enter the database name, alias, hostIP and port ... which obviously fails as remote sql server is on port 1433. ... I have just noticed that doing telnet <remote sql ip> 1433, ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem accessing remote sql server
    ... I have just noticed that doing telnet <remote sql ip> 1433, the isa log ... sql server management studio express to connect, isa log does not log any ... attempt on port 1433. ...
    (microsoft.public.windows.server.sbs)
  • ISA and SQL2000
    ... My company developed software years ago that required port 1433 ... to be open to the Internet. ... this doesnt stop the direct pipe into the SQL server on port ... I would like to place an ISA server in a DMZ (or perimeter in front of ...
    (microsoft.public.isa)
  • Re: ODBC failing to connect
    ... Well looking at the Firewall logs I can see the it is opening the port then ... First off I went into the SQL Server logs and found out that it is ... Back to the ISA machine, and opened up telnet and tried to connect to SQL ... You'd also want to check your ports and protocols - one way ...
    (microsoft.public.sqlserver.connect)
  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)