Cross network acess by name YES, shown in browsing list NO

Hi everyone.

I'm writing because I'm having a weird problem and I couldn't find a
suitable solution searching here at the newsgroups or searching the
web.

The situation is the following:

At the office and at home I've got a Linksys router WRT54GL running
DD-WRT v23 vpn SP2 firmware in each place. The office router it's
running OpenVPN in server mode , and the home router is running OpenVPN
in client mode. The office subnet scope is 192.168.0.0/24 and the home
subnet scope is 192.168.1.0/24. The office subnet has a Windows 2003
Server as PDC, this PDC has DNS, Active Directory and WINS servers
installed. The home subnet is a workgroup of 2 computers, the workgroup
name is the same as the office domain that the PDC maintains. The
OpenVPN tunnel between the routers has the subnet scope
192.168.50.0/24.

The OpenVPN tunnel it's working find, I can ping office's computers
from home and ping home's computers from office. Both routers has in
their DHCP server configuration the instruction to set the WINS server
running in the Windows 2003 PDC at office side.

The weird problem comes with the NetBIOS names. From home I can access
an office shared resource by connecting for example a network drive and
set the path in the way \\<office_computer>\<shared folder>, I can do
the same the other way around, I mean, in an office computer access a
home shared resource. The problem comes when I tried to browse the
network list at home and at office. The home browsing list doesn't show
the office computers, and the office browsing list doesn't show home
computers. I checked WINS server entries and it has all the entries
corresponding to the office and to home computers, that's the reason
why I can access the shared resource crossing subnets.

I checked home's computers Windows registry keys:
HKLM\SYSTEM\CurrentControlSet\Services\Browser\Par ameters\MaintainServerList
was setting in Auto
HKLM\SYSTEM\CurrentControlSet\Services\Browser\Par ameters\IsDomainMaster
was setting in FALSE

The IsDomainMaster I left it as it was, with FALSE value, and the
MaintainServerList key I changed its value to FALSE, I rebooted the
computer and after that in the browsing list of home computer the
office computers appeared, but the other home computer and that
computer itself didn't appear.

I started to think that the problem was that home's network is a
workgroup with the same name as the office's domain name, so I changed
it but it didn't work, the "new" workgroup didn't appeared in the
home's browsing list. I changed back the MaintainServerList to Auto
value, I rebooted and then the "new" workgroup name appear in the
browsing list but the office domain disappeared.

Any way to solve this??

Another thing to mention, at office I've got one computer that is not
joined to the domain and it has a workgroup name same as the domain
name. This computer browsing list shows office computers joined to the
domain merged with this computer isolated from the domain, this is a
similar situation as the home's computers but the problem is that
home's computers doesn't merge the browsing lists. The only difference
here is that this isolate office computer is in the same subnet as the
rest of the domain, and home's computers are in a different subnet as I
describe at the start of this post.

Any hint will be usefull to me because I'm run out of ideas.

Thanks in advance.

Assuming you have WINS setup correctly, you may want to check the master browser.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
Hi everyone.

I'm writing because I'm having a weird problem and I couldn't find a
suitable solution searching here at the newsgroups or searching the
web.

The situation is the following:

At the office and at home I've got a Linksys router WRT54GL running
DD-WRT v23 vpn SP2 firmware in each place. The office router it's
running OpenVPN in server mode , and the home router is running OpenVPN
in client mode. The office subnet scope is 192.168.0.0/24 and the home
subnet scope is 192.168.1.0/24. The office subnet has a Windows 2003
Server as PDC, this PDC has DNS, Active Directory and WINS servers
installed. The home subnet is a workgroup of 2 computers, the workgroup
name is the same as the office domain that the PDC maintains. The
OpenVPN tunnel between the routers has the subnet scope
192.168.50.0/24.

The OpenVPN tunnel it's working find, I can ping office's computers
from home and ping home's computers from office. Both routers has in
their DHCP server configuration the instruction to set the WINS server
running in the Windows 2003 PDC at office side.

The weird problem comes with the NetBIOS names. From home I can access
an office shared resource by connecting for example a network drive and
set the path in the way \\<office_computer>\<shared folder>, I can do
the same the other way around, I mean, in an office computer access a
home shared resource. The problem comes when I tried to browse the
network list at home and at office. The home browsing list doesn't show
the office computers, and the office browsing list doesn't show home
computers. I checked WINS server entries and it has all the entries
corresponding to the office and to home computers, that's the reason
why I can access the shared resource crossing subnets.

I checked home's computers Windows registry keys:
HKLM\SYSTEM\CurrentControlSet\Services\Browser\Par ameters\MaintainServerList
was setting in Auto
HKLM\SYSTEM\CurrentControlSet\Services\Browser\Par ameters\IsDomainMaster
was setting in FALSE

The IsDomainMaster I left it as it was, with FALSE value, and the
MaintainServerList key I changed its value to FALSE, I rebooted the
computer and after that in the browsing list of home computer the
office computers appeared, but the other home computer and that
computer itself didn't appear.

I started to think that the problem was that home's network is a
workgroup with the same name as the office's domain name, so I changed
it but it didn't work, the "new" workgroup didn't appeared in the
home's browsing list. I changed back the MaintainServerList to Auto
value, I rebooted and then the "new" workgroup name appear in the
browsing list but the office domain disappeared.

Any way to solve this??

Another thing to mention, at office I've got one computer that is not
joined to the domain and it has a workgroup name same as the domain
name. This computer browsing list shows office computers joined to the
domain merged with this computer isolated from the domain, this is a
similar situation as the home's computers but the problem is that
home's computers doesn't merge the browsing lists. The only difference
here is that this isolate office computer is in the same subnet as the
rest of the domain, and home's computers are in a different subnet as I
describe at the start of this post.

Any hint will be usefull to me because I'm run out of ideas.

Thanks in advance.

Robert, do I need to have a master browse in each side (one in the
office and one at home) ???

Because now I've got only one master broser, it's the Windows 2003
Server that it's the domain PDC that's located at the office.


Robert L [MVP - Networking] ha escrito:

