Cannot Browse from domain populated subnets to remote subnets whichcontain only workgroup servers

[pag@associateddynamics.com]

We are unable to see a 2 remote subnets in the browser list, and the
machines in these subnets cannot see other machines in other subnets.
These problem subnets only contain Windows 2003 servers with manually
configured static IP addresses that are in separate workgroups.

We have the remaining subnets which contain machines in a single
domain and they are all visible, and browsing works correctly.

We have the following configuration

o Windows 2000 active directory environment updated to Windows 2003 R2
schema
o Wins installed on PDC which is a windows 2000 server on SP4
o Subnets connected by hardware VPN via routers
o All machines pointing to DNS and Wins on PDC
o Can successfully map network drives to problem workgroup machines
and map drives on problem machines to domain machines - although need
to specify valid login credentials
o Firewalling software not installed as all machines behind a hardware
firewall
o No packet filtering between subnets in either direction
o All machines are in DNS and resolve backwards and forwards correctly

We require browsing functionality for software that access machines
from the browser list.

[Phillip Windell]

The behavor you see is exactly the way it works. There is nothing "wrong"
with anything. Domains and Workgroups handle "browsing" differently.
Browsing also work via "broadcasts", so it will not work across subnets.

You have to run a WINS Server.
All machines (every last one) has to use the WINS Server in its TCP/IP
specs.

Once all machines are registered in the WINS Server the "browsing" will work
as normal.


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/downlo...7/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/e...epartners.mspx
-----------------------------------------------------

<pag@associateddynamics.com> wrote in message
news:f2b9d379-76e6-4476-b478-04379c6afe56@v67g2000hse.googlegroups.com...
> We are unable to see a 2 remote subnets in the browser list, and the
> machines in these subnets cannot see other machines in other subnets.
> These problem subnets only contain Windows 2003 servers with manually
> configured static IP addresses that are in separate workgroups.
>
> We have the remaining subnets which contain machines in a single
> domain and they are all visible, and browsing works correctly.
>
> We have the following configuration
>
> o Windows 2000 active directory environment updated to Windows 2003 R2
> schema
> o Wins installed on PDC which is a windows 2000 server on SP4
> o Subnets connected by hardware VPN via routers
> o All machines pointing to DNS and Wins on PDC
> o Can successfully map network drives to problem workgroup machines
> and map drives on problem machines to domain machines - although need
> to specify valid login credentials
> o Firewalling software not installed as all machines behind a hardware
> firewall
> o No packet filtering between subnets in either direction
> o All machines are in DNS and resolve backwards and forwards correctly
>
> We require browsing functionality for software that access machines
> from the browser list.

[pag@associateddynamics.com]

Thanks for your response.

I would expect to be able to browse different domains and workgroups
in both directions, and this is not working despite WINS being
installed.

I would expect to see on clicking Entire Network/Microsoft Windows
Network a list of all domains and workgroups.and browse down to them.
The problem workgroups are not showing.

WINS is installed on the domain and seems to be working correctly with
records from the problem workgroups and machines present.

Certainly if we plug in a machine in my subnet on a different
workgroup - its workgroup becomes visible in the browserlist alongside
the domain.

[Lanwench [MVP - Exchange]]

pag@associateddynamics.com wrote:
> Thanks for your response.
>
> I would expect to be able to browse different domains and workgroups
> in both directions, and this is not working despite WINS being
> installed.

Well, perhaps you might want to adjust some of your expectations :).
Browsing can be a PITA between routed subnets, even if you use WINS.
Frankly, I like having browsing as an option, but since I tend to use
domains, login scripts & mapped drive letters (and I know the UNC paths for
anything I haven't assigned a drive letter to) I can't see it as all that
necessary. Nice, but not necessary.
>
> I would expect to see on clicking Entire Network/Microsoft Windows
> Network a list of all domains and workgroups.and browse down to them.
> The problem workgroups are not showing.
>
> WINS is installed on the domain and seems to be working correctly with
> records from the problem workgroups and machines present.
>
> Certainly if we plug in a machine in my subnet on a different
> workgroup - its workgroup becomes visible in the browserlist alongside
> the domain.

Try posting an unedited ipconfig /all from your DC (presuming you run WINS
on your DC) and one of the problem clients.

[Phillip Windell]

<pag@associateddynamics.com> wrote in message
news:dc5bf10a-febb-41f5-aa5c-36b89a1ae2d3@d70g2000hsf.googlegroups.com...
> Thanks for your response.
>
> I would expect to be able to browse different domains and workgroups
> in both directions, and this is not working despite WINS being
> installed.

Get rid of the workgroup. It isn't work the time it takes to troubleshoot
it. If you can't get rid of it then at least make the Workgroup name the
same as the Domain Name so it becomes more transparent. There is no such
thing as a "real" workgroup membership, so changing the name should not have
any other side effects,...in fact, in reality, machines will communicate
fine even if the workgroups names are not the same.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------