Windows NETworking's NOT Working. DC Loses Its Master Browser Role

Gentlemen,

A top of my head just got blown off. Everything works except for Windows
Networking.
I have 2 servers in my domain. (no other machines in this test domain)
1. SERVER-DC
2. SERVER-FS

Problem: When I browse Microsoft Windows Network in Windows Explorer from
either SERVER-DC or SERVER-FS I get only the SERVER-FS machine in the tree.

How to do I get the SERVER-DC machine present in the list?

++Here's what I have for SERVER-DC++

Registry settings on SERVER-DC:
HKLM\SYSTEM\CurrentControlSet\Sevices\Browser\Para meter key has the
following parameters:
IsDomainMaster = TRUE
MaintainServerList = Yes

Other registry settings are intact.

Here's what I get if I run nbtstat -n on SERVER-DC
============START============
Local Area Connection:
Node IpAddress: [192.168.0.2] Scope Id: []
NetBIOS Local Name Table
Name Type Status
---------------------------------------------
SERVER-DC <00> UNIQUE Registered
ASTRA <00> GROUP Registered
ASTRA <1C> GROUP Registered
SERVER-DC <20> UNIQUE Registered
ASTRA <1B> UNIQUE Registered
ASTRA <1E> GROUP Registered
ASTRA <1D> UNIQUE Registered

..__MSBROWSE__.<01> GROUP Registered

==============END==================


What I get when run browstat

Retrieving master browser
======BEGIN=========
C:\Documents and Settings\Administrator>browstat getmaster
\Device\NetBT_Tcpip_{
810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra
Master Browser: SERVER-DC
======END=========

Retrieving PDC

=========BEGIN===========
C:\Documents and Settings\Administrator>browstat getpdc
\Device\NetBT_Tcpip_{810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra
PDC: SERVER-DC
=========END===========

Retrieving WFW

========BEGIN===========
C:\Documents and Settings\Administrator>browstat listwfw astra
Calling NetServerEnum to enumerate WFW servers.
0 WFW servers returned. 0 total.
There are WFW servers with an active Browser.
========END===========

Viewing the servers

========BEGIN===========
C:\Documents and Settings\Administrator.ASTRA>browstat view
\Device\NetBT_Tcpip_
{810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra

Remoting NetServerEnum to \\SERVER-DC on transport
\Device\NetBT_Tcpip_{810BAD07-9C0F-4187-B822-A2A3AC64C4BE} with flags ffffffff
1 entries returned. 1 total. 16 milliseconds
========END===========

Notice, there's no SERVER-DC in the list!!!

++Here's what I have for SERVER-FS++

Registry settings on SERVER-DC:
HKLM\SYSTEM\CurrentControlSet\Sevices\Browser\Para meter key has the
following parameters:
IsDomainMaster = FALSE
MaintainServerList = No

Other registry settings are intact.

Here's what I get if I run nbtstat -n on SERVER-FS
============START============
C:\Documents and Settings\Administrator.ASTRA>nbtstat
-n>nbtstat-server-fs.txt
Local Area Connection:
Node IpAddress: [192.168.0.3] Scope Id: []
NetBIOS Local Name Table
Name Type Status
---------------------------------------------
SERVER-FS <00> UNIQUE Registered
ASTRA <00> GROUP Registered
SERVER-FS <20> UNIQUE Registered
==============END==================


What I get when run browstat

Retrieving master browser
======BEGIN=========
C:\Documents and Settings\Administrator.ASTRA>browstat getmaster
\Device\NetBT_T
cpip_{B60C3001-AE04-4E2F-8EBC-BFCF592256EF} astra
Master Browser: SERVER-DC
======END=========

Retrieving PDC

=========BEGIN===========
C:\Documents and Settings\Administrator.ASTRA>browstat getpdc
\Device\NetBT_Tcpi
p_{B60C3001-AE04-4E2F-8EBC-BFCF592256EF} astra
PDC: SERVER-DC
=========END===========

Retrieving WFW

========BEGIN===========
C:\Documents and Settings\Administrator.ASTRA>browstat listwfw astra
Calling NetServerEnum to enumerate WFW servers.
0 WFW servers returned. 0 total.
There are WFW servers with an active Browser.
========END===========

Viewing the servers

========BEGIN===========
C:\Documents and Settings\Administrator.ASTRA>browstat view
\Device\NetBT_Tcpip_
{B60C3001-AE04-4E2F-8EBC-BFCF592256EF} astra
Remoting NetServerEnum to \\SERVER-DC on transport
\Device\NetBT_Tcpip_{B60C3001-AE04-4E2F-8EBC-BFCF592256EF} with flags ffffffff
1 entries returned. 1 total. 15 milliseconds

\\SERVER-FS NT 05.02 (W,S,NT,SS,DFS)
========END===========

Notice, there's no SERVER-DC in the list!!!



Summarizing:

1. There's only difference in nbtstat -n output between SERVER-DC and
SERVER-FS. The output seems to be OK. Isn't it?
2. There's NO difference in any browstat output (except for the GUIDs in
transports which for sure are unique for SERVER-DC and SERVER-FS)

Hence, I wonder -what could be the problem???

Additional info
1. Both servers are running Windows Server 2003 R2 SP2 X64
2. Both servers are running in a child partition on Hyper-V server (that's
both are virtual machines)
3. If I set the
IsDomainMaster = FALSE
MaintainServerList = Yes

on SERVER-DC

and

IsDomainMaster = FALSE
MaintainServerList = Auto

on SERVER-FS

like it is so by default - the SERVER-FS just takes the master role from
SERVER-DC!!! However, the PDC role remains to be hold by SERVER-DC. In this
case, I can't get any browstat from SERVER-DC neither can I browse Microsoft
Windows Network in Windows Explorer from either SERVER-DC
4. I had TWO NETWORK INTERFACES installed on SERVER-DC. But then I removed
the second (from another subnet) from it. So now thers's only a single
network interface present on the SERVER-DC
5. SERVER-FS has a second network interface. However, this interface is
disabled.
6. SERVER-DC has WINS service installed and running.


Could somebody please help me find out what's going on and what's more - how
to get it fixed?
All my hopes are in your help.

Thank you in advance. In MSFT we [try] trust.

"Exotic Hadron" <(E-Mail Removed)> wrote in message
news:E44E5A34-B9A5-4F39-91F5-(E-Mail Removed)...
> Gentlemen,
>
> A top of my head just got blown off. Everything works except for Windows
> Networking.
> I have 2 servers in my domain. (no other machines in this test domain)
> 1. SERVER-DC
> 2. SERVER-FS
>
> Problem: When I browse Microsoft Windows Network in Windows Explorer from
> either SERVER-DC or SERVER-FS I get only the SERVER-FS machine in the
> tree.
>
> How to do I get the SERVER-DC machine present in the list?
>
> ++Here's what I have for SERVER-DC++
>
> Registry settings on SERVER-DC:
> HKLM\SYSTEM\CurrentControlSet\Sevices\Browser\Para meter key has the
> following parameters:
> IsDomainMaster = TRUE
> MaintainServerList = Yes
>
> Other registry settings are intact.
>
> Here's what I get if I run nbtstat -n on SERVER-DC
> ============START============
> Local Area Connection:
> Node IpAddress: [192.168.0.2] Scope Id: []
> NetBIOS Local Name Table
> Name Type Status
> ---------------------------------------------
> SERVER-DC <00> UNIQUE Registered
> ASTRA <00> GROUP Registered
> ASTRA <1C> GROUP Registered
> SERVER-DC <20> UNIQUE Registered
> ASTRA <1B> UNIQUE Registered
> ASTRA <1E> GROUP Registered
> ASTRA <1D> UNIQUE Registered
>
> ..__MSBROWSE__.<01> GROUP Registered
>
> ==============END==================
>
>
> What I get when run browstat
>
> Retrieving master browser
> ======BEGIN=========
> C:\Documents and Settings\Administrator>browstat getmaster
> \Device\NetBT_Tcpip_{
> 810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra
> Master Browser: SERVER-DC
> ======END=========
>
> Retrieving PDC
>
> =========BEGIN===========
> C:\Documents and Settings\Administrator>browstat getpdc
> \Device\NetBT_Tcpip_{810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra
> PDC: SERVER-DC
> =========END===========
>
> Retrieving WFW
>
> ========BEGIN===========
> C:\Documents and Settings\Administrator>browstat listwfw astra
> Calling NetServerEnum to enumerate WFW servers.
> 0 WFW servers returned. 0 total.
> There are WFW servers with an active Browser.
> ========END===========
>
> Viewing the servers
>
> ========BEGIN===========
> C:\Documents and Settings\Administrator.ASTRA>browstat view
> \Device\NetBT_Tcpip_
> {810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra
>
> Remoting NetServerEnum to \\SERVER-DC on transport
> \Device\NetBT_Tcpip_{810BAD07-9C0F-4187-B822-A2A3AC64C4BE} with flags
> ffffffff
> 1 entries returned. 1 total. 16 milliseconds
> ========END===========
>
> Notice, there's no SERVER-DC in the list!!!
>
> ++Here's what I have for SERVER-FS++
>
> Registry settings on SERVER-DC:
> HKLM\SYSTEM\CurrentControlSet\Sevices\Browser\Para meter key has the
> following parameters:
> IsDomainMaster = FALSE
> MaintainServerList = No
>
> Other registry settings are intact.
>
> Here's what I get if I run nbtstat -n on SERVER-FS
> ============START============
> C:\Documents and Settings\Administrator.ASTRA>nbtstat
> -n>nbtstat-server-fs.txt
> Local Area Connection:
> Node IpAddress: [192.168.0.3] Scope Id: []
> NetBIOS Local Name Table
> Name Type Status
> ---------------------------------------------
> SERVER-FS <00> UNIQUE Registered
> ASTRA <00> GROUP Registered
> SERVER-FS <20> UNIQUE Registered
> ==============END==================
>
>
> What I get when run browstat
>
> Retrieving master browser
> ======BEGIN=========
> C:\Documents and Settings\Administrator.ASTRA>browstat getmaster
> \Device\NetBT_T
> cpip_{B60C3001-AE04-4E2F-8EBC-BFCF592256EF} astra
> Master Browser: SERVER-DC
> ======END=========
>
> Retrieving PDC
>
> =========BEGIN===========
> C:\Documents and Settings\Administrator.ASTRA>browstat getpdc
> \Device\NetBT_Tcpi
> p_{B60C3001-AE04-4E2F-8EBC-BFCF592256EF} astra
> PDC: SERVER-DC
> =========END===========
>
> Retrieving WFW
>
> ========BEGIN===========
> C:\Documents and Settings\Administrator.ASTRA>browstat listwfw astra
> Calling NetServerEnum to enumerate WFW servers.
> 0 WFW servers returned. 0 total.
> There are WFW servers with an active Browser.
> ========END===========
>
> Viewing the servers
>
> ========BEGIN===========
> C:\Documents and Settings\Administrator.ASTRA>browstat view
> \Device\NetBT_Tcpip_
> {B60C3001-AE04-4E2F-8EBC-BFCF592256EF} astra
> Remoting NetServerEnum to \\SERVER-DC on transport
> \Device\NetBT_Tcpip_{B60C3001-AE04-4E2F-8EBC-BFCF592256EF} with flags
> ffffffff
> 1 entries returned. 1 total. 15 milliseconds
>
> \\SERVER-FS NT 05.02 (W,S,NT,SS,DFS)
> ========END===========
>
> Notice, there's no SERVER-DC in the list!!!
>
>
>
> Summarizing:
>
> 1. There's only difference in nbtstat -n output between SERVER-DC and
> SERVER-FS. The output seems to be OK. Isn't it?
> 2. There's NO difference in any browstat output (except for the GUIDs in
> transports which for sure are unique for SERVER-DC and SERVER-FS)
>
> Hence, I wonder -what could be the problem???
>
> Additional info
> 1. Both servers are running Windows Server 2003 R2 SP2 X64
> 2. Both servers are running in a child partition on Hyper-V server (that's
> both are virtual machines)
> 3. If I set the
> IsDomainMaster = FALSE
> MaintainServerList = Yes
>
> on SERVER-DC
>
> and
>
> IsDomainMaster = FALSE
> MaintainServerList = Auto
>
> on SERVER-FS
>
> like it is so by default - the SERVER-FS just takes the master role from
> SERVER-DC!!! However, the PDC role remains to be hold by SERVER-DC. In
> this
> case, I can't get any browstat from SERVER-DC neither can I browse
> Microsoft
> Windows Network in Windows Explorer from either SERVER-DC
> 4. I had TWO NETWORK INTERFACES installed on SERVER-DC. But then I
> removed
> the second (from another subnet) from it. So now thers's only a single
> network interface present on the SERVER-DC
> 5. SERVER-FS has a second network interface. However, this interface is
> disabled.
> 6. SERVER-DC has WINS service installed and running.
>
>
> Could somebody please help me find out what's going on and what's more -
> how
> to get it fixed?
> All my hopes are in your help.
>
> Thank you in advance. In MSFT we [try] trust.
>

Make sure that there are no entries left behind in WINS for the second
NIC you had in the DC. A multihomed DC will give you this sort of problem.
Disabling or removing the NIC will solve the problem but WINS might still
have an entry for it.

Here is the reason why a second NIC in the DC causes this problem. If a
machine tries to get a browse list using the "wrong" IP address for the
master browser, it fails (because the browser is linked to a particular NIC,
as you see in the browstat listing). When the request fails, the machine
forces a browser election because browsing has failed. It forces an election
by declaring that it is the browse master (because it cannot find an active
browse master on the network).

On both computers, if you run net view, do you receive the same results?

--
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
"Exotic Hadron" <(E-Mail Removed)> wrote in message
news:E44E5A34-B9A5-4F39-91F5-(E-Mail Removed)...
> Gentlemen,
>
> A top of my head just got blown off. Everything works except for Windows
> Networking.
> I have 2 servers in my domain. (no other machines in this test domain)
> 1. SERVER-DC
> 2. SERVER-FS
>
> Problem: When I browse Microsoft Windows Network in Windows Explorer from
> either SERVER-DC or SERVER-FS I get only the SERVER-FS machine in the
> tree.
>
> How to do I get the SERVER-DC machine present in the list?
>
> ++Here's what I have for SERVER-DC++
>
> Registry settings on SERVER-DC:
> HKLM\SYSTEM\CurrentControlSet\Sevices\Browser\Para meter key has the
> following parameters:
> IsDomainMaster = TRUE
> MaintainServerList = Yes
>
> Other registry settings are intact.
>
> Here's what I get if I run nbtstat -n on SERVER-DC
> ============START============
> Local Area Connection:
> Node IpAddress: [192.168.0.2] Scope Id: []
> NetBIOS Local Name Table
> Name Type Status
> ---------------------------------------------
> SERVER-DC <00> UNIQUE Registered
> ASTRA <00> GROUP Registered
> ASTRA <1C> GROUP Registered
> SERVER-DC <20> UNIQUE Registered
> ASTRA <1B> UNIQUE Registered
> ASTRA <1E> GROUP Registered
> ASTRA <1D> UNIQUE Registered
>
> ..__MSBROWSE__.<01> GROUP Registered
>
> ==============END==================
>
>
> What I get when run browstat
>
> Retrieving master browser
> ======BEGIN=========
> C:\Documents and Settings\Administrator>browstat getmaster
> \Device\NetBT_Tcpip_{
> 810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra
> Master Browser: SERVER-DC
> ======END=========
>
> Retrieving PDC
>
> =========BEGIN===========
> C:\Documents and Settings\Administrator>browstat getpdc
> \Device\NetBT_Tcpip_{810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra
> PDC: SERVER-DC
> =========END===========
>
> Retrieving WFW
>
> ========BEGIN===========
> C:\Documents and Settings\Administrator>browstat listwfw astra
> Calling NetServerEnum to enumerate WFW servers.
> 0 WFW servers returned. 0 total.
> There are WFW servers with an active Browser.
> ========END===========
>
> Viewing the servers
>
> ========BEGIN===========
> C:\Documents and Settings\Administrator.ASTRA>browstat view
> \Device\NetBT_Tcpip_
> {810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra
>
> Remoting NetServerEnum to \\SERVER-DC on transport
> \Device\NetBT_Tcpip_{810BAD07-9C0F-4187-B822-A2A3AC64C4BE} with flags
> ffffffff
> 1 entries returned. 1 total. 16 milliseconds
> ========END===========
>
> Notice, there's no SERVER-DC in the list!!!
>
> ++Here's what I have for SERVER-FS++
>
> Registry settings on SERVER-DC:
> HKLM\SYSTEM\CurrentControlSet\Sevices\Browser\Para meter key has the
> following parameters:
> IsDomainMaster = FALSE
> MaintainServerList = No
>
> Other registry settings are intact.
>
> Here's what I get if I run nbtstat -n on SERVER-FS
> ============START============
> C:\Documents and Settings\Administrator.ASTRA>nbtstat
> -n>nbtstat-server-fs.txt
> Local Area Connection:
> Node IpAddress: [192.168.0.3] Scope Id: []
> NetBIOS Local Name Table
> Name Type Status
> ---------------------------------------------
> SERVER-FS <00> UNIQUE Registered
> ASTRA <00> GROUP Registered
> SERVER-FS <20> UNIQUE Registered
> ==============END==================
>
>
> What I get when run browstat
>
> Retrieving master browser
> ======BEGIN=========
> C:\Documents and Settings\Administrator.ASTRA>browstat getmaster
> \Device\NetBT_T
> cpip_{B60C3001-AE04-4E2F-8EBC-BFCF592256EF} astra
> Master Browser: SERVER-DC
> ======END=========
>
> Retrieving PDC
>
> =========BEGIN===========
> C:\Documents and Settings\Administrator.ASTRA>browstat getpdc
> \Device\NetBT_Tcpi
> p_{B60C3001-AE04-4E2F-8EBC-BFCF592256EF} astra
> PDC: SERVER-DC
> =========END===========
>
> Retrieving WFW
>
> ========BEGIN===========
> C:\Documents and Settings\Administrator.ASTRA>browstat listwfw astra
> Calling NetServerEnum to enumerate WFW servers.
> 0 WFW servers returned. 0 total.
> There are WFW servers with an active Browser.
> ========END===========
>
> Viewing the servers
>
> ========BEGIN===========
> C:\Documents and Settings\Administrator.ASTRA>browstat view
> \Device\NetBT_Tcpip_
> {B60C3001-AE04-4E2F-8EBC-BFCF592256EF} astra
> Remoting NetServerEnum to \\SERVER-DC on transport
> \Device\NetBT_Tcpip_{B60C3001-AE04-4E2F-8EBC-BFCF592256EF} with flags
> ffffffff
> 1 entries returned. 1 total. 15 milliseconds
>
> \\SERVER-FS NT 05.02 (W,S,NT,SS,DFS)
> ========END===========
>
> Notice, there's no SERVER-DC in the list!!!
>
>
>
> Summarizing:
>
> 1. There's only difference in nbtstat -n output between SERVER-DC and
> SERVER-FS. The output seems to be OK. Isn't it?
> 2. There's NO difference in any browstat output (except for the GUIDs in
> transports which for sure are unique for SERVER-DC and SERVER-FS)
>
> Hence, I wonder -what could be the problem???
>
> Additional info
> 1. Both servers are running Windows Server 2003 R2 SP2 X64
> 2. Both servers are running in a child partition on Hyper-V server (that's
> both are virtual machines)
> 3. If I set the
> IsDomainMaster = FALSE
> MaintainServerList = Yes
>
> on SERVER-DC
>
> and
>
> IsDomainMaster = FALSE
> MaintainServerList = Auto
>
> on SERVER-FS
>
> like it is so by default - the SERVER-FS just takes the master role from
> SERVER-DC!!! However, the PDC role remains to be hold by SERVER-DC. In
> this
> case, I can't get any browstat from SERVER-DC neither can I browse
> Microsoft
> Windows Network in Windows Explorer from either SERVER-DC
> 4. I had TWO NETWORK INTERFACES installed on SERVER-DC. But then I
> removed
> the second (from another subnet) from it. So now thers's only a single
> network interface present on the SERVER-DC
> 5. SERVER-FS has a second network interface. However, this interface is
> disabled.
> 6. SERVER-DC has WINS service installed and running.
>
>
> Could somebody please help me find out what's going on and what's more -
> how
> to get it fixed?
> All my hopes are in your help.
>
> Thank you in advance. In MSFT we [try] trust.
>

Thanks Bill for answering my question,
>Make sure that there are no entries left behind in WINS for the second
>NIC you had in the DC. A multihomed DC will give you this sort of problem.
>Disabling or removing the NIC will solve the problem but WINS might still
>have an entry for it.
The thing is I installed WINS service ONLY after I faced the problem. On
that time I had the second interface disabled and REMOVED from the virtual
machine SERVER-DC.
Still the records in registry for the removed interface are present in
registry here
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}]
Should I clean off everything that corresponds to the GUID of removed
adapter from the registry?
(The GUID for the current interface can be retrieved by running browstat
dumpnet)

Here's what I have in my WINS DB

Record Name Type IP Address State Static Owner Version Expiration
--__MSBROWSE__- [01h] Other 192.168.0.2 Active 192.168.0.2 1F6 9/15/2008
11:10:00 AM
ASTRA [1Bh] Domain Master
Browser 192.168.0.2 Active 192.168.0.2 1F5 9/16/2008 1:08:01 AM
ASTRA [00h] Workgroup 192.168.0.2 Active 192.168.0.2 1F9 9/16/2008 1:04:02 AM
ASTRA [1Ch] Domain Controller 192.168.0.2 Active 192.168.0.2 1F8 9/16/2008
1:02:02 AM
ASTRA [1Eh] Normal Group Name 192.168.0.2 Active 192.168.0.2 1F7 9/15/2008
11:14:00 AM
SERVER-FS [00h] WorkStation 192.168.0.3 Active x 192.168.0.2 1FB Infinite
SERVER-FS [03h] Messenger 192.168.0.3 Active x 192.168.0.2 1FC Infinite
SERVER-FS [20h] File Server 192.168.0.3 Active x 192.168.0.2 1FD Infinite
SERVER-DC [20h] File Server 192.168.0.2 Active 192.168.0.2 1FE 9/16/2008
1:06:01 AM

What's confusing here is that there's only one entry for the domain
controller (master browser) SERVER-DC. On the other hand, that's what the
ASTRA records are for isn't it? (ASTRA is my domain name).
Is the table OK or wrong?

>When the request fails, the machine forces a browser election because browsing has failed. It forces an election
>by declaring that it is the browse master (because it cannot find an active browse master on the network).

Thanks! But WHY does the machine (SERVER-FS machine in my case) try "to get
a browse list using the "wrong" IP address for the
master browser"??? Why does it use the wrong IP if I didn't have a WINS in
my network when I had a multihomed system? (I installed WINS only after I
fixed the problem and transferred the master role back to the domain
controller SERVER-DC)

Here’s the irony! Isn't it my day today? http://www.google.com/logos/lhc.gif
Or am I not the Exotic Hadron after all?!?

Thank you for answering, Robert,

>On both computers, if you run net view, do you receive the same results?

YES. On both I get the same result as Microsoft Windows Network shows (since
they both call the same Networking API, am I right?)
Server Name Remark

-------------------------------------------------------------------------------
\\SERVER-FS

The command completed successfully.

Could you please look at the WINS table that I posted replying to Bill's post?

Oh my…
How do I not to recall Bob Marley here?

No sun will shine in my day today; (no sun will shine)
The high yellow moon won't come out to play:
(that high yellow moon won't come out to play)
I said (darkness) darkness has covered my light,
(and the stage) And has changed my day into night, yeah.
Where is the love to be found? (oo-ooh-ooh)
Won't someone tell me?
'Cause my (sweet life) life must be somewhere to be found -
(must be somewhere for me)
Instead of concrete jungle (jungle!)
Where the living is harder (concrete, jungle!).


What do I do now? Any clue? In my case it probably would be OK to just
revert to the last working snapshot. But… Still I don't want to re-install
all the software that was installed after the snapshot was made.

It's seriously confusing... this NetBIOS et al. What if somebody will place
the second interface again? Everybody has the right for a mistake.

Can you see server-dc if you do net share on the server-dc? Also post back
the result of ipconfig /all may help.

--
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
"Exotic Hadron" <(E-Mail Removed)> wrote in message
news:21747AA1-B724-421C-BBF4-(E-Mail Removed)...
> Thank you for answering, Robert,
>
>>On both computers, if you run net view, do you receive the same results?
>
> YES. On both I get the same result as Microsoft Windows Network shows
> (since
> they both call the same Networking API, am I right?)
> Server Name Remark
>
> -------------------------------------------------------------------------------
> \\SERVER-FS
>
> The command completed successfully.
>
> Could you please look at the WINS table that I posted replying to Bill's
> post?
>
> Oh my…
> How do I not to recall Bob Marley here?
>
> No sun will shine in my day today; (no sun will shine)
> The high yellow moon won't come out to play:
> (that high yellow moon won't come out to play)
> I said (darkness) darkness has covered my light,
> (and the stage) And has changed my day into night, yeah.
> Where is the love to be found? (oo-ooh-ooh)
> Won't someone tell me?
> 'Cause my (sweet life) life must be somewhere to be found -
> (must be somewhere for me)
> Instead of concrete jungle (jungle!)
> Where the living is harder (concrete, jungle!).
>
>
> What do I do now? Any clue? In my case it probably would be OK to just
> revert to the last working snapshot. But… Still I don't want to re-install
> all the software that was installed after the snapshot was made.
>
> It's seriously confusing... this NetBIOS et al. What if somebody will
> place
> the second interface again? Everybody has the right for a mistake.
>

It may be important: I changed the registry settings and set the following

Registry settings on SERVER-FS:
HKLM\SYSTEM\CurrentControlSet\Sevices\Browser\Para meter key has the
following parameters:
IsDomainMaster = FALSE
MaintainServerList = Auto

Registry settings on SERVER-DC are the same

Registry settings on SERVER-FS:
HKLM\SYSTEM\CurrentControlSet\Sevices\Browser\Para meter key has the
following parameters:
IsDomainMaster = TRUE
MaintainServerList = YES
Here's what I get when I run net share command on the Server-DC server

Share name Resource Remark
-------------------------------------------------------------------------------
C$ C:\ Default share

E$ E:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

CD Drive (D) D:\ Caching disabled
NETLOGON C:\WINDOWS\sysvol\sysvol\astra.local\SCRIPTS
Logon server share

SYSVOL C:\WINDOWS\sysvol\sysvol Logon server share

The command completed successfully.

Everything seems to be OK.

I can also do net use in both directions. When I run net use \\server-fs on
server-dc I get following:

The command completed successfully.

The same return I get when I run net use \\server-dc on server-fs!

That is connections via IPC$ are established successfully, right?

Here's the ipconfig /all on the server-dc machine.
============BEGIN===================
Windows IP Configuration

Host Name . . . . . . . . . . . . : server-dc
Primary Dns Suffix . . . . . . . : astra.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : astra.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : astra.local
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network
Adapter
Physical Address. . . . . . . . . : 00-15-5D-D9-18-0F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.2
Primary WINS Server . . . . . . . : 192.168.0.2
================END===================

What's more:

1. If I shut the server-fs down, I don't get any computers present in the
Windows Networking at all. When I expand the Microsoft Windows Network tree I
only see the root node presenting the name of my domain (Astra). And there
isn't no computers under this node!

Correspondingly, when I run net view on the server-dc with server-fs shut
down I get:
=============BEGIN===================
There are no entries in the list.
==============END====================

When I run browstat view on the server-dc with server-fs shut down I get:
========BEGIN===========
C:\Documents and Settings\Administrator.ASTRA>browstat view
\Device\NetBT_Tcpip_
{810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra

Remoting NetServerEnum to \\SERVER-DC on transport
\Device\NetBT_Tcpip_{810BAD07-9C0F-4187-B822-A2A3AC64C4BE} with flags ffffffff
0 entries returned. 0 total. 0 milliseconds
========END===========

However, querying for master and pdc gets the same results as when I have
the server-fs running:

Retrieving master browser
======BEGIN=========
C:\Documents and Settings\Administrator>browstat getmaster
\Device\NetBT_Tcpip_{
810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra
Master Browser: SERVER-DC
======END=========

Retrieving PDC

=========BEGIN===========
C:\Documents and Settings\Administrator>browstat getpdc
\Device\NetBT_Tcpip_{810BAD07-9C0F-4187-B822-A2A3AC64C4BE} astra
PDC: SERVER-DC
=========END===========

This time I have the following WINS table

===============BEGIN====================
Record Name Type IP Address State Static Owner Version Expiration
--__MSBROWSE__- [01h] Other 192.168.0.2 Active 192.168.0.2 222 9/16/2008
10:23:43 AM
ASTRA [1Bh] Domain Master
Browser 192.168.0.2 Active 192.168.0.2 21C 9/16/2008 10:23:28 AM
ASTRA [00h] Workgroup 192.168.0.2 Active 192.168.0.2 225 9/16/2008 10:23:28
AM
ASTRA [1Ch] Domain Controller 192.168.0.2 Active 192.168.0.2 21D 9/16/2008
10:23:28 AM
ASTRA [1Eh] Normal Group Name 192.168.0.2 Active 192.168.0.2 221 9/16/2008
10:23:28 AM
SERVER-FS [00h] WorkStation 192.168.0.3 Released 192.168.0.2 223 9/14/2008
10:07:50 AM
SERVER-FS [20h] File Server 192.168.0.3 Released 192.168.0.2 224 9/14/2008
10:07:48 AM
SERVER-DC [00h] WorkStation 192.168.0.2 Active 192.168.0.2 220 9/16/2008
10:23:28 AM
SERVER-DC [20h] File Server 192.168.0.2 Active 192.168.0.2 21F 9/16/2008
10:23:28 AM

===============END====================

Is it a bug in a protocol or whatever?

"Robert L. (MS-MVP)" wrote:

> Can you see server-dc if you do net share on the server-dc? Also post back
> the result of ipconfig /all may help.
>
> --
> 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
> "Exotic Hadron" <(E-Mail Removed)> wrote in message
> news:21747AA1-B724-421C-BBF4-(E-Mail Removed)...
> > Thank you for answering, Robert,
> >
> >>On both computers, if you run net view, do you receive the same results?
> >
> > YES. On both I get the same result as Microsoft Windows Network shows
> > (since
> > they both call the same Networking API, am I right?)
> > Server Name Remark
> >
> > -------------------------------------------------------------------------------
> > \\SERVER-FS
> >
> > The command completed successfully.
> >
> > Could you please look at the WINS table that I posted replying to Bill's
> > post?
> >
> > Oh my…
> > How do I not to recall Bob Marley here?
> >
> > No sun will shine in my day today; (no sun will shine)
> > The high yellow moon won't come out to play:
> > (that high yellow moon won't come out to play)
> > I said (darkness) darkness has covered my light,
> > (and the stage) And has changed my day into night, yeah.
> > Where is the love to be found? (oo-ooh-ooh)
> > Won't someone tell me?
> > 'Cause my (sweet life) life must be somewhere to be found -
> > (must be somewhere for me)
> > Instead of concrete jungle (jungle!)
> > Where the living is harder (concrete, jungle!).
> >
> >
> > What do I do now? Any clue? In my case it probably would be OK to just
> > revert to the last working snapshot. But… Still I don't want to re-install
> > all the software that was installed after the snapshot was made.
> >
> > It's seriously confusing... this NetBIOS et al. What if somebody will
> > place
> > the second interface again? Everybody has the right for a mistake.
> >
>
>

Okay, I have figured out the root of the problem.

What I did is I launched the Wireshark on SERVER-DC (my domain controller
and master browser - IP address 192.168.0.2) and started listening on its
single interface.

That's what I got.
1. When I had the SERVER-FS turned off, there was NO PACKETS coming from
SERVER-DC. So for some reason, server was not announcing about its presence,
nor had I any broadcast packets from the interface. OK, maybe it's how the
thing should be. However, I thought that network interface always broadcasts
itself to the outside. Whether I am wrong or not this all is OK compared to
what I saw after I had the SERVER-FS booted up.

2. Once I booted the SERVER-FS I started receiving packets from SERVER-FS.
Here's the WireShark capture filtered by BROWSE protocol.

================BEGIN===================
No. Time Source Destination Protocol Info
1 0.000000 192.168.0.1 192.168.0.255 BROWSER
Host Announcement HYPER-V-HOST, Workstation, Server, Dialin Server, NT
Workstation, NT Server
107 32.682873 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
108 32.693172 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
<CUTOFF>
750 209.020059 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
751 225.035996 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
752 225.435656 192.168.0.2 192.168.3.255 BROWSER
Local Master Announcement SERVER-DC, Workstation, Server, Domain Controller,
Time Source, NT Workstation, Master Browser, Unknown server type:23
753 241.094899 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
754 257.154195 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
<CUTOFF>
760 353.505098 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
761 369.540250 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
764 380.807455 192.168.0.2 192.168.3.255 BROWSER
Domain/Workgroup Announcement ASTRA, Domain Controller, NT Workstation,
Domain Enum
765 385.590754 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
766 401.640137 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
<CUTOFF>
827 706.721209 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
828 722.769426 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
829 723.109732 192.168.0.1 192.168.0.255 BROWSER
Host Announcement HYPER-V-HOST, Workstation, Server, Dialin Server, NT
Workstation, NT Server
830 738.830828 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
831 754.896764 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23
================END=====================

OK, let's start analyzing:
1. Since I run it in Hyper-V, the first announcement came from my primary
partition (that's from the host machine where all my virtual machines are
running on). It's the HYPER-V-HOST machine running on interface with IP
address 192.168.0.1 which serves as a gateway between the host machine and
the virtual machines.
This gateway interface has a subnet mask of 192.168.0.0/24 (that's
255.255.255.0)
Here's the entry that corresponds to the BROWSE announcements that came from
the HYPER-V-HOST machine:
1 0.000000 192.168.0.1 192.168.0.255 BROWSER Host
Announcement HYPER-V-HOST, Workstation, Server, Dialin Server, NT
Workstation, NT Server
2. Then we see a series of BROWSE announcements that came from the SERVER-FS
server:

107 32.682873 192.168.0.3 192.168.0.255 BROWSER Host
Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
Unknown server type:23

I cut off the excess repeating lines.

3. All of a sudden in the line 753 we see the announcement that goes out
from the domain controller server - the SERVER-DC machine with IP address of
192.168.0.2

752 225.435656 192.168.0.2 192.168.3.255 BROWSER
Local Master Announcement SERVER-DC, Workstation, Server, Domain Controller,
Time Source, NT Workstation, Master Browser, Unknown server type:23

===SOURCE OF THE PROBLEM===

Now look a the destination! It goes to 192.168.0.0/22 network (that is the
network 192.168.0.0 with subnet mask of 255.255.252.0). Why does it do so?
The answer is - the interface on the SERVER-DC has the subnet mask of
255.255.252.0! For some reason I made it wider than the gateway… What else,
the subnet mask that I configured my DHCP server to give to the clients (and
hence to the SERVER-FS server) was also narrower . I configured the DHCP to
give 255.255.255.0 mask . Oh, silly me…

===SOLUTION FOR THE PROBLEM===

I changed the network subnet mask on the interface on SERVER-DC to
192.168.0.0/24 (255.255.255.0) and this solved all of my problems. The
SERVER-DC machine immediately started broadcasting announcements to
192.168.0.255 and I got the SERVER-DC appeared in the Microsoft Windows
Network tree!

===Now here's the question===

What if I wanted to widen my virtual network. What should I have done then
to make other? Should I have just widen the subnet mask on the gateway
interface and set it to 255.255.252.0?
Or should I have just configured the DHCP server to give the wider mask to
my clients?
If so, how do I configure the wide mask 192.168.0.0/22 but narrow the scope
of addresses that should be given to the clients?
When we create a scope on DHCP server we have to specify the two things:

1. The scope of addresses to be distributed by DHCP server
2. Subnet mask

I don’t get what's the need to specify the scope if I can't specify it
narrower than the address range specified by mask.
So if I specified the mask of 192.168.0.0/22 should I have specified the END
IP ADDRESS as 192.168.3.254? That is should I have specified the upper border
of the network scope specified by the mask as the END IP ADDRESS?

Second, I thought that broadcasting goes across all the network until it
faces a gateway or router. So having the SERVER-DC interface set to
192.168.0.0/22 why doesn't it reach the computers in 192.168.0.0/24? What
should I have done to get the announcements from the SERVER-DC to be
broadcasted for all the range of 1022 hosts and 4 networks that fall into
the 192.168.0.0/22 range?

(Hope somebody will finally teach me the basics of subnetting/networking).
Hoping for your help.

Thank you for helping me!

Thank makes sense. Thank you for the update.

For the rest question, why do you just make 172.16.0.0/16? Basically, all
devices should be in the same subnet.

--
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
"Exotic Hadron" <(E-Mail Removed)> wrote in message
news:E25D7536-DDCE-4A0F-946E-(E-Mail Removed)...
> Okay, I have figured out the root of the problem.
>
> What I did is I launched the Wireshark on SERVER-DC (my domain controller
> and master browser - IP address 192.168.0.2) and started listening on its
> single interface.
>
> That's what I got.
> 1. When I had the SERVER-FS turned off, there was NO PACKETS coming from
> SERVER-DC. So for some reason, server was not announcing about its
> presence,
> nor had I any broadcast packets from the interface. OK, maybe it's how the
> thing should be. However, I thought that network interface always
> broadcasts
> itself to the outside. Whether I am wrong or not this all is OK compared
> to
> what I saw after I had the SERVER-FS booted up.
>
> 2. Once I booted the SERVER-FS I started receiving packets from SERVER-FS.
> Here's the WireShark capture filtered by BROWSE protocol.
>
> ================BEGIN===================
> No. Time Source Destination Protocol
> Info
> 1 0.000000 192.168.0.1 192.168.0.255 BROWSER
> Host Announcement HYPER-V-HOST, Workstation, Server, Dialin Server, NT
> Workstation, NT Server
> 107 32.682873 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> 108 32.693172 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> <CUTOFF>
> 750 209.020059 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> 751 225.035996 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> 752 225.435656 192.168.0.2 192.168.3.255 BROWSER
> Local Master Announcement SERVER-DC, Workstation, Server, Domain
> Controller,
> Time Source, NT Workstation, Master Browser, Unknown server type:23
> 753 241.094899 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> 754 257.154195 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> <CUTOFF>
> 760 353.505098 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> 761 369.540250 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> 764 380.807455 192.168.0.2 192.168.3.255 BROWSER
> Domain/Workgroup Announcement ASTRA, Domain Controller, NT Workstation,
> Domain Enum
> 765 385.590754 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> 766 401.640137 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> <CUTOFF>
> 827 706.721209 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> 828 722.769426 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> 829 723.109732 192.168.0.1 192.168.0.255 BROWSER
> Host Announcement HYPER-V-HOST, Workstation, Server, Dialin Server, NT
> Workstation, NT Server
> 830 738.830828 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> 831 754.896764 192.168.0.3 192.168.0.255 BROWSER
> Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
> ================END=====================
>
> OK, let's start analyzing:
> 1. Since I run it in Hyper-V, the first announcement came from my primary
> partition (that's from the host machine where all my virtual machines are
> running on). It's the HYPER-V-HOST machine running on interface with IP
> address 192.168.0.1 which serves as a gateway between the host machine and
> the virtual machines.
> This gateway interface has a subnet mask of 192.168.0.0/24 (that's
> 255.255.255.0)
> Here's the entry that corresponds to the BROWSE announcements that came
> from
> the HYPER-V-HOST machine:
> 1 0.000000 192.168.0.1 192.168.0.255 BROWSER Host
> Announcement HYPER-V-HOST, Workstation, Server, Dialin Server, NT
> Workstation, NT Server
> 2. Then we see a series of BROWSE announcements that came from the
> SERVER-FS
> server:
>
> 107 32.682873 192.168.0.3 192.168.0.255 BROWSER Host
> Announcement SERVER-FS, Workstation, Server, NT Workstation, NT Server,
> Unknown server type:23
>
> I cut off the excess repeating lines.
>
> 3. All of a sudden in the line 753 we see the announcement that goes out
> from the domain controller server - the SERVER-DC machine with IP address
> of
> 192.168.0.2
>
> 752 225.435656 192.168.0.2 192.168.3.255 BROWSER
> Local Master Announcement SERVER-DC, Workstation, Server, Domain
> Controller,
> Time Source, NT Workstation, Master Browser, Unknown server type:23
>
> ===SOURCE OF THE PROBLEM===
>
> Now look a the destination! It goes to 192.168.0.0/22 network (that is the
> network 192.168.0.0 with subnet mask of 255.255.252.0). Why does it do so?
> The answer is - the interface on the SERVER-DC has the subnet mask of
> 255.255.252.0! For some reason I made it wider than the gateway… What
> else,
> the subnet mask that I configured my DHCP server to give to the clients
> (and
> hence to the SERVER-FS server) was also narrower . I configured the DHCP
> to
> give 255.255.255.0 mask . Oh, silly me…
>
> ===SOLUTION FOR THE PROBLEM===
>
> I changed the network subnet mask on the interface on SERVER-DC to
> 192.168.0.0/24 (255.255.255.0) and this solved all of my problems. The
> SERVER-DC machine immediately started broadcasting announcements to
> 192.168.0.255 and I got the SERVER-DC appeared in the Microsoft Windows
> Network tree!
>
> ===Now here's the question===
>
> What if I wanted to widen my virtual network. What should I have done then
> to make other? Should I have just widen the subnet mask on the gateway
> interface and set it to 255.255.252.0?
> Or should I have just configured the DHCP server to give the wider mask to
> my clients?
> If so, how do I configure the wide mask 192.168.0.0/22 but narrow the
> scope
> of addresses that should be given to the clients?
> When we create a scope on DHCP server we have to specify the two things:
>
> 1. The scope of addresses to be distributed by DHCP server
> 2. Subnet mask
>
> I don’t get what's the need to specify the scope if I can't specify it
> narrower than the address range specified by mask.
> So if I specified the mask of 192.168.0.0/22 should I have specified the
> END
> IP ADDRESS as 192.168.3.254? That is should I have specified the upper
> border
> of the network scope specified by the mask as the END IP ADDRESS?
>
> Second, I thought that broadcasting goes across all the network until it
> faces a gateway or router. So having the SERVER-DC interface set to
> 192.168.0.0/22 why doesn't it reach the computers in 192.168.0.0/24? What
> should I have done to get the announcements from the SERVER-DC to be
> broadcasted for all the range of 1022 hosts and 4 networks that fall into
> the 192.168.0.0/22 range?
>
> (Hope somebody will finally teach me the basics of subnetting/networking).
> Hoping for your help.
>
> Thank you for helping me!

Sorry, Robert. What do you mean? Why _don't_ I just make 172.16.0.0/16? To
get the direct broadcasting to 172.16.255.255? Because here I used
192.168.0.0/22.
(I in fact use 172.16.0.0/16 on the gateway for the third network in my
other virtual environment...)

Second, when you say that "all devices should be in the same subnet", do you
mean that I had to set 192.168.0.0/22 on both my gateway (192.168.0.1) and
SERVER-FS (192.168.0.3) when I had the SERVER-DC interface set to IP address
192.168.0.2 with 255.255.252.0?

Thank you once again. Your recommendation to look at ipconfig turned to be
helpful!


"Robert L. (MS-MVP)" wrote:

> Thank makes sense. Thank you for the update.
>
> For the rest question, why do you just make 172.16.0.0/16? Basically, all
> devices should be in the same subnet.