Connection problems (SQL 2000)

Hope you help me....
Two SBS 2000's (trying to get the damn think to replicate).
BROAD has fixed IP of 81.174.xxx.xxx and CLIFT has 81.174.xxx.xxx
Broad is set as the subscriber, Clift as the distributor
Broad can ping, tracert Clift using IP and Name
ISA firewall ports open to allow traffic in/out of both servers
SQL Protocol mapped to 14446 instead of 1433.
Win XP workstation can connect via ODBC to Clift SQL Database no problems
using user sa.
BROAD cannot make connection to CLIFT via ODBC (server not found).
BROAD cannot connect to CLIFT via Client network tool or SQL Analyser?
BROAD and CLIFT router's completely open, no restrictions (for testing only)
So why can I connect using my XP workstation and not the other server?.
The CLIFT server must be OK for access because I can access the database
remotely and open it.
I cannot see any reason why i am having problems with this...
Ideas.
Many thanks
Ok, so let me get this straight. There are three machines, Broad, Clift and
your workstation.
Broad can ping clift. Your workstation can ping clift (and connect). Broad
cannot connect to clift using ODBC.
Ping means you have network connectivity. I take it you did a ping -a
81.174.xxx.xxx and ping -a clift to ensure that it is resolving to the
correct ip address. Now I think you should use ODBC ping to try to connect
to it. Also use client network utility to set up an alias to clift on broad
using the ip address and instance name, and then try again.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
""confused"" <confused@.discussions.microsoft.com> wrote in message
news:130033D1-DA47-48E6-A984-37080D4FFEBB@.microsoft.com...
> Hope you help me....
> Two SBS 2000's (trying to get the damn think to replicate).
> BROAD has fixed IP of 81.174.xxx.xxx and CLIFT has 81.174.xxx.xxx
> Broad is set as the subscriber, Clift as the distributor
> Broad can ping, tracert Clift using IP and Name
> ISA firewall ports open to allow traffic in/out of both servers
> SQL Protocol mapped to 14446 instead of 1433.
> Win XP workstation can connect via ODBC to Clift SQL Database no problems
> using user sa.
> BROAD cannot make connection to CLIFT via ODBC (server not found).
> BROAD cannot connect to CLIFT via Client network tool or SQL Analyser?
> BROAD and CLIFT router's completely open, no restrictions (for testing
> only)
> So why can I connect using my XP workstation and not the other server?.
> The CLIFT server must be OK for access because I can access the database
> remotely and open it.
> I cannot see any reason why i am having problems with this...
> Ideas.
> Many thanks
|||Hi Hilary,
odbcping works fine from an XP workstation to each server but NOT from
server to server. I can ping between servers and tracert but nothing else.
Have tried setting up alias on each server but odbcping still wont work from
server to server. Now is there any ports that need to be opened on the server
for odbcping to work? I really dont get it....
Thanks
"Hilary Cotter" wrote:

> Ok, so let me get this straight. There are three machines, Broad, Clift and
> your workstation.
> Broad can ping clift. Your workstation can ping clift (and connect). Broad
> cannot connect to clift using ODBC.
> Ping means you have network connectivity. I take it you did a ping -a
> 81.174.xxx.xxx and ping -a clift to ensure that it is resolving to the
> correct ip address. Now I think you should use ODBC ping to try to connect
> to it. Also use client network utility to set up an alias to clift on broad
> using the ip address and instance name, and then try again.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> ""confused"" <confused@.discussions.microsoft.com> wrote in message
> news:130033D1-DA47-48E6-A984-37080D4FFEBB@.microsoft.com...
>
>
|||Yes, you need to open whatever port SQL Server is running on for inbound
communication. So if it is running on 1433 you need to open up port 1433 for
inbound communication.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
""confused"" <confused@.discussions.microsoft.com> wrote in message
news:5524C527-EB97-4423-BA34-6BF5E4F1B199@.microsoft.com...[vbcol=seagreen]
> Hi Hilary,
> odbcping works fine from an XP workstation to each server but NOT from
> server to server. I can ping between servers and tracert but nothing else.
> Have tried setting up alias on each server but odbcping still wont work
> from
> server to server. Now is there any ports that need to be opened on the
> server
> for odbcping to work? I really dont get it....
>
> Thanks
> "Hilary Cotter" wrote:
|||Hi,
I am using 14446 instead of 1433.
I have created packet filters (both ways with fixed IP) on both servers
I have created Protocol rules based upon that Port so there really isnt
anything stopping the comms from working.
However, I looked inside the ISA log (Firewall) and it states that port
14446 from IP 81.174.xxx.xxx is BLOCKED for some reason but I cant find
anything in the ISA console that does block it.
So as far as I can see, ISA is blocking the comms. The 14446 port is OPEN so
I really dont understand.
TIM
"Hilary Cotter" wrote:

> Yes, you need to open whatever port SQL Server is running on for inbound
> communication. So if it is running on 1433 you need to open up port 1433 for
> inbound communication.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> ""confused"" <confused@.discussions.microsoft.com> wrote in message
> news:5524C527-EB97-4423-BA34-6BF5E4F1B199@.microsoft.com...
>
>
|||I think you need a networking specialist to help resolve this.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
""confused"" <confused@.discussions.microsoft.com> wrote in message
news:8B1A0BDE-375C-44EA-A6A2-B31462D028EF@.microsoft.com...[vbcol=seagreen]
> Hi,
> I am using 14446 instead of 1433.
> I have created packet filters (both ways with fixed IP) on both servers
> I have created Protocol rules based upon that Port so there really isnt
> anything stopping the comms from working.
> However, I looked inside the ISA log (Firewall) and it states that port
> 14446 from IP 81.174.xxx.xxx is BLOCKED for some reason but I cant find
> anything in the ISA console that does block it.
> So as far as I can see, ISA is blocking the comms. The 14446 port is OPEN
> so
> I really dont understand.
> TIM
> "Hilary Cotter" wrote:
|||Hip, Hip Horrrray..... I've sorted the problem at last....
As I suspected ISA was blocking the port request inbound!.
All I had to do was to set the IP Packet to accept ALL PORTS inbound. This
may well sound trivial to you all but I had no idea that the inbound call
would use a random port even though I specified a fixed port to use.
I still cant use ODBCPING but what the hell it works...
Thanks for your help Hilary as I'm sure I will need more assitance soon!.
TIM
"Hilary Cotter" wrote:

> I think you need a networking specialist to help resolve this.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> ""confused"" <confused@.discussions.microsoft.com> wrote in message
> news:8B1A0BDE-375C-44EA-A6A2-B31462D028EF@.microsoft.com...
>
>