> Assuming you have WINS setup correctly, you may want to check the master browser.
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
> Hi everyone.
>
> I'm writing because I'm having a weird problem and I couldn't find a
> suitable solution searching here at the newsgroups or searching the
> web.
>
> The situation is the following:
>
> At the office and at home I've got a Linksys router WRT54GL running
> DD-WRT v23 vpn SP2 firmware in each place. The office router it's
> running OpenVPN in server mode , and the home router is running OpenVPN
> in client mode. The office subnet scope is 192.168.0.0/24 and the home
> subnet scope is 192.168.1.0/24. The office subnet has a Windows 2003
> Server as PDC, this PDC has DNS, Active Directory and WINS servers
> installed. The home subnet is a workgroup of 2 computers, the workgroup
> name is the same as the office domain that the PDC maintains. The
> OpenVPN tunnel between the routers has the subnet scope
> 192.168.50.0/24.
>
> The OpenVPN tunnel it's working find, I can ping office's computers
> from home and ping home's computers from office. Both routers has in
> their DHCP server configuration the instruction to set the WINS server
> running in the Windows 2003 PDC at office side.
>
> The weird problem comes with the NetBIOS names. From home I can access
> an office shared resource by connecting for example a network drive and
> set the path in the way \\<office_computer>\<shared folder>, I can do
> the same the other way around, I mean, in an office computer access a
> home shared resource. The problem comes when I tried to browse the
> network list at home and at office. The home browsing list doesn't show
> the office computers, and the office browsing list doesn't show home
> computers. I checked WINS server entries and it has all the entries
> corresponding to the office and to home computers, that's the reason
> why I can access the shared resource crossing subnets.
>
> I checked home's computers Windows registry keys:
> HKLM\SYSTEM\CurrentControlSet\Services\Browser\Par ameters\MaintainServerList
> was setting in Auto
> HKLM\SYSTEM\CurrentControlSet\Services\Browser\Par ameters\IsDomainMaster
> was setting in FALSE
>
> The IsDomainMaster I left it as it was, with FALSE value, and the
> MaintainServerList key I changed its value to FALSE, I rebooted the
> computer and after that in the browsing list of home computer the
> office computers appeared, but the other home computer and that
> computer itself didn't appear.
>
> I started to think that the problem was that home's network is a
> workgroup with the same name as the office's domain name, so I changed
> it but it didn't work, the "new" workgroup didn't appeared in the
> home's browsing list. I changed back the MaintainServerList to Auto
> value, I rebooted and then the "new" workgroup name appear in the
> browsing list but the office domain disappeared.
>
> Any way to solve this??
>
> Another thing to mention, at office I've got one computer that is not
> joined to the domain and it has a workgroup name same as the domain
> name. This computer browsing list shows office computers joined to the
> domain merged with this computer isolated from the domain, this is a
> similar situation as the home's computers but the problem is that
> home's computers doesn't merge the browsing lists. The only difference
> here is that this isolate office computer is in the same subnet as the
> rest of the domain, and home's computers are in a different subnet as I
> describe at the start of this post.
>
> Any hint will be usefull to me because I'm run out of ideas.
>
> Thanks in advance.
>
> ------=_NextPart_000_003A_01C70EE5.D470F260
> Content-Type: text/html; charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
> X-Google-AttachSize: 5104
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
> <META content="MSHTML 6.00.2900.2995" name=GENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=#ffffff>
> <DIV>Assuming you have WINS setup correctly, you may want to check the master
> browser.</DIV>
> <DIV><BR>Bob Lin, MS-MVP, MCSE &amp; CNE<BR>Networking, Internet, Routing, VPN
> Troubleshooting on <A
> href="http://www.ChicagoTech.net">http://www.ChicagoTech.net</A> <BR>How to
> Setup Windows, Network, VPN &amp; Remote Access on <A
> href="http://www.HowToNetworking.com">http://www.HowToNetworking.com</A> </DIV>
> <BLOCKQUOTE
> style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>&lt;<A href="private.php?do=newpm&u=">santiago78@gmai l.com</A>&gt;
> wrote in message <A
> href="news:(E-Mail Removed) glegroups.com">news:1164295527.557408.62480@l12g20 00cwl.googlegroups.com</A>...</DIV>Hi
> everyone.<BR><BR>I'm writing because I'm having a weird problem and I couldn't
> find a<BR>suitable solution searching here at the newsgroups or searching
> the<BR>web.<BR><BR>The situation is the following:<BR><BR>At the office and at
> home I've got a Linksys router WRT54GL running<BR>DD-WRT v23 vpn SP2 firmware
> in each place. The office router it's<BR>running OpenVPN in server mode , and
> the home router is running OpenVPN<BR>in client mode. The office subnet scope
> is 192.168.0.0/24 and the home<BR>subnet scope is 192.168.1.0/24. The office
> subnet has a Windows 2003<BR>Server as PDC, this PDC has DNS, Active Directory
> and WINS servers<BR>installed. The home subnet is a workgroup of 2 computers,
> the workgroup<BR>name is the same as the office domain that the PDC maintains.
> The<BR>OpenVPN tunnel between the routers has the subnet
> scope<BR>192.168.50.0/24.<BR><BR>The OpenVPN tunnel it's working find, I can
> ping office's computers<BR>from home and ping home's computers from office.
> Both routers has in<BR>their DHCP server configuration the instruction to set
> the WINS server<BR>running in the Windows 2003 PDC at office side.<BR><BR>The
> weird problem comes with the NetBIOS names. From home I can access<BR>an
> office shared resource by connecting for example a network drive and<BR>set
> the path in the way <A
> href="file://\\<office_computer>\<shared">\\&lt;office_computer &gt;\&lt;shared</A>
> folder&gt;, I can do<BR>the same the other way around, I mean, in an office
> computer access a<BR>home shared resource. The problem comes when I tried to
> browse the<BR>network list at home and at office. The home browsing list
> doesn't show<BR>the office computers, and the office browsing list doesn't
> show home<BR>computers. I checked WINS server entries and it has all the
> entries<BR>corresponding to the office and to home computers, that's the
> reason<BR>why I can access the shared resource crossing subnets.<BR><BR>I
> checked home's computers Windows registry
> keys:<BR>HKLM\SYSTEM\CurrentControlSet\Services\Br owser\Parameters\MaintainServerList<BR>was
> setting in
> Auto<BR>HKLM\SYSTEM\CurrentControlSet\Services\Bro wser\Parameters\IsDomainMaster<BR>was
> setting in FALSE<BR><BR>The IsDomainMaster I left it as it was, with FALSE
> value, and the<BR>MaintainServerList key I changed its value to FALSE, I
> rebooted the<BR>computer and after that in the browsing list of home computer
> the<BR>office computers appeared, but the other home computer and
> that<BR>computer itself didn't appear.<BR><BR>I started to think that the
> problem was that home's network is a<BR>workgroup with the same name as the
> office's domain name, so I changed<BR>it but it didn't work, the "new"
> workgroup didn't appeared in the<BR>home's browsing list. I changed back the
> MaintainServerList to Auto<BR>value, I rebooted and then the "new" workgroup
> name appear in the<BR>browsing list but the office domain
> disappeared.<BR><BR>Any way to solve this??<BR><BR>Another thing to mention,
> at office I've got one computer that is not<BR>joined to the domain and it has
> a workgroup name same as the domain<BR>name. This computer browsing list shows
> office computers joined to the<BR>domain merged with this computer isolated
> from the domain, this is a<BR>similar situation as the home's computers but
> the problem is that<BR>home's computers doesn't merge the browsing lists. The
> only difference<BR>here is that this isolate office computer is in the same
> subnet as the<BR>rest of the domain, and home's computers are in a different
> subnet as I<BR>describe at the start of this post.<BR><BR>Any hint will be
> usefull to me because I'm run out of ideas.<BR><BR>Thanks in
> advance.<BR></BLOCKQUOTE></BODY></HTML>
>
> ------=_NextPart_000_003A_01C70EE5.D470F260--

