Re: Problem accessing machine in another domain



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

...kurt


<srp336@xxxxxxxxxxxxxxx> wrote in message
news:1148331919.304423.192880@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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!



.



Relevant Pages

  • Re: [9fans] site is down?
    ... Murray Hill suffered a power oddity, I think a spike, on January 1st ... that caused a several-hour-long outage and seems to have caused ... miscellaneous other damage. ... We usually notice problems with the outside machines fairly soon (more ...
    (comp.os.plan9)
  • Problem accessing machine in another domain
    ... I've got a problem browsing to machines in another domain. ... that domain, the ones that work have WINS servers defined, and the ones ... Other machines in that domain have no problem access the machine we ... There is a two-way trust relationship between our domain and theirs. ...
    (microsoft.public.win2000.networking)
  • Re: [help] 1 cpu to rule them all
    ... >> configuration and maintenance in one place is a lot more economical than ... it isn't the price of the hardware that makes it ... > You can make things easier by having lots of machines that are virtually ... > directories) on servers. ...
    (comp.os.linux.hardware)
  • Re: Creating and AD domain
    ... > None of these machines are reachable from the internet, ... > access the internet, using existing DHCP and DNS servers. ... > As of now, I've got a domain created, the domain controller is up and has ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to access I/O port directly in VC6.0?
    ... As soon as you have standalone machines, ... Their "security" as far as servers was a joke; ... discovered the internal wireless network was completely unencrypted. ...
    (microsoft.public.vc.mfc)