Problem with push subscription where subscriber identified by IP not name

I have set up six push subscriptions of the same publication on a wide area
network successfully, but am having a problem with the seventh one. I think
the problem is due to the fact that the subscription was set up using the
subscribing server's IP address rather than network name (there is currently
a problem on the network so the server's name can't be resolved)
The error seen in the merge agent for the subscription is:
The subscription to publication 'PersonNameAddrUpdate' is invalid.
(Source: Merge Replication Provider (Agent); Error number: -2147201019)
------
The remote server is not defined as a subscription server.
(Source: xxx.xxx.xxx.xx (Data source); Error number: 14010)
------
(xxx.xxx.xxx.xx is the subscribing server's IP address)
Is there anything that can be done while we have this problem with the
network?
Try using the client network utility to map the subscriber's IP address to
its netbios name and then register that in Enterprise Manager and as a
subscriber.
HTH,
Paul Ibison
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:%237O3GIeTFHA.2812@.TK2MSFTNGP09.phx.gbl...
>I have set up six push subscriptions of the same publication on a wide area
>network successfully, but am having a problem with the seventh one. I think
>the problem is due to the fact that the subscription was set up using the
>subscribing server's IP address rather than network name (there is
>currently a problem on the network so the server's name can't be resolved)
> The error seen in the merge agent for the subscription is:
> The subscription to publication 'PersonNameAddrUpdate' is invalid.
> (Source: Merge Replication Provider (Agent); Error number: -2147201019)
> ------
> The remote server is not defined as a subscription server.
> (Source: xxx.xxx.xxx.xx (Data source); Error number: 14010)
> ------
> (xxx.xxx.xxx.xx is the subscribing server's IP address)
> Is there anything that can be done while we have this problem with the
> network?
>
|||I figured it out with help from this page:
http://www.adminlife.com/247referenc...36/184432.aspx
The answer was:
The error can also occur if the subscriber is registered using a TCP/IP
address instead of a Name.(see 321822). To work around, use the client
utilities to create an ALIAS name to the subscribers TCP/IP address and then
use that ALIAS name when registering the subscriber instead of the TCP/IP
address.
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:%237O3GIeTFHA.2812@.TK2MSFTNGP09.phx.gbl...
>I have set up six push subscriptions of the same publication on a wide area
>network successfully, but am having a problem with the seventh one. I think
>the problem is due to the fact that the subscription was set up using the
>subscribing server's IP address rather than network name (there is
>currently a problem on the network so the server's name can't be resolved)
> The error seen in the merge agent for the subscription is:
> The subscription to publication 'PersonNameAddrUpdate' is invalid.
> (Source: Merge Replication Provider (Agent); Error number: -2147201019)
> ------
> The remote server is not defined as a subscription server.
> (Source: xxx.xxx.xxx.xx (Data source); Error number: 14010)
> ------
> (xxx.xxx.xxx.xx is the subscribing server's IP address)
> Is there anything that can be done while we have this problem with the
> network?
>