Connection problems (SQL 2000) -- sql server replication

Hilary Cotter
12/21/2006 12:00:00 AM

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

[quoted text, click to view]

confused
12/21/2006 4:12:00 AM

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.

sql server replication : Connection problems (SQL 2000)