This is more or less the expected behavior. You should get a unified browse
list if you join the home computers to the domain. If instead they are
joined to a workgroup with the same NetBIOS name as the domain, you "may" be
able to get a unified browse list on the home network by:

1. Set MaintainServerList to Yes or auto.

2. Add an lmhosts file entry:

<IP address> <PDC emulator name> #PRE #DOM:<NetBIOSDomainName>

Sometimes this works, and sometimes .............:

http://support.microsoft.com/kb/150800/en-us

Doug Sherman
MCSE, MCSA, MCP+I, MVP

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hi everyone.
>
> I'm writing because I'm having a weird problem and I couldn't find a
> suitable solution searching here at the newsgroups or searching the
> web.
>
> The situation is the following:
>
> At the office and at home I've got a Linksys router WRT54GL running
> DD-WRT v23 vpn SP2 firmware in each place. The office router it's
> running OpenVPN in server mode , and the home router is running OpenVPN
> in client mode. The office subnet scope is 192.168.0.0/24 and the home
> subnet scope is 192.168.1.0/24. The office subnet has a Windows 2003
> Server as PDC, this PDC has DNS, Active Directory and WINS servers
> installed. The home subnet is a workgroup of 2 computers, the workgroup
> name is the same as the office domain that the PDC maintains. The
> OpenVPN tunnel between the routers has the subnet scope
> 192.168.50.0/24.
>
> The OpenVPN tunnel it's working find, I can ping office's computers
> from home and ping home's computers from office. Both routers has in
> their DHCP server configuration the instruction to set the WINS server
> running in the Windows 2003 PDC at office side.
>
> The weird problem comes with the NetBIOS names. From home I can access
> an office shared resource by connecting for example a network drive and
> set the path in the way \\<office_computer>\<shared folder>, I can do
> the same the other way around, I mean, in an office computer access a
> home shared resource. The problem comes when I tried to browse the
> network list at home and at office. The home browsing list doesn't show
> the office computers, and the office browsing list doesn't show home
> computers. I checked WINS server entries and it has all the entries
> corresponding to the office and to home computers, that's the reason
> why I can access the shared resource crossing subnets.
>
> I checked home's computers Windows registry keys:
>
HKLM\SYSTEM\CurrentControlSet\Services\Browser\Par ameters\MaintainServerList
> was setting in Auto
> HKLM\SYSTEM\CurrentControlSet\Services\Browser\Par ameters\IsDomainMaster
> was setting in FALSE
>
> The IsDomainMaster I left it as it was, with FALSE value, and the
> MaintainServerList key I changed its value to FALSE, I rebooted the
> computer and after that in the browsing list of home computer the
> office computers appeared, but the other home computer and that
> computer itself didn't appear.
>
> I started to think that the problem was that home's network is a
> workgroup with the same name as the office's domain name, so I changed
> it but it didn't work, the "new" workgroup didn't appeared in the
> home's browsing list. I changed back the MaintainServerList to Auto
> value, I rebooted and then the "new" workgroup name appear in the
> browsing list but the office domain disappeared.
>
> Any way to solve this??
>
> Another thing to mention, at office I've got one computer that is not
> joined to the domain and it has a workgroup name same as the domain
> name. This computer browsing list shows office computers joined to the
> domain merged with this computer isolated from the domain, this is a
> similar situation as the home's computers but the problem is that
> home's computers doesn't merge the browsing lists. The only difference
> here is that this isolate office computer is in the same subnet as the
> rest of the domain, and home's computers are in a different subnet as I
> describe at the start of this post.
>
> Any hint will be usefull to me because I'm run out of ideas.
>
> Thanks in advance.
>

Hi Doug, I tried your solution and it didn't work :-(

I've read the KB article and I think that I know the reason why the
solution didn't work. Using LMHOSTS file at home computers and setting
in it the NetBIOS name of the PDC located at the office it's way to
implement a kind of WINS in static way for home subnet, but in my case
WINS server located at the office is accessible from home computers.
Looking at the WINS console I found that home computers where correctly
registered. Also I tried to execute nbtstat -c at one of the home
computers (previously to try your solution) and the "DOMAIN<1b>"
registry pointing to the PDC IP appear.

After reading the KB article (I thank you very much for this
information) I found that the problem is that behaviour described in
the Summary and More Information sections of that article is not
currently happen in my case (or I cannot find the way to setup
computers and networks to make it happen).

The PDC located at office is the Domain Master Browser, I'm sure of
that because running nbtstat -n in the PDC the "DOMAIN<1b>" registry
appear. My issue is that I don't know if the computer that I mainly use
at home is set at Segment Master Browse for the workgroup network build
at home.

