WINS replication problems - some records seem to be missing

We have a T1 to another location of our company in another city. File
sharing between the two locations seems to have gone well for quite a
few months now, but recently a problem has been happening. Users on the
remote end have had access problems getting to random hosts on our end.
When they open the hosts in question in Network Neighborhood, they get
"<hostname> is not accessible. The network path was not found".

The WINS servers on their end replicate with the ones on our end
(push/pull). When I check the WINS on their end, I see Workstation
records, but no File Server records (which is what I'm assuming is
causing the above error). If I manually start a push replication from
our end, the records show up. What might the problem be?

The replication on both ends is using a persistent connection. Could
the connection have gotten broken and one or both of the WINS servers
not been aware of that? Has this happened to anyone else?

From a problem client immediately after getting a "network path
not found" error open and dos prompt and run nbtstat -c; what
do you see?
<(E-Mail Removed)> wrote in message news:
> We have a T1 to another location of our company in another city. File
> sharing between the two locations seems to have gone well for quite a
> few months now, but recently a problem has been happening. Users on the
> remote end have had access problems getting to random hosts on our end.
> When they open the hosts in question in Network Neighborhood, they get
> "<hostname> is not accessible. The network path was not found".
>
> The WINS servers on their end replicate with the ones on our end
> (push/pull). When I check the WINS on their end, I see Workstation
> records, but no File Server records (which is what I'm assuming is
> causing the above error). If I manually start a push replication from
> our end, the records show up. What might the problem be?
>
> The replication on both ends is using a persistent connection. Could
> the connection have gotten broken and one or both of the WINS servers
> not been aware of that? Has this happened to anyone else?
>

I'm not sure when this problem will resurface (hopefully never).

I don't know what nbtstat -c would have shown, but I'm assuming it
would show a single record for the remote host in question (type 00h,
and no type 20h). We were able to ping it by name, but not open it in
Network Neighborhood (the net use command worked by ip address, but not
by name).