Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

SBS 2011 RDP login works but gives 404 error for System choices

Posted on 2014-04-03
2
Medium Priority
?
349 Views
Last Modified: 2014-04-03
Remote Desktop users can "log on" to the initial page but get 404 error after selection screen is given. The selection screen is what I'm call the 1st page after RDP logon that gives a user the choice of selecting the REMOTE computer name or choice of E-mail or shared folder use.  Actually, the selection page flashes for a second and then the 404 error appears.

This happened after I used the SBS Wizard to "fix my network" where it saw "Your domain name as incorrect DNS settings".

DNS is now confused within the SBS virtual world. The outside world knows how to get there but once inside...problems

Here is the setup:
SBS 2011 Premium on a dual-cpu, quad-core Xeon E5620 HP Proliant with 32 GB RAM

Host OS "HYPERV" - 2008R2 with Hyper-V only
VM OS "GUEST1" - 2008R2 SBS w/Exchange2010  [3 cores, 10GB RAM]
VM OS "GUEST2" - 2008R2 W/SQL and RDP  [4 cores, 18GB RAM]
0
Comment
Question by:USER8719
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 16

Accepted Solution

by:
Enphyniti earned 1500 total points
ID: 39975110
does your internal AD domain name match your external public domain?  If so, you need to have split DNS that keeps seperate records for public and internal IPs.

for example, if your public dns lists www.yourdomain.com as 200.123.123.123, you'd need to have an internal record that lists www.yourdomain.com as 192.186.0.123 (or whatever the *internal* address of your webserver is.

What is your SBS looking at for DNS resolution?  Because it should be looking at itself.  Properly configured DNS on a domain controller will look to itself first for DNS resolution.  Then DNS itself should be configured with valid forwarders to handle requests that cannot be resolved locally.
0
 

Author Closing Comment

by:USER8719
ID: 39975866
ENPHYNITI:
Thanks for the answer.  It was good general advise.  As it turns out the issue was much more complex.  So, I'll give you points for the answer anyway.  

The SBS "Wizard" really messed up the system.  We actually got Microsoft involved.  They ran a diagnostic and made some SSL changes in the registry.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question