NET VIEW /D:<DomainB> ends with an ERROR 2107

"The device is not connected."
What network services affect the proper resolution of this command?

Here is the scenario:

DomainA (main corporate domain)
DomainB (secondary development domain)

If I put the same command on DomainA, it resolves and displays the expected
output.
If I run the command against DomainB, it does not. I get the above error.

I can ping machines in DomainB by using their FQDN, and can ping the DC in
that domain. I have insured that the Domain is defined in DNS (forwarders in
place... .even tried a secondary zone replication in DomainA's DNS)

Now, to add a wrinkle, I have several corporate locations dispersed
geographically that are in DomainA.

If I remote into another office location, and I run the "net view
/d:<DomainB>" from there, it resolves. The site it can resolve from has a
pretty messed up networking environment, which leads me to believe that in
our desire to clean up and standardize our networking topology, that
something has been blocked on the networking side of the equation when we
redid the main office network locally where I am located.

So, in summary, if you type in the net view /d command, what (on the network
side of the equation) happens to that request and what needs to be in place
for the request to succeed?

Thanks for your time!
-=Craig

"Craig Tate" <(E-Mail Removed)> wrote in message
news:5263973D-25B9-4D4F-9D2F-(E-Mail Removed)...
> "The device is not connected."
> What network services affect the proper resolution of this command?
>
> Here is the scenario:
>
> DomainA (main corporate domain)
> DomainB (secondary development domain)
>
> If I put the same command on DomainA, it resolves and displays the
> expected
> output.
> If I run the command against DomainB, it does not. I get the above error.
>
> I can ping machines in DomainB by using their FQDN, and can ping the DC in
> that domain. I have insured that the Domain is defined in DNS (forwarders
> in
> place... .even tried a secondary zone replication in DomainA's DNS)
>
> Now, to add a wrinkle, I have several corporate locations dispersed
> geographically that are in DomainA.
>
> If I remote into another office location, and I run the "net view
> /d:<DomainB>" from there, it resolves. The site it can resolve from has a
> pretty messed up networking environment, which leads me to believe that in
> our desire to clean up and standardize our networking topology, that
> something has been blocked on the networking side of the equation when we
> redid the main office network locally where I am located.
>
> So, in summary, if you type in the net view /d command, what (on the
> network
> side of the equation) happens to that request and what needs to be in
> place
> for the request to succeed?
>
> Thanks for your time!
> -=Craig

The first thing you need to be aware of is that net view is a legacy
application that uses Netbios names and the computer browser service, not
DNS.

Are you running WINS? Are all machines using the same WINS server? If not,
do the WINS servers replicate? The browser service works on LAN broadcasts.
To work in a WAN, you need WINS to allow the browse masters to communicate
with each other across routers and WAN links.