There is a thing very clear after doing a lot of trial & error: If the
value of
HKLM\SYSTEM\CurrentControlSet\Services\Browser\Par ameters\MaintainServerList
is Auto or TRUE at home computers at the workgroup, the browsing list
only contains the workgroup computers, and if the value of that
registry key is FALSE the browsing list contains the office computers
only.

In both cases shared resources from office computers can be access
without problem, but for that I've got to know the name and in which
office's computer is located the share resource. With the registry key
set in FALSE I can explore from home the office's share resources, and
with the registry key set in TRUE I can only explore the home's shared
resources, and what I want and need is to explore at the same time the
shared resources from office's and home's computers.

Any idea??

Thanks very much.

On Nov 23, 1:58 pm, "Doug Sherman [MVP]"
<nodspamher...@notampabayspamforme.rr.com> wrote:
> This is more or less the expected behavior. You should get a unified browse
> list if you join the home computers to the domain. If instead they are
> joined to a workgroup with the same NetBIOS name as the domain, you "may" be
> able to get a unified browse list on the home network by:
>
> 1. Set MaintainServerList to Yes or auto.
>
> 2. Add an lmhosts file entry:
>
> <IP address> <PDC emulator name> #PRE #DOM:<NetBIOSDomainName>
>
> Sometimes this works, and sometimes .............:
>
> http://support.microsoft.com/kb/150800/en-us
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>

You've grasped the issue well - unfortunately understanding it doesn't go
very far towards solving it. The issue of workgroup vs. domain browsing and
their interaction between subnets has remained more or less unchanged since
NT 4.0. Sometimes there is no solution.

Something else which sometimes works is to join the home computers to a
different workgroup. On the WINS server manually create a 1b record for
this 'domain' pointing to the master browser on the home network - you can
also try setting this machine to IsDomainMaster = true. You can also try
this keeping the workgroup name the same as that of the domain. One way or
another you are trying to trick a workgroup machine machine into reporting
itself as a segment master browser (something it will not normally do)
and/or getting the PDC to believe that a workgroup machine is a domain
controller. The whole process involves trial and error with no guarantee of
success.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"santiago78" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hi Doug, I tried your solution and it didn't work :-(
>
> I've read the KB article and I think that I know the reason why the
> solution didn't work. Using LMHOSTS file at home computers and setting
> in it the NetBIOS name of the PDC located at the office it's way to
> implement a kind of WINS in static way for home subnet, but in my case
> WINS server located at the office is accessible from home computers.
> Looking at the WINS console I found that home computers where correctly
> registered. Also I tried to execute nbtstat -c at one of the home
> computers (previously to try your solution) and the "DOMAIN<1b>"
> registry pointing to the PDC IP appear.
>
> After reading the KB article (I thank you very much for this
> information) I found that the problem is that behaviour described in
> the Summary and More Information sections of that article is not
> currently happen in my case (or I cannot find the way to setup
> computers and networks to make it happen).
>
> The PDC located at office is the Domain Master Browser, I'm sure of
> that because running nbtstat -n in the PDC the "DOMAIN<1b>" registry
> appear. My issue is that I don't know if the computer that I mainly use
> at home is set at Segment Master Browse for the workgroup network build
> at home.
>
> There is a thing very clear after doing a lot of trial & error: If the
> value of
>
HKLM\SYSTEM\CurrentControlSet\Services\Browser\Par ameters\MaintainServerList
> is Auto or TRUE at home computers at the workgroup, the browsing list
> only contains the workgroup computers, and if the value of that
> registry key is FALSE the browsing list contains the office computers
> only.
>
> In both cases shared resources from office computers can be access
> without problem, but for that I've got to know the name and in which
> office's computer is located the share resource. With the registry key
> set in FALSE I can explore from home the office's share resources, and
> with the registry key set in TRUE I can only explore the home's shared
> resources, and what I want and need is to explore at the same time the
> shared resources from office's and home's computers.
>
> Any idea??
>
> Thanks very much.
>
> On Nov 23, 1:58 pm, "Doug Sherman [MVP]"
> <nodspamher...@notampabayspamforme.rr.com> wrote:
> > This is more or less the expected behavior. You should get a unified
browse
> > list if you join the home computers to the domain. If instead they are
> > joined to a workgroup with the same NetBIOS name as the domain, you
"may" be
> > able to get a unified browse list on the home network by:
> >
> > 1. Set MaintainServerList to Yes or auto.
> >
> > 2. Add an lmhosts file entry:
> >
> > <IP address> <PDC emulator name> #PRE #DOM:<NetBIOSDomainName>
> >
> > Sometimes this works, and sometimes .............:
> >
> > http://support.microsoft.com/kb/150800/en-us
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
>

