Changed server IPs, getting errors.


Recommended Posts

I split my network into multiple VLANs putting all the servers into a VLAN and clients on to a separate VLAN.

 

I have changed the server IPs to reflect this.

 

My main DC is 2008 which I am slowly migrating to a new 2012 r2 server, which is currently the secondary DC.

 

Everything seems OK except from the Group Policy Management Console on the 2012, when loading it says:

 

"The specified domain controller cannot be contacted"

 

I can select the Master manually but then I get a different error:

"The RPC Server was unavailable"

 

Most google results relate to firewall issues, however the Windows Firewall is disabled on both servers.

 

2012 server is a VM.

.. I have also noticed I can't access it remotely, I need to go through Hyper V Manager on the host.

 

Any ideas?
 

Link to comment
https://www.neowin.net/forum/topic/1252694-changed-server-ips-getting-errors/
Share on other sites

And what do you have in your AD.. Why did you split them to different vlans?  And your not firewalling between the segments?  What is doing the routing between your segments?

 

Can you give us details of what is routing and what your segments are?  Do you have dns on both servers?  What does dcdiag say ?  https://technet.microsoft.com/en-us/library/cc731968.aspx

^ Exactly -- think maybe they just changed the address space and running both over the same physical network.  Or did they just say lets use 192.168.0.1-254 for clients and 192.168.1.1-254 for servers in our 192.168.0.0/23 ??  Details will help us help you.

  On 07/04/2015 at 10:43, BudMan said:

And what do you have in your AD.. Why did you split them to different vlans?  And your not firewalling between the segments?  What is doing the routing between your segments?

 

Can you give us details of what is routing and what your segments are?  Do you have dns on both servers?  What does dcdiag say ?  https://technet.microsoft.com/en-us/library/cc731968.aspx

 

Because we are coming away from our local authority network and had it reconfigured as a result.. we now have multiple VLANs: servers, printers, wireless APs, finance, workstations.

 

Firewall was just disabled for testing.

VLAN NAME, IP, ADDRESS RANGE, ROUTER, DEFAULT GATEWAY 
VLAN 80 ROUTING NETWORK 10.83.125.208 /28 10.83.125.209 10.83.125.215 
VLAN 81 
VLAN 82 FINANCE 10.83.121.0 /24   10.83.121.1 
VLAN 83 PRINTERS 10.83.122.0 /24   10.83.122.1 
VLAN 84 SERVERS 10.83.123.0 /24   10.83.123.1 
VLAN 85 WIRELESS AP 10.83.124.0 /24   10.83.124.1 
VLAN 86 WORKSTATIONS 10.83.112.0 /24   10.83.112.1 

Yes DNS is on both servers.

     Starting test: FrsEvent

         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems.


     Starting test: NetLogons

         [WVPS-SCH-SRV] User credentials does not have permission to perform

         this operation.

         The account used for this test must have network logon privileges

         for this machine's domain.

         ......................... WVPS-SCH-SRV failed test NetLogons



    Starting test: Replications

         [Replications Check,WVPS-SCH-SRV] DsReplicaGetInfo(PENDING_OPS, NULL)

         failed, error 0x2105 "Replication access was denied."

         ......................... WVPS-SCH-SRV failed test Replications




      Starting test: Services

            Could not open NTDS Service on WVPS-SCH-SRV, error 0x5

            "Access is denied."

         ......................... WVPS-SCH-SRV failed test Services

Seems like some permission errors? Maybe unrelated to the networking changes? It is strange this only happened after network changes, these errors weren't present previously.

Well you might be getting access denied because of dns problems pointing to old IPs, etc..

 

Validate dns with dcdiag..  As to firewalls - not talking software firewall.. What is actually routing between your segments?  A layer 3 switch?  Router/Firewall distro, hardware router?

As budman stated you are probably missing something, a dns entry on your network adapters possibly.   may need to run a ipconfig /registerdns to force an immediate update to dns. 

 

