Paul
This is step by step what I do:
1. VPN is well configured. My VPN IP is 172.27.0.1 (PUBLISHER)
2. SUBSCRIBER is 172.27.0.10
3. I already registered on PUBLISHER the SUBSCRIBER as 172.27.0.10 (i also
used the Client Network Utility on the PUBLISHER to Alias this server with
his original name)
4. I already registered on SUBSCRIBER the PUBLISHER as 172.27.0.1 (i also
used the Client Network Utility on the SUBSCRIBER to Alias this server with
his original name)
5. I added to HOSTS file the ip and name of the PUBLISHER.
6. I'm testing VPN in a 10 computers LAN. PC1 is configured as VPN SERVER
and the rest, workstation/clients. Each workstation represents a national
location. For example, PC2 is City2, PC3 is Country1, PC4 is Country2... you
follow me?
When I register the sqlservers i have to use their IPs 'cause there is not
way for them to find themselves in the VPN network. For example, when i
register a new server in my Publisher, it automatically finds all the
servers in my LAN (not thru VPN network)... so, I have to manually adds the
server IP in order to reach it thru the VPN, not the LAN. (remember i'm
testing/simulating in my LAN). I think this is giving me the conflicts. When
my subscription tries to find JUCAR-2 (my VPN SERVER and SQL PUBLISHER) it
just says "It can't connect to JUCAR-2". I think the subscriber is doing
NOTHING with the IP cause the publication apparently appears under the
ServerName, not IP.
I keep on reading the Hilary Cotter book but i can't find anything useful
for this.
These are the error messages:
The process could not connect to Distributor 'JUCAR-2'. NOTE: The step was
retried the requested number of times (10) without succeeding. The step
failed.
That's it.
WEll... i keep on trying to find out... any other suggestion?
[quoted text, click to view] "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:%23JlXiZ1JGHA.1388@TK2MSFTNGP11.phx.gbl...
> Jose,
> can you post up the complete error message. If not a lot comes back, then
> please enable logging and post up that. I suspect it is a logon issue, but
> I'd like to see the message to confirm.
> Cheers,
> Paul Ibison SQL Server MVP,
www.replicationanswers.com > (recommended sql server 2000 replication book:
>
http://www.nwsu.com/0974973602p.html)
>
>
>
>