+ Post New Thread
Results 1 to 3 of 3
Windows Server 2008 R2 Thread, Troubleshooting help in Technical; I am having some network issues and I am struggling to troubleshoot it. We have a single server running S2008R2. ...
  1. #1

    Join Date
    Jun 2011
    Location
    Dublin, Ireland
    Posts
    23
    Thank Post
    6
    Thanked 3 Times in 3 Posts
    Rep Power
    7

    Question Troubleshooting help

    I am having some network issues and I am struggling to troubleshoot it. We have a single server running S2008R2. It has two nics, one connected to the internet and one on our LAN. It is the DC and it is running:
    • DHCP
    • DNS
    • DFS
    • RRAS - NAT for internet
    • Print Management

    Everything was running fine until last week when a second server was accidentally switched on. It was also set up as a DC. I switched that back off, but ever since we've had a raft of problems that I am struggling to fix.

    Working
    Server internet- inet working fine on server
    Ping- Everyone can ping each other no problem
    NSLookup- Shows correct IP and name for server & workstations

    Intermittent
    Login- No logon server available to service your request, you can log in if you keep trying
    Internet- Working from Server and some (random) workstations

    Not working
    Remote Desktop
    Shared Drives Network path not found
    Network Printers Offline - can go to the print server IP address from a browser
    Group Policy gpupdate /force fails, lack of connectivity to a DC

    I am thinking something is screwed up with Active Directory, but I don't really know how to trouble shoot, any suggestions would be brilliant

    Thanks,

    Niall.

  2. #2

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,137
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    77
    The OLD you switched on, what do you plan to do with it? If not needed I would decomm that

    How long was that DC off for? How many days?

    Could have replicated old data across to the working DC.

  3. #3

    m25man's Avatar
    Join Date
    Oct 2005
    Location
    Romford, Essex
    Posts
    1,618
    Thank Post
    49
    Thanked 448 Times in 331 Posts
    Rep Power
    136
    Multihoming a DC is fraught with complexities and the re-introduction of a second DC will only cause more complications.

    If your current DC is the only DC in the Domain and the old one you turned on is not in anyway still related it should not have had any great impact, however your lack of explaination as to what the other DC's role in this network is/was leaves me wondering what are we dealing with here?

    Firstly I would thoroughly recommend that you stop using your DC as an Internet Router and get yourself a proper firewall apart from making your DC a Bullseye on the Internet there are the added complexities of NAT and the Windows Firewall to contend with.
    Having spent years working with SBS2000 2003 2008 and now 2011 I can assure you it will make life a whole lot easier and safer.

    The Multi Homing will give you severe headaches in the Binding Order department unless you have been meticulous in setting each service up and making sure things are correct such as what NIC is your DHCP binding to?

    I suggest you research the topic of Multi Homing a DC on Google you will find all sorts of useful stuff such as this Can DC be multihomed in Windows 2008 Server?
    All telling you why it's not a good idea to Multihome your DC.

    By all means do it on a stand alone even a virtual one but not on your DC unless you are absolutely certain you understand what your doing.

SHARE:
+ Post New Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •