prob:missing master browser from w2k3 server network (reposted)

Status: one Windows 2003 server as domain controller,WINS and DNS server
active, RRAS active to allow external user (NT4) to access internal
resources.
In the internal lan, there are w9x, 2k and XP client.
When an external user logon to RRAS port, nobody with win2k and XP are able
to see any pc inside the network browser.
With netbios browsing consolle, I get back an error "Impossible to find the
master browser"
This happen even if I remove the WINS address from the client ip
configuration, so I suppose it depends from DNS.
Anyway, if I type the server name as \\server\ I am able to browse the
server resource.
If I restart RRAS everything works fine, till an other user logon to rras
port.
I've tryed to set the dns to listen only to the internal lan address, but is
does not solve.
I know this problem is well known under windows 2000 server, and the Italian
Microsoft Support answered me that this problem is not existing under
windows 2003 server.
Does anyone have the same problem?
Any suggestion?
Thank you
Alessandro Belli

quoted from http://www.ChicagoTech.net
Name Resolution and Connectivity Issues on W2K Domain Controller with RRAS
and DNS Installed
Symptoms: You may experience some name resolution and connectivity issues if
the W2K domain controller is configured with RRAS and DNS. After a remote
client establishes a connection by using Dial-Up Networking, one or more of
the following symptoms may occur: 1. Internal clients may no longer be able
to browse the Web.
2. A "cannot find server or DNS" error occurs when using nslookup.
3. When using PING to ping the name of the server on an Internal client, it
returns any other address other than the IP address that is bound to the
server's internal adapter.
4. You cannot browse through the list of computers in Network Neighborhood
or My Network Places.
5. You may receive Event ID: 4319, Source: Netbt. Description: A duplicate
name has been detected on the tcp network. The IP address of the machine
that sent the message is in the data. Use NBTSTAT with a switch of N in a
command window to see which name is in a conflict state.
6. W2K/XP clients cannot map a network drive to the server. The client may
receive the following error message: No Logon Servers Available to Service
your Logon Request.
Resolutions: 1. Install the latest service pack.
2. Make sure the clients have correct DNS and WINS settings.
3. Disable NetBIOS for all RRAS connections.
4. Double-click on the entries for the servername[00h], and servername[20h]
to verify that there is only 1 IP address on them.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Alessandro Belli" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Status: one Windows 2003 server as domain controller,WINS and DNS server
> active, RRAS active to allow external user (NT4) to access internal
> resources.
> In the internal lan, there are w9x, 2k and XP client.
> When an external user logon to RRAS port, nobody with win2k and XP are
able
> to see any pc inside the network browser.
> With netbios browsing consolle, I get back an error "Impossible to find
the
> master browser"
> This happen even if I remove the WINS address from the client ip
> configuration, so I suppose it depends from DNS.
> Anyway, if I type the server name as \\server\ I am able to browse the
> server resource.
> If I restart RRAS everything works fine, till an other user logon to rras
> port.
> I've tryed to set the dns to listen only to the internal lan address, but
is
> does not solve.
> I know this problem is well known under windows 2000 server, and the
Italian
> Microsoft Support answered me that this problem is not existing under
> windows 2003 server.
> Does anyone have the same problem?
> Any suggestion?
> Thank you
> Alessandro Belli
>
>

No, the browser service has nothing to do with DNS. The problem you are
seeing is a new form of the old multihomed PDC problem from NT days.

The browser service with Netbt (Netbios over TCP/IP) works by building
browse lists in each segment (using broadcasts). Problems occur if a browser
(especially a first/only DC which is the Domain Master Browser) is
multihomed (ie has interfaces in more than one segment).

If you make a DC a remote access server, it becomes multihomed as soon
as a remote client connects, because the server acquires an extra IP for its
internal RAS interface. To prevent this causing problems with browsing, you
need to disable Netbios over TCP/IP on the RAS interface. ( I trust that you
have already disabled Netbt on the server's public interface, if it has
one).

To prevent Netbt on the RRAS interface.

Open Registry Editor.
Navigate to HKLM\System\CurrentControlSet\Services (continued next line)
\RemoteAccess\Parameters\Ip

Create a new REG_DWORD called DisableNetbiosOverTcpip
Set its value to 1

After you do this, restart RRAS. Then check your WINS database and clear
out any old entries which have the RAS interface IP. The only entries for
the server's name should refer to the LAN IP.

Since you have mentioned DNS, note that you can get similar problems
with DNS if you allow dynamic DNS registration. You can again get the
problem of a name associating with more than one IP address. This doesn't
affect browsing, but it can cause other problems. See KB 289735 .

"Alessandro Belli" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Status: one Windows 2003 server as domain controller,WINS and DNS server
> active, RRAS active to allow external user (NT4) to access internal
> resources.
> In the internal lan, there are w9x, 2k and XP client.
> When an external user logon to RRAS port, nobody with win2k and XP are
able
> to see any pc inside the network browser.
> With netbios browsing consolle, I get back an error "Impossible to find
the
> master browser"
> This happen even if I remove the WINS address from the client ip
> configuration, so I suppose it depends from DNS.
> Anyway, if I type the server name as \\server\ I am able to browse the
> server resource.
> If I restart RRAS everything works fine, till an other user logon to rras
> port.
> I've tryed to set the dns to listen only to the internal lan address, but
is
> does not solve.
> I know this problem is well known under windows 2000 server, and the
Italian
> Microsoft Support answered me that this problem is not existing under
> windows 2003 server.
> Does anyone have the same problem?
> Any suggestion?
> Thank you
> Alessandro Belli
>
>

thank you, I will try to disable netbios on the rras port.
Bye
Alessandro
"Alessandro Belli" <(E-Mail Removed)> ha scritto nel messaggio
news:(E-Mail Removed)...
> Status: one Windows 2003 server as domain controller,WINS and DNS server
> active, RRAS active to allow external user (NT4) to access internal
> resources.
> In the internal lan, there are w9x, 2k and XP client.
> When an external user logon to RRAS port, nobody with win2k and XP are
able
> to see any pc inside the network browser.
> With netbios browsing consolle, I get back an error "Impossible to find
the
> master browser"
> This happen even if I remove the WINS address from the client ip
> configuration, so I suppose it depends from DNS.
> Anyway, if I type the server name as \\server\ I am able to browse the
> server resource.
> If I restart RRAS everything works fine, till an other user logon to rras
> port.
> I've tryed to set the dns to listen only to the internal lan address, but
is
> does not solve.
> I know this problem is well known under windows 2000 server, and the
Italian
> Microsoft Support answered me that this problem is not existing under
> windows 2003 server.
> Does anyone have the same problem?
> Any suggestion?
> Thank you
> Alessandro Belli
>
>