If you have internet access, I would be more than happy to look at this for you.  open up a teamviewer session (go to teamviewer.com) and pm me the id and password.

  On 07/04/2015 at 12:24, BudMan said:

Well you might be getting access denied because of dns problems pointing to old IPs, etc..

 

Validate dns with dcdiag..  As to firewalls - not talking software firewall.. What is actually routing between your segments?  A layer 3 switch?  Router/Firewall distro, hardware router?

 

Cisco Catalyst 3560 v2

 

  On 07/04/2015 at 12:38, Jared- said:

Can you access other VMs on your Hyper-V host remotely? 

 

Yes they seem ok.. We have 3 VMs on the server, one of them is the domain controller which is the only one I am having trouble from.

 

  On 07/04/2015 at 13:05, sc302 said:

As budman stated you are probably missing something, a dns entry on your network adapters possibly.   may need to run a ipconfig /registerdns to force an immediate update to dns. 

 

If you have internet access, I would be more than happy to look at this for you.  open up a teamviewer session (go to teamviewer.com) and pm me the id and password.

 

I am off site now but will give it a go tomorrow.. If I need help I will send you team view details in PM, thanks for the offer.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • This is the curse of Linux on the desktop, the development and maintenance manpower is spread out across countless distributions. The same thing has to be integrated many times.
    • The new official logo of the GOP
    • Linux 6.16-rc1 is out: What's new and what does it mean for your system? by Paul Hill Linus Torvalds, head and founder of the Linux kernel, has announced the closure of the merge window where major new features are added to the kernel, and the beginning of the Linux 6.16 release candidates, beginning with release candidate 1 (Linux 6.16-rc1). Linux 6.15 was released two weeks ago and in the time since, developers have had the opportunity to try and get their new kernel features into the Linux 6.16 kernel. Over the next two months, we will get seven or eight release candidates where developers will stabilize new and existing features. This means that the stable version of Linux 6.16 will arrive around the end of July. Torvalds said that the merge window seemed pretty normal this time, but did say he had a feeling that there were more “late straggler” pull requests than is typical. Despite this, everything seems to be fine and the schedule will be going forward as planned. Key areas of development Torvalds explained that around half of the changes in the first release candidate were driver updates, with the bulk of those being made up with by GPU and networking drivers. For end users these are the most important changes because when your favorite distribution of Linux ships a new release with this kernel, it will support more graphics cards and networking equipment like Wi-Fi cards. The non-driver updates in this version are split between architecture-specific updates, documentation and tooling (perf tool and selftests), and core changes to filesystems, core kernel, memory management, and networking. Torvalds said the core changes include some of the “most important” changes, though they’re not necessarily major changes. Fixes to the core ensure a more stable Linux kernel for end users, plus better performance. The merge window saw developers submit thousands of non-merge commits and merges. The non-merge commits were around 13,000 while the merge commits nearly reached 1,000. There were 1,783 unique authors submitting code during this window. Next steps Over the coming weeks, Linux developers, including individuals or representatives of companies, will submit bug fixes for new and existing features. This release candidate cycle will run until around the end of July and then the final version will become available. End users shouldn’t go out and download Linux 6.16 when it’s released, instead just wait for your Linux distribution to update to it, as distribution-specific changes get made. Neowin will be following these releases and reporting on any interested changes that are noted. Source: LKML
    • There was no cancelation. Microsoft delayed work on it to focus on further tuning the OS and improving the OS experience overall, before going full core into a direct hardware battle with their partners.
  • Recent Achievements

    • Week One Done
      Al_ earned a badge
      Week One Done
    • Week One Done
      MadMung0 earned a badge
      Week One Done
    • Reacting Well
      BlakeBringer earned a badge
      Reacting Well
    • Reacting Well
      Lazy_Placeholder earned a badge
      Reacting Well
    • Dedicated
      Epaminombas earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +FloatingFatMan
      273
    3. 3
      ATLien_0
      242
    4. 4
      snowy owl
      211
    5. 5
      Edouard
      182
  • Tell a friend

    Love Neowin? Tell a friend!