Thanks Doug... I will try during the weekend and later I will post the
results.

On 24 nov, 14:20, "Doug Sherman [MVP]"
<nodspamher...@notampabayspamforme.rr.com> wrote:
> You've grasped the issue well - unfortunately understanding it doesn't go
> very far towards solving it. The issue of workgroup vs. domain browsing and
> their interaction between subnets has remained more or less unchanged since
> NT 4.0. Sometimes there is no solution.
>
> Something else which sometimes works is to join the home computers to a
> different workgroup. On the WINS server manually create a 1b record for
> this 'domain' pointing to the master browser on the home network - you can
> also try setting this machine to IsDomainMaster = true. You can also try
> this keeping the workgroup name the same as that of the domain. One way or
> another you are trying to trick a workgroup machine machine into reporting
> itself as a segment master browser (something it will not normally do)
> and/or getting the PDC to believe that a workgroup machine is a domain
> controller. The whole process involves trial and error with no guarantee of
> success.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "santiago78" <santiag...@gmail.com> wrote in messagenews:(E-Mail Removed) oglegroups.com...
>
> > Hi Doug, I tried your solution and it didn't work :-(
>
> > I've read the KB article and I think that I know the reason why the
> > solution didn't work. Using LMHOSTS file at home computers and setting
> > in it the NetBIOS name of the PDC located at the office it's way to
> > implement a kind of WINS in static way for home subnet, but in my case
> > WINS server located at the office is accessible from home computers.
> > Looking at the WINS console I found that home computers where correctly
> > registered. Also I tried to execute nbtstat -c at one of the home
> > computers (previously to try your solution) and the "DOMAIN<1b>"
> > registry pointing to the PDC IP appear.
>
> > After reading the KB article (I thank you very much for this
> > information) I found that the problem is that behaviour described in
> > the Summary and More Information sections of that article is not
> > currently happen in my case (or I cannot find the way to setup
> > computers and networks to make it happen).
>
> > The PDC located at office is the Domain Master Browser, I'm sure of
> > that because running nbtstat -n in the PDC the "DOMAIN<1b>" registry
> > appear. My issue is that I don't know if the computer that I mainly use
> > at home is set at Segment Master Browse for the workgroup network build
> > at home.
>
> > There is a thing very clear after doing a lot of trial & error: If the
> > value ofHKLM\SYSTEM\CurrentControlSet\Services\Browser\P arameters\MaintainServerList
>
> > is Auto or TRUE at home computers at the workgroup, the browsing list
> > only contains the workgroup computers, and if the value of that
> > registry key is FALSE the browsing list contains the office computers
> > only.
>
> > In both cases shared resources from office computers can be access
> > without problem, but for that I've got to know the name and in which
> > office's computer is located the share resource. With the registry key
> > set in FALSE I can explore from home the office's share resources, and
> > with the registry key set in TRUE I can only explore the home's shared
> > resources, and what I want and need is to explore at the same time the
> > shared resources from office's and home's computers.
>
> > Any idea??
>
> > Thanks very much.
>
> > On Nov 23, 1:58 pm, "Doug Sherman [MVP]"
> > <nodspamher...@notampabayspamforme.rr.com> wrote:
> > > This is more or less the expected behavior. You should get a unified
> browse
> > > list if you join the home computers to the domain. If instead they are
> > > joined to a workgroup with the same NetBIOS name as the domain, you
> "may" be
> > > able to get a unified browse list on the home network by:
>
> > > 1. Set MaintainServerList to Yes or auto.
>
> > > 2. Add an lmhosts file entry:
>
> > > <IP address> <PDC emulator name> #PRE #DOM:<NetBIOSDomainName>
>
> > > Sometimes this works, and sometimes .............:
>
> > >http://support.microsoft.com/kb/150800/en-us
>
> > > Doug Sherman
> > > MCSE, MCSA, MCP+I, MVP

