Archived from groups: microsoft.public.win2000.general,microsoft.public.windows.server.general,microsoft.public.windows.server.networking (
More info?)
To add to what Michael has said, using a DC as a remote access server is
not a great idea. Browsing will certainly be a problem and you may get
problems with DNS as well. There are a couple of KB articles on this. They
were issued for W2k but still apply for W2k3 DCs. The issue is similar to
the old NT problem of multihomed browsers.
292822 Name Resolution and Connectivity Issues on Windows 2000 Domain
Controller with Routing and Remote Access and DNS Installed.
830063 Name resolution and connectivity issues on Windows 2000 domain
controllers that have the Routing and Remote Access service and DNS
installed.
Michael Giorgio - MS MVP wrote:
> You've got multihomed master browser issue:
>
http://support.microsoft.com/search/default.aspx?qu=multihomed%20master%20browser
>
> BTW WINS aids in browsing.
>
> "Grant" <gpsnett@hotmail.com> wrote in message news:
>> Thanks for that info. I should explain in further detail what the
>> configuration is here.
>>
>> Machine1: win2k3, DC, 2 network cards on the same subnet, was
>> cofigured for routing and remote access, now disabled.
>> Machine2: win2k3, DC, 2 network cards on the same subnet, cofigured
>> for routing and remote access. This machine will be replacing
>> Machine1.
>>
>> Machine2 has been trying to get the browser list from machine1 for a
>> couple of days now and now when I try and browse the domain from
>> machine2 I get this new error message:
>>
>> ----------------------
>> System error 6118 has occurred.
>> The list of servers for this workgroup is not currently available
>> ----------------------
>>
>> However I can browse ALL machines on my domain from Machine1. I can
>> see both subnets fine. Any other computers on this subnet can only
>> see the .1 subnet though.
>>
>> This problem has something to do with this pesky browser service.
>> All I have changed on Machine2 is to remove the Wins server from
>> each network card and enable NETBIOS over TCP/IP. The machine is now
>> impotent at browsing the domain.
>>
>> Why cant machine2 get this list from machine1? They can both see
>> each other fine - theyre both DC's ffs!
>>
>> grrrrr
>>
>> "Mark P" <bluetick_hound@hotmail.com> wrote in message
>> news:e%231UXzpcFHA.3620@TK2MSFTNGP09.phx.gbl...
>>> DHCP servers are supposed to check to see if an ip address is on the
>>> network. if it doesn't find it then it will pass out that il
>>> address.
>>>
>>> One thing that i did before moving DHCP was to set the exporation
>>> for a DHPC
>>> ip was down to about 15 min. That way the computer would request a
>>> new ip address sooner rather than later. Standard time out is 1
>>> day i think not sure. I have mine set to 8 because of the amount
>>> of guest that come in and
>>> out of the office. It allows for IPs not to be taken up all day
>>> long if we
>>> run out.
>>>
>>> As far as your Browser war is conserned -- i have that problem also
>>> because
>>> of subnetting. I'm running about 50 different subnet through Cisco
>>> routers.
>>> and 4 states. If i use ip helper address through the routers to
>>> pass out DHPC to those locations on there subnet (my DHCP scope is
>>> huge BTW) and don't cut off other ports on the router .. everything
>>> would be at war because a computer on each subnet will want a
>>> master browers for there subnet. Windows 98 computers will also
>>> cause Browser issues. They don't understand windows 2000 and above.
>>>
>>> If you are not running a router between your subnets then you
>>> should make your DHCP and Master DC servers 255.0.0.0 class A or
>>> even a class B 255.255.0.0 sub net. The server will see both
>>> subnets.. and just give the server 2 different ip address.. i.e.
>>> 192.168.1.1 and 192.168.200.1 DHCP server can be 192.168.1.2 and
>>> 192.168.200.2. i only have 1 ip and a class A
>>> subnet on my corp lan the servers have no issues seeing all comuters
>>> across
>>> the WAN.
>>>
>>> One other thing to note is that if you wish to no tmake your
>>> servers have 2
>>> IPs / class AorB subnet / 2 subnets. Then you need a router on your
>>> network
>>> behind the firewall that will route that traffic to different
>>> computers.
>>>
>>> if you want all computers to see all computers then subnet for all
>>> should be
>>> 255.255.0.0 for a 192.168.xxx.xxx network... all computers from
>>> 192.168.1.1
>>> to 192.168.254.254 (192.168.255.255 is a broad cast) that should
>>> also fix the problem because they are all part of the same subnet.
>>>
>>>
>>> "Phillip Windell" <@.> wrote in message
>>> news:uthDWJocFHA.1356@TK2MSFTNGP10.phx.gbl...
>>>> Just do a "release/renew" on the machine. It will not be a lasting
>>>> problem. Don't mess with anything.
>>>>
>>>> --
>>>>
>>>> Phillip Windell [MCP, MVP, CCNA]
>>>> www.wandtv.com
>>>>
>>>> "Grant" <gpsnett@hotmail.com> wrote in message
>>>> news:%23wr148ncFHA.3492@TK2MSFTNGP14.phx.gbl...
>>>>> I moved DHCP to a new server and one of the client machines got a
>>>>> duplicate IP address error message yesterday. Is that what you
>>>>> mean? Is there a way to clear this error database and start again?
>>>>>
>>>>> "Jetro" <somewhere@internet.space> wrote in message
>>>>> news:eNGn04ncFHA.3216@TK2MSFTNGP10.phx.gbl...
>>>>>> Lost .200 view may be caused by initial "Duplicate name exist"
>>>>>> error and its
>>>>>> resolution.
Facebook
Twitter
Instagram