Problem accessing machine in another domain

[srp336]

I've got a problem browsing to machines in another domain. The company
I work for has another location that we connect to over a pair of T1s.
Until recently, there were no file sharing problems. Now, after a brief
outage on the T1 circuits, things don't seem to be working quite right.

To give an example, some of the machines I can get to fine, and some
give the "\\machine1 is inaccessible. The network path was not found"
error. I'm not sure why only some give this error. Of the servers on
that domain, the ones that work have WINS servers defined, and the ones
that don't have no WINS server defined. But, that doesn't explain the
workstations, all of which are on DHCP (receiving WINS settings
automatically) and some of which work and some of which don't.

I'm able to ping the machines, both by name and by ip address.
I've tried to get access to the machines (e.g., with net use, etc.)
both by name and by ip address with no luck.
Other machines in that domain have no problem access the machine we
have trouble getting to.

There is a two-way trust relationship between our domain and theirs.
Could something need to be reset? I can verify the trust on both ends
and it says everything is OK. I can't seem to spot any WINS problems.
What else can I check?

Thanks!

 

[Kurt]

Check your WINS configs, make sure your replication restarted after the T1
outage.

...kurt

 

[srp336]

Thanks, I'll check on that...

I also have a user on that remote network who can't see any zones since
the outage. He can get to machines directly, by name or ip, though. Is
this related to the first problem?

Thanks again!

 

[Kurt]

I don't know what you mean by "can't see any zones". If you mean you can't
see the workgroups or domains in My network Places, yes. You must have a
functioning WINS server to see NetBIOS names across a routed (like a T1)
link.

....kurt

 

[srp336]

Yes, that's what's happening. As far as I know, all clients at that
location get the same WINS server addresses through DHCP. And no one
else has this problem. There must be something I'm missing here...