locked
Multi-homed server - problem with browsing network RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have network with one server which runs Exchange, Active Directory, IIS, VPN, DNS, DHCP. Router is making NAT between Internet and local networks. Server has two NICs and services such DNS must listen to both interfaces. It causes that computers have problem with browsing network. It is recommended to have Domain Controller with one NIC. I have computers joined to AD, but there are some computers which are in workgroup.

    I think that these changes may resolve this problem:

    I will connect central switch to router and I will set for router to use external DHCP at server --> Server will than have only one NIC and I can continue to use DNS, DHCP at server. At the end I will set up WINS and browsing network will work.

    Actual schema of network: internet - router - server - central switch - two switches connecting PCs with internet and AD

    Do these changes resolve my problem with browsing network?

    Monday, July 19, 2010 3:27 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I would recommend that you plug the router into the central switch and not the server.  All of your computers and server should be plugged into the switch using one NIC.

    You should also disable DHCP on the router and use the DHCP service from the server itself.  You have more control over the DHCP settings from the Windows Server.  The DHCP service on the router is very limited.  In addition, you'll need to configure specific client DNS settings so the workstations can find AD/Exchange, etc...

    Visit: anITKB.com, an IT Knowledge Base.
    Monday, July 19, 2010 7:07 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I would recommend that you plug the router into the central switch and not the server.  All of your computers and server should be plugged into the switch using one NIC.

    You should also disable DHCP on the router and use the DHCP service from the server itself.  You have more control over the DHCP settings from the Windows Server.  The DHCP service on the router is very limited.  In addition, you'll need to configure specific client DNS settings so the workstations can find AD/Exchange, etc...

    Visit: anITKB.com, an IT Knowledge Base.
    Monday, July 19, 2010 7:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you for reply.
    Monday, July 19, 2010 7:12 PM