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

    • No operating system works well with programs that modify its interface. There will always be bugs, whether it's MacOS or Linux. Windows too, you'll only suffer from bugs using this crap software.
    • KDE brings UI improvements, bug fixes and more to Plasma 6.4 as stable release draws near by David Uzondu With less than a month to the release of Plasma 6.4, the KDE dev team has shared what it has been working on in the latest issue of its weekly roundup. The update shows a heavy focus on user interface polish and a whole slew of bug fixes as the June 17 release date gets closer. The team has pushed a number of UI refinements for the upcoming version. On the System Settings page for Wi-Fi, the network list can now be fully navigated with a keyboard. KDE also disabled the ability to drag and drop displays on top of one another in the monitor settings. This was done because it could create unsupported arrangements that triggered a cascade of strange bugs throughout the system. Waking up a sleeping computer by pressing the power button no longer causes the bizarre logout screen to appear after you unlock it, which is a relief. Alignment issues in the settings page for the Digital Clock widget were also resolved. The list of bug fixes for 6.4 is extensive. The development team has fixed the most common crash affecting the System Monitor and squashed another one related to a divide-by-zero error. For users with multiple monitors, a long-awaited fix has landed that prevents windows from disappearing when the screen they are on gets disconnected. Even the humble Sticky Notes widget received attention; it will no longer freeze the Plasma shell if you place it on a very thick panel. Discover, the software center, also had a bug patched that caused it to crash if closed too quickly after launch. Here's the full list of improvements: Putting a Sticky Note widget on a very thick panel can no longer cause Plasma to freeze; now, you can use a thick panel with a sticky note on it as a notes sidebar. Fixed the most common System Monitor crash. Fixed another crash in System Monitor, this time a divide-by-zero. Fixed a case where xdg-desktop-portal-kde could crash after you choose a video source to start streaming. Fixed a bug that caused Discover to crash if you close it immediately after it launched. Fixed multiple subtle bugs with the screen chooser widget and OSD that caused it to do the wrong thing on rotated screens or when mirroring screens. Fixed a bug that caused the System Settings’ search field not to be focused properly when pressing Ctrl+F while any UI elements in a settings page already had focus. Fixed the root cause of multiple issues involving windows disappearing when you disconnect the screen they’re on. Clicking a button on a desktop widget that opens a menu no longer inappropriately makes the widget enter Widget Edit Mode. Files with a # or ? character in their name or full path are no longer unexpectedly missing from the history lists in Kicker/Kickoff/etc launchers. Fixed a bug that caused the screen chooser window to sometimes not appear as expected when OBS was launched. Fixed a bug that caused tiled windows on a multi-screen setup to lose their tiling settings when the system went to sleep and woke up again. The "Move window to [activity]" feature now works properly when invoked from the Task Manager widget. Fixed a bug in the Kicker Application Menu that caused keyboard navigation not to work if the popup opened with an item under the pointer. In the Overview effect’s grid view, dragging windows tiled on one virtual desktop over to a different virtual desktop now keeps them tiled as expected. The focus may be on the imminent 6.4 release, but work on what comes next never really stops. Looking ahead, development on Plasma 6.5 is already well underway. Just last week, the KDE team brought several performance improvements to Plasma 6.5.0. This week, the team fixed a nagging bug that sometimes caused the Networks widget to think a hotspot was still enabled after disconnecting from Wi-Fi. On the features side, the System Settings' Fonts page now prevents you from breaking your system entirely by setting fonts below 4pt. In addition to that, switching time spans in the Info Center’s energy page now features smooth graph animations. Performance-wise, kwriteconfig should also be faster, allowing changes you made to the keyboard layout using the tool to reflect immediately.
    • Display Driver Uninstaller (DDU) 18.1.1.4 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.1.4 changelog: Intel: Added NPU presence detection before removing shared DLL files (these were previously left to prevent potential NPU-related issues). Intel: Added optional NPU removal Improved "Extension" driver removal process. Updated several translations. Download: Display Driver Uninstaller 18.1.1.4 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot | Forum Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • That is what I also think to a point. How is 26 necessarily different than just another iteration like 18, 19, 20, etc? At first I think it would be better for Apple to use 2026, 2027, and then maybe truncate it to just 28, 29, and so on. Granted, I also think it makes more sense to use the year when it was released (2025 or 25), not 26/2026. Maybe Apple's thinking is as stated by Aditya that the bulk of a release being the current release is during the following year (2026, for example) after it is released (2025, for example). There are other examples of these sorts of things. In the NBA, the season has always started in the Fall and ends in the Spring. When the season ends is how the season is named. So, this is the 2025 NBA season and the Pacers and Thunder are playing to be the 2025 NBA Champions. The NFL starts in the Fall and the end of the season is always in the beginning of the next year as well. The Super Bowl was played on February 9, 2025, but that was the end of the 2024 NFL season. So, contrary to the NBA, the NFL names it season based on when it starts, not when it ends. Maybe that is because more of the NFL season is played at the end of the year (2024 in the most recent example) whereas most of the NBA season is played in the first half of the following year (2025 in the current example).
  • Recent Achievements

    • Week One Done
      abortretryfail earned a badge
      Week One Done
    • First Post
      Mr bot earned a badge
      First Post
    • First Post
      Bkl211 earned a badge
      First Post
    • One Year In
      Mido gaber earned a badge
      One Year In
    • One Year In
      Vladimir Migunov earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      snowy owl
      252
    3. 3
      +FloatingFatMan
      251
    4. 4
      ATLien_0
      228
    5. 5
      +Edouard
      191
  • Tell a friend

    Love Neowin? Tell a friend!