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

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...@xxxxxxxxx> 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 ;-)


.

Relevant Pages

  • Re: WindowsXP and RISC OS computers
    ... >> - You can however ping Nixiyo from the windows XP machine, ... > workgroup: WORKGROUP ... > Name as M$ calls it, had been changed on the centrex machine. ... > Neither icon appears in My Network Places on the centrex. ...
    (comp.sys.acorn.networking)
  • Re: Simple File Sharing Wont Work
    ... longer access the WORKGROUP. ... I know I'm grasping at straws but how does the network work ... Permanently disable XP's built-in Internet Connection Firewall on ... > Windows XP Internet Connection Firewall ...
    (microsoft.public.windowsxp.network_web)
  • Workgroupt is not accessible
    ... The only network connection with the ... Even when it accesses the workgroup, ... >firewalls while troubleshooting. ... >Windows XP Internet Connection Firewall ...
    (microsoft.public.windowsxp.network_web)
  • Re: Crossover cable problem
    ... do you have Windows Firewall activated? ... My older pc> default value was 100 mbps, the newer pc was 10 mbps. ... >>>- I've run the network setup wizard numerous times. ... >>>I've found for my config is to specify a workgroup with no ISP ...
    (microsoft.public.windowsxp.network_web)
  • RE: Windows Networking with XP Pro
    ... (Windows XP Pro or Home with SP1 or SP2) ... The computer can ping other computers in the same workgroup. ... Click Start, click Control Panel, and then click Network and Internet ... able to update your profile and access the the partner newsgroups. ...
    (microsoft.public.windowsxp.help_and_support)