Let us know how it goes - good luck.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"santiago78" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ps.com...
> Thanks Doug... I will try during the weekend and later I will post the
> results.
>
> On 24 nov, 14:20, "Doug Sherman [MVP]"
> <nodspamher...@notampabayspamforme.rr.com> wrote:
> > You've grasped the issue well - unfortunately understanding it doesn't
go
> > very far towards solving it. The issue of workgroup vs. domain browsing
and
> > their interaction between subnets has remained more or less unchanged
since
> > NT 4.0. Sometimes there is no solution.
> >
> > Something else which sometimes works is to join the home computers to a
> > different workgroup. On the WINS server manually create a 1b record for
> > this 'domain' pointing to the master browser on the home network - you
can
> > also try setting this machine to IsDomainMaster = true. You can also
try
> > this keeping the workgroup name the same as that of the domain. One way
or
> > another you are trying to trick a workgroup machine machine into
reporting
> > itself as a segment master browser (something it will not normally do)
> > and/or getting the PDC to believe that a workgroup machine is a domain
> > controller. The whole process involves trial and error with no
guarantee of
> > success.
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "santiago78" <santiag...@gmail.com> wrote in
messagenews:(E-Mail Removed) oglegroups.com...
> >
> > > Hi Doug, I tried your solution and it didn't work :-(
> >
> > > I've read the KB article and I think that I know the reason why the
> > > solution didn't work. Using LMHOSTS file at home computers and setting
> > > in it the NetBIOS name of the PDC located at the office it's way to
> > > implement a kind of WINS in static way for home subnet, but in my case
> > > WINS server located at the office is accessible from home computers.
> > > Looking at the WINS console I found that home computers where
correctly
> > > registered. Also I tried to execute nbtstat -c at one of the home
> > > computers (previously to try your solution) and the "DOMAIN<1b>"
> > > registry pointing to the PDC IP appear.
> >
> > > After reading the KB article (I thank you very much for this
> > > information) I found that the problem is that behaviour described in
> > > the Summary and More Information sections of that article is not
> > > currently happen in my case (or I cannot find the way to setup
> > > computers and networks to make it happen).
> >
> > > The PDC located at office is the Domain Master Browser, I'm sure of
> > > that because running nbtstat -n in the PDC the "DOMAIN<1b>" registry
> > > appear. My issue is that I don't know if the computer that I mainly
use
> > > at home is set at Segment Master Browse for the workgroup network
build
> > > at home.
> >
> > > There is a thing very clear after doing a lot of trial & error: If the
> > > value
ofHKLM\SYSTEM\CurrentControlSet\Services\Browser\P arameters\MaintainServerLi
st
> >
> > > is Auto or TRUE at home computers at the workgroup, the browsing list
> > > only contains the workgroup computers, and if the value of that
> > > registry key is FALSE the browsing list contains the office computers
> > > only.
> >
> > > In both cases shared resources from office computers can be access
> > > without problem, but for that I've got to know the name and in which
> > > office's computer is located the share resource. With the registry key
> > > set in FALSE I can explore from home the office's share resources, and
> > > with the registry key set in TRUE I can only explore the home's shared
> > > resources, and what I want and need is to explore at the same time the
> > > shared resources from office's and home's computers.
> >
> > > Any idea??
> >
> > > Thanks very much.
> >
> > > On Nov 23, 1:58 pm, "Doug Sherman [MVP]"
> > > <nodspamher...@notampabayspamforme.rr.com> wrote:
> > > > This is more or less the expected behavior. You should get a
unified
> > browse
> > > > list if you join the home computers to the domain. If instead they
are
> > > > joined to a workgroup with the same NetBIOS name as the domain, you
> > "may" be
> > > > able to get a unified browse list on the home network by:
> >
> > > > 1. Set MaintainServerList to Yes or auto.
> >
> > > > 2. Add an lmhosts file entry:
> >
> > > > <IP address> <PDC emulator name> #PRE #DOM:<NetBIOSDomainName>
> >
> > > > Sometimes this works, and sometimes .............:
> >
> > > >http://support.microsoft.com/kb/150800/en-us
> >
> > > > Doug Sherman
> > > > MCSE, MCSA, MCP+I, MVP
>

Unbelievable!!!!

I tried everything... set the IsDomainMaster in true while changing the
workgroup name at the primary used computer, I also tried
(unsuccessfully) to create in the WINS server a 1b registry with the
workgroup name and the IP of the primary used computer at home, because
1b registry with same names (at that moment I was trying with domain
and workgroup names equal) and different IPs aren't allow in the WINS
server. Then I tried to change again the workgroup name and create the
1b registry for that workgroup name, thing I did with success but it
was useless because when browsing the network at home computer (either
combining IsDomainMaster in TRUE or FALSE with MaintainServerList in
TRUE or FALSE) only the workgroup with the new name was seen, and not
the workgroup AND the office domain.

To sum up, nothing that came to my mind worked... but the miracle
happened ;-)

By chance I bring to home today a notebook that is commonly use at
office. This notebook as Windows 2000 Workstation with SP4. This
notebook is configured to join the domain when it's at the office, but
when I used outside of it (like at home) I log into it as standalone
computer.

I left the notebook on, and by chance I sit in front of the primary
computer that I used at home, I inspected the browsing list just to
know which are the shared resources of that computer and I saw by first
time since I began with all this mess, the complete list merged!!!!
office computers and home computers all together!!!!

