I have a 2016 Server, that has Hyper-V installed but not being used. This is a production server used 24/7.

The server is showing a vEthernet adapter and an Ethernet adapter. It appears that the server is using the vEthernet adapter and not the Ethernet adapter for normal use. Most of the connection items for the Ethernet adapter are unchecked. They are checked for the vEthernet.

The server has occasional connectivity problems, and the network icon in the notification area indicates there is no internet access. However, there is internet access.

I would like to use the regular Ethernet adapter instead of vEthernet. Is the correct procedure to check all the items on Ethernet that are currently checked on vEthernet. Then, uncheck those options on vEthernet?

I am considering removing Hyper-V from this server using Add/Remove Windows Features, but based on various warnings regarding removing Hyper-V, I am concerned it could cause side effects or stop the server from booting.

We have a customer with a Server 2008 R2 Remote Desktop Server.

When we log onto the server via RDP as User1, the time in the RDP session matches the time of the server.

When we log onto the server via RDP as User2, the time in the RDP session is six minutes faster than the server clock. This occurs regardless of the PC used to log into the server.

How can the time in one user session be six minutes off from the server clock? I didn't even think this would be possible.

I can't find anything online about this issue. If it was a timezone issue, it seems like the clock would be off by one hour. In this case, User1, User2, and the PC used to connect are all set to EST.

On a Windows Server 2012 R2 machine, logged in as domain administrator trying to access the c:\users\public\desktop folder, getting access denied. This machine is the domain controller.

How can I get access to this folder?

1. Using takeown from cmd.exe using runas as the local domain administrator:

C:\Users\Public>takeown /f c:\users\public\desktop
ERROR: Access is denied.

2. Tried icacls

C:\Users\Public>icacls Desktop /t /grant Everyone:F
Desktop: Access is denied.
Successfully processed 0 files; Failed processing 1 files

3. Viewing it via explorer when logged in as domain administrator

How can I view the all the print queues on a 2008 server, even redirected ones created by remote desktop users?

When I log into a Server 2008 Server as Administrator, and I view the Printers folder (or use the Print Management tool) I only see my printers, and printers created via a 3rd party tool, Screwdrivers. I don't see the redirected print queues created for remote desktop users. Is there any way to see or manage these print queues as an administrator?

I can shadow the users and see their print queues, but that's the only way right now.

We can't connect to a specific external server from inside our LAN.

However we can connect to the same server from outside our LAN, at home, or using a mobile phone. It was working just fine for months, and one day it stopped working. I can't figure out what, if anything, changed when it stopped working.

I'm trying to develop a procedure to troubleshoot this and pinpoint the problem.

The server is a hosted CentOS vps. If I ping any of it's 3 IP addresses from inside our LAN, the ping times out. If I try to connect to web servers on the vps, it times out. If I perform a tracert, I get these results:

Tracing route to static-161-150-73-69.nocdirect.com [69.73.150.161] over a maximum of 30 hops:

1     *        *        *     Request timed out.
2     *        *        *     Request timed out.
3    34 ms    10 ms    30 ms  96.120.4.229 
4    10 ms    12 ms     8 ms  xe-11-1-0-32767-sur01.n4atlanta.ga.atlanta.comcast.net [68.85.68.61] 
5     9 ms    15 ms    12 ms  xe-9-0-2-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.86.106.182] 
6    14 ms    23 ms    23 ms  he-5-12-0-0-10-cr01.56marietta.ga.ibone.comcast.net [68.86.93.125] 
7    16 ms    15 ms    15 ms  pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.86.86] 
8    21 ms    12 ms    16 ms  173.167.57.134 
9     *       19 ms    18 ms  ae3-20g.cr2.atl1.us.nlayer.net [69.31.135.165] 
10    18 ms    13 ms    16 ms  as46562.ae6-1677.cr2.atl1.us.nlayer.net [198.47.120.146] 
11    11 ms    16 ms    25 ms  184.170.245.254 
12    13 ms    21 ms    15 ms  209.140.17.58 
13    23 ms    12 ms    19 ms  arya.nocdirect.com [69.73.150.66] 
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *    [10.0.0.144]  reports: Destination host unreachable.
Trace complete.

Our LAN is behind a D-link DFL-800 firewall. I can't see any rules on the firewall to block traffic to these 3 addresses.

I CAN ping other IP addresses that are probably at the hosting company, IP's that are slightly above and below the IP range.

Here's a successful tracert from outside our LAN

Tracing route to static-161-150-73-69.nocdirect.com [69.73.150.161] over a maximum of 30 hops:

1     1 ms     1 ms     1 ms  192.168.1.1 
2    28 ms    22 ms    26 ms  c-76-111-52-1.hsd1.ga.comcast.net [76.111.52.1] 
3     9 ms     8 ms    10 ms  xe-11-0-0-32767-sur01.b6powsprings.ga.atlanta.comcast.net [68.85.68.109] 
4    53 ms    17 ms    13 ms  xe-11-1-1-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.85.108.169] 
5    19 ms    23 ms    23 ms  he-5-13-0-0-10-cr01.56marietta.ga.ibone.comcast.net [68.86.93.201] 
6    12 ms    15 ms    12 ms  pos-0-11-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.88.186] 
7    13 ms    16 ms    18 ms  173.167.57.134 
8    11 ms    17 ms    10 ms  ae0-50g.cr1.atl1.us.nlayer.net [69.31.135.129] 
9    13 ms    13 ms    10 ms  ae1-40g.cr2.atl1.us.nlayer.net [69.31.135.138] 
10    12 ms    12 ms    11 ms  as46562.ae6-1677.cr2.atl1.us.nlayer.net [198.47.120.146] 
11    18 ms    70 ms    23 ms  184.170.245.254 
12    12 ms    16 ms    16 ms  209.140.17.58 
13    13 ms    13 ms    11 ms  arya.nocdirect.com [69.73.150.66] 
14    15 ms    20 ms    13 ms  static-161-150-73-69.nocdirect.com [69.73.150.161] 
Trace complete.

Resolution:

I SSH'd into the server and followed the procedure outlined in the following blog post.

How to Remove and Add Rules to IP Tables Chains in Centos Linux

1 Dump all the rules to a file

iptables -L -n --line-numbers > /tmp/ip.tables

2 Edit the file using vi

vi /tmp/ip.tables

3 Locate LOCALINPUT or LOCALOUTPUT rules that DROP your IP. Make a note of the rule number.

4 Delete the rules

iptables -D LOCALINPUT {rule#}

iptables -D LOCALOUTPUT {rule#}

5 Add rules to allow your IP

iptables -A INPUT -p all -s {IP} -j ACCEPT

iptables -A OUTPUT -p all -s {IP} -j ACCEPT

We have Windows Server 2012 Standard as a remote desktop server, and older legacy thin clients cannot connect to it. Is there guidance that indicates the minimum required version of RDP to connect to Server 2012?

When we activated a license server on our 2012 Standard RDS server, some of the thin clients started receiving an error when they connect: "Remote Desktop disconnected because of a security error. The client cannot to the remote computer. verify you are logged on the network and try connecting again"

The server also logs "A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 10."

We believe that the version of RDP on the thin client dictates whether or not it can connect.

Windows 8, Windows 7, and Windows XP SP3 can connect, as can newer thin clients.

We have unchecked the "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)" located on the Remote tab of System Properties, and on Server Manager\Remote Desktop Services\Collections[servername]\Properties of the collection->Tasks->Edit Properties. However, older thin clients still cannot connect.

I can't find an authoritative answer from Microsoft as to exactly what version(s) of RDP are supported to connect to RDS under Server 2012.

We host some web sites on servers in our office. We have two internet connections, a primary and a backup connection (with separate IP address ranges.) We need to be able to detect, from outside our LAN, that the primary internet connection has failed.

We use a special DNS service that will switch the DNS records to point at our backup IP addresses if the primary addresses go offline. It detects if our primary addresses have gone offline by pinging a server, or loading a web page on our end, and if that fails, it switches our DNS over to the secondary IP addresses.

We did have it check for the existence of a page on our web server, but the problem is when we reboot that web server for windows updates, it thinks the internet connection has gone down and switches over to the secondary connection, which causes problems. It switches back after a few minutes, once the server reboots.

Up until recently, my procedure was to log into the external DNS and disable the fail-over, then reboot the server, then re-enable it. It's not an optimal solution because the fail-over has to set on on per-domain basis, and there are quite a few.

I would like to have the fail-over check a device which is always on, 100% of the time. Preferably no moving parts on a UPS, so it never goes down. I tried to use a Hawking print server, which has a web-based interface, but it seems unreliable as it has detected the internet connection has failed when it really has not. Worst case, I can build a fan-less PC that boots from USB maybe, and just runs a stripped down unix version with a web host that serves one page.

Are there any simple, 100% reliable devices that could be pressed into service that can be pinged, or serve a web page that could be used?

We use the Remote Desktop role in Server 2008 Enterprise SP2 to give users access to a 32-bit application. It is configured to auto-start the application via the "Start the following program at logon:" property for the user. When the user exits from the application, it should automatically log them off the server.

However, it simply hangs with a blank desktop in the RDP session. If we run task manager in the session, we can see that splwow64.exe is still running (along with the other standard RDP session applications.) If we terminate splwow64.exe then the session logs off.

How can we force splwow64.exe to terminate with our application so the session will log off?

I need to add the URL's that IE is accessing for SmartScreen Filter to our proxy server white list. Since we've enabled our white list we get a popup from IE that it can't access the SmartScreen filters.

I've googled various variations on that question but I keep coming back to how you can manage what URL's it filters.

I've found the windows update URL's (shown below), but it seems that the SmartScreen ones are different.

• .download.windowsupdate.com
• .update.microsoft.com
• .windowsupdate.com
• .windowsupdate.microsoft.com
• download.microsoft.com
• download.windowsupdate.com
• ntservicepack.microsoft.com
• windowsupdate.microsoft.com
• wustat.windows.com