Map Drive on Windows Server 2003 R2 at System Boot


Recommended Posts

Could have been something I miss configured. But setup was as follows:

Create VM,

Install Server 2012,

Add AD DC as a role,

Join existing forest,

Joined 2008 forest 44kenlane.com,

Played around with things, edited users, etc,

No further symptoms for like two weeks.

Upon rebooting Server 2008r2 the symptoms began.

Eventually removed 2012 from domain. Issue solved.

I can not find anything that says 2012 "requires" ipv6 -- now some components do, like remote direct access.

I see this

http://technet.microsoft.com/en-us/library/hh831743

At least one Active Directory domain must be deployed with at least one Windows Server 2003, Windows Server 2008 R2, Windows Server 2008 or Windows Server 2012-based domain controller (an Internet Protocol version 6 [iPv6]-capable domain controller and global catalog)

But sure looks like you need IPv4 as well -- WTF, you going to say a component requires IPv6, then then also require IPv4 is just broke if you ask me!

http://technet.microsoft.com/en-us/library/hh831633

Configure your internal network interface with a static Internet Protocol version 4 (IPv4) address configuration.

Having things that only use IPv6 while it is not not the dominate protocol is causing more issues than its possibly helping. Your application should be able to use either or! Same **** with their homegroups, for it to work you have to use have ipv6, but it doesn't actually use IPv6 for what your doing with it.

If you going to use IPv6 in your AD, then clearly their are things that have to be configured! So that could be your problem. But if your not using direct remote access, I can find nothing that "states" you have have Ipv6 enabled on 2012.

To be honest I have having a hard time finding any good information on bringing up 2012 in a 2008r2 setup.

I find stuff that says not to disable IPv6 -- but that type of advice is BS. You sure an the hell do not need teredo running, and depending on your setup your not going to need isatap or tunnels either. So if you want people to use Ipv6 - then give the correct steps to disable the features of it that are not needed.

Or better yet have them disabled by default, and give instructions on how to bring up the protocols/features they need.

Having everything enabled out of the back is just BAD BAD BAD practice! Did they not learn their lesson when they had services enabled out of the box before like IIS and FTP, and messenger, etc.

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

    • No registered users viewing this page.
  • Posts

    • Then you answered your own question as per your own words, WINE does not have feature parity in macOS vs Linux. I’m not sure what Box86 is, but Rosetta is closed source. They can’t just add support for it. Rosetta support comes from the OS itself.
    • Couldn't a custom power plan help to park the non x3d ccd's? Then that would solve this latency/performance issues people are having with the x3d chips?
    • So is Ubuntu and Fedora (with GNOME). It's a welcome move and those that need X11 can easily install as pointed out in the article it but that won't stop a loud minority from whining of course. Funny but It will actually be easier to install X11 on Ubuntu then enable Flatpak support/Flathub and use them.
    • End of an era? Kubuntu is removing default support for X11 in new installs by David Uzondu X11, the old window system whose days have long felt numbered, just saw another one of its major supporters head for the exit. Kubuntu has decided to follow its parent distro's lead, making its next release, version 25.10, a Wayland-only affair for fresh installs. It seems many Linux developers see Wayland as the future. Just recently, Linux Mint started working to improve support for the protocol in Cinnamon, tackling lingering issues with keyboard layouts and input methods. You can even see the progress in KDE's development, where an upgrade to Wayland PiP is planned for KDE Plasma 6.5. So what's the logic behind dropping a session that, for the most part, still works? According to Kubuntu's Rik Mills, the team wants to "rip off this sticking plaster" now, in an interim release, rather than ###### off a lot of people by doing it in the next Long-Term Support version, 26.04. The developers feel that maintaining code for the aging X11 system holds back progress on security and new features that Wayland can enable more easily. Plus, supporting two separate display servers is a massive undertaking. Of course, this change might have some people worried, but relax; all is not lost if you still need the old session. If you're running hardware that acts up, like some older NVIDIA cards, or who relies on an ancient application that doesn't play nicely with the XWayland compatibility layer, you can still get your familiar session back. Just enter the following command in your terminal: sudo apt install plasma-session-x11 Once that command finishes, the X11 session will appear as an option on the login screen, so you can carry on as before. As OMGUbuntu notes, not everyone in the Ubuntu family is following its lead just yet. Other official flavors like Xubuntu, Ubuntu Budgie, and Ubuntu Cinnamon are expected to keep offering an X11 session on their default installs for this cycle.
  • Recent Achievements

    • First Post
      Johnny Mrkvička earned a badge
      First Post
    • Week One Done
      viraltui earned a badge
      Week One Done
    • One Month Later
      serfegyed earned a badge
      One Month Later
    • Dedicated
      firey earned a badge
      Dedicated
    • Dedicated
      fettermanj earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      642
    2. 2
      Michael Scrip
      221
    3. 3
      ATLien_0
      216
    4. 4
      Xenon
      144
    5. 5
      Steven P.
      143
  • Tell a friend

    Love Neowin? Tell a friend!