I checked the settings of the home computers, all of them have
IsDomainMaster and MaintainServerList in FALSE. No lmhost file in any
of those computers. The notebook with Windows 2000 SP4 was not touched
in its configuration, it has IsDomainMaster in FALSE and
MaintainServerList in Auto.

I think that the miracle... or talking seriously, the solution... it
was to connect to the home network a computer that previously was
joined at the office network.

I don't know why the browsing list crossing networks has this strange
behaviour.

Perhaps this expierence helps another one to avoid to suffer all this
mess ;-)


On 24 nov, 22:43, "Doug Sherman [MVP]"
<nodspamher...@notampabayspamforme.rr.com> wrote:
> Let us know how it goes - good luck.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "santiago78" <santiag...@gmail.com> wrote in messagenews:(E-Mail Removed) glegroups.com...
>

I've got to add some sad information.

Today morning I wake up, I turn on the primary computer that I use at
home and when I tried to browse the network to enter into a share
resource from an office computer, office computers had gone. So I tried
to reproduce the situation that yesterday made that the browsing list
showed the 2 network merged, so I turned on the notebook that I brought
from the office yesterday that has Windows 2000. After the notebook was
turned on the browsing list started to show the two network merged.
After seeing that, using remote desktop to the WINS server I check the
WINS entries registered with the IP of the Windows 2000 notebook. I
wrote down those entries in a paper, I turned off the notebook and I
tried to make that the primary computer that I used at home pushes to
the WINS server the same entries as the notebook with Windows 2000
does. I did it with success, with only the primary computer at home
turned on, using remote desktop to WINS server I checked that the
entries at the server were the same that the notebook push to the
server but with the IP corresponding to the primary computer at home.
The registry keys IsDomainMaster and MaintainServerList in the notebook
were set in FALSE and Auto, so I did the same at the primary computer
at home. After rebooting I tried browsing the network and it didn't
work, again only home computers were visible. I realized that the
notebook has a computer account in the office's active directory so I
create an account for the primary home computer, but after rebooting
the home computer, it didn't work too. Finally, just for trying, I
change the windows configuration of the primary home computer to join
the office domain. The computer was joined successfully. I rebooted, I
log on into the home computer with the account that I've got at the
office domain and when I tried to browse the network, again, only home
computers appear, in this case only one, because only the primary home
computer was turned on.

Conclution after all this expierence: I'm 99.99% sure that the
implementation of the browsing network system is different from Windows
2000 SP4 to Windows XP SP2. Although you can try any work around under
Windows XP, it won't work because it seems to has a bug in the browsing
list creation (maybe produced in some of the updates since Windows XP
was released to try to solve a more important bug).

On 27 nov, 23:42, "santiago78" <santiag...@gmail.com> wrote:
> Unbelievable!!!!
>
> I tried everything... set the IsDomainMaster in true while changing the
> workgroup name at the primary used computer, I also tried
> (unsuccessfully) to create in the WINS server a 1b registry with the
> workgroup name and the IP of the primary used computer at home, because
> 1b registry with same names (at that moment I was trying with domain
> and workgroup names equal) and different IPs aren't allow in the WINS
> server. Then I tried to change again the workgroup name and create the
> 1b registry for that workgroup name, thing I did with success but it
> was useless because when browsing the network at home computer (either
> combining IsDomainMaster in TRUE or FALSE with MaintainServerList in
> TRUE or FALSE) only the workgroup with the new name was seen, and not
> the workgroup AND the office domain.
>
> To sum up, nothing that came to my mind worked... but the miracle
> happened ;-)
>
> By chance I bring to home today a notebook that is commonly use at
> office. This notebook as Windows 2000 Workstation with SP4. This
> notebook is configured to join the domain when it's at the office, but
> when I used outside of it (like at home) I log into it as standalone
> computer.
>
> I left the notebook on, and by chance I sit in front of the primary
> computer that I used at home, I inspected the browsing list just to
> know which are the shared resources of that computer and I saw by first
> time since I began with all this mess, the complete list merged!!!!
> office computers and home computers all together!!!!
>
> I checked the settings of the home computers, all of them have
> IsDomainMaster and MaintainServerList in FALSE. No lmhost file in any
> of those computers. The notebook with Windows 2000 SP4 was not touched
> in its configuration, it has IsDomainMaster in FALSE and
> MaintainServerList in Auto.
>
> I think that the miracle... or talking seriously, the solution... it
> was to connect to the home network a computer that previously was
> joined at the office network.
>
> I don't know why the browsing list crossing networks has this strange
> behaviour.
>
> Perhaps this expierence helps another one to avoid to suffer all this
> mess ;-)
>