Any update on this issue, please?
Thanks
Chris
"Chris" wrote:
> Thanks Bill,
>
> Now the strange thing is...the PDC of our local domain will access this
> remote network fine, and displays all the PCs + Servers on the remote
> network. Any other server2003 server (including the BDC, which we having the
> trouble with and need to access the remote network) will not connect. It
> shows the domain, but says 'cannot access...' as per my earlier message.
>
> Any XP PC on the local network can also access the remote network. The
> remote network can now access our local network as well through netork places
> and see all the PCs. It's literally all the server 2003 server on our local
> network, except the PDC.
>
> Any ideas?
>
> Thanks
>
> Chris
>
>
> "Bill Grant" wrote:
>
> > That is correct. You cannot access resources in another domain without
> > domain trusts.
> >
> > "Chris" <(E-Mail Removed)> wrote in message
> > news:3F300010-B179-4436-A04D-(E-Mail Removed)...
> > >I realised the VPN end-points didnt have NETBIOS broadcast enabled in their
> > > config. As soon as I enabled this the remote network appeared. However,
> > > When
> > > I double-click the remote network within My Network Places / Microsoft
> > > Windows Network it comes up with:
> > >
> > > 'domain' is not accessible. You might not have permission to use this
> > > network resource.....'
> > >
> > > I guess it's due to the fact that my local network (domain) doesn't have
> > > cross-forest trust with the remote network. Or am I barking up the wrong
> > > tree
> > > here? Any more help will be greatly appreciated.
> > >
> > > Thanks
> > >
> > > Chris
> > >
> > > "Bill Grant" wrote:
> > >
> > >> The display you see in My Network Places is built by the computer
> > >> browser
> > >> service. This is a legacy NT app which uses broadcasts and Netbios names.
> > >> It
> > >> usually fails in routed networks and WANs because the routers/WAN links
> > >> block broadcasts.
> > >>
> > >> To see a remote network in the list, the remote network would need to
> > >> be
> > >> using the same WINS server as your LAN, or the two WINS servers would
> > >> need
> > >> to replicate. Only WINS allows the browser service to operate across
> > >> routers/WAN links. It enables the master browsers to find each other and
> > >> build a network-wide browse list.
> > >>
> > >> Note that WINS does not build the browse list (as some believe). WINS
> > >> allows the browsers to operate by enabling them to resolve browser names
> > >> to
> > >> IP addresses and contact other browsers directly across routers/WAN
> > >> links.
> > >>
> > >> "Chris" <(E-Mail Removed)> wrote in message
> > >> news:A845ED53-157E-4DE1-86F1-(E-Mail Removed)...
> > >> >I am trying to 'see' a network within my network places. My local
> > >> >network
> > >> >is
> > >> > on one domain, and the remote network is on another domain (i.e. a
> > >> > different
> > >> > company).
> > >> > I have a local network on one IP range (10.x.x.x) and a remote network
> > >> > on
> > >> > a
> > >> > different range 192.x.x.x. I have a VPN setup so each network can talk
> > >> > directly to each other.
> > >> > On the remote network the server I am trying to access is a SBS2003
> > >> > with
> > >> > ISA2004. However, routing paths have been put in place so tha traffic
> > >> > to
> > >> > the
> > >> > 10.x.x.x range is routed directly through the VPN unit, and not
> > >> > ISA2004.
> > >> > Likewise for the local network. The local server has a routing path to
> > >> > route
> > >> > all traffic to the 192.x.x.x range through the VPN, and not the company
> > >> > firewall.
> > >> > There are other networks visible in my network places but not the one I
> > >> > need
> > >> > here.
> > >> > What can I try to make the remote ntwork visible / available?
> > >> >
> > >> > Thanks
> > >> >
> > >> > Chris
> > >>
> > >>
> > >>
> >
> >
> >
|