SHAREPOINT 2010 MIGRATION AND NOW USERS CANT LOGIN

All, My client has a Hyper V server running on a physical host in our colocation flawlessly. They are wanting to vacate the co-location and move everything into a 3rd party cloud...So, I recently moved the Hyper V to a VM environment in the cloud.  It came from its native environment and is now being hosted in a 3rd party cloud by Intermedia. I setup a VPN tunnel back to the domain environment at the co-location and the VPN shows that it's up and running fine and is passing network traffic.

Even though VPN is up and running, I was unable to ping domain controller. I am able to ping the domain controller by IP, just not by server name. I modified the HOST file on the new virtual server which is running SharePoint 2010 Enterprise and am now able to ping the domain controller by server name from the virtaul server.

Here's the real issue....

The new server loads up, sharepoint works fine with one catch...The only user that can login to SharePoint is the domain Administrator. If any other user trys to login, they cant. There's no error displayed. Simply, the login box goes away for about a second and then simply prompts for a login again.

Just for info, SharePoint 2010 and SQL are loaded on the same Virtual server in the new cloud environment.




Did I forget to do something here ? Also, please let me know if I need to provide any more detailed info.

What could I have done wrong or what step(s) did I miss ?

Thanks for taking the time to read my support question. This is a high priority and I could sure use some good input.
PAULADAMSJRAsked:
Who is Participating?
 
Darrell PorterConnect With a Mentor Enterprise Business Process ArchitectCommented:
WARNING:  DO NOT EDIT THE REGISTRY UNLESS YOU ARE COMFORTABLE WITH SUCH MODIFICATIONS.  You can do serious harm to your system if you make a mistake in the registry.

Open RegEdit
Navigate to
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters
On the right pane, right click and create a new DWORD value named ScreenBadTlds
This name is CaSe-SeNSiTiVe.
Modify the value and set it to 0.

This behavior is by design, but can be worked around using the above registry change.
0
 
Darrell PorterEnterprise Business Process ArchitectCommented:
The domain admin is likely working because that profile is cached.
This is still a domain authentication issue - this can be verified by looking at the errors in the security and system event logs.

Did you move the server to one of the configured sites in Active Directory?
0
 
PAULADAMSJRAuthor Commented:
Hi WalkaboutTigger,

I am not sure about your question. But what I did do was just removed it from Active directory and am attempting to add it back.

getting the following error when trying to do so:

Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.

An error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller for domain 192.168.26.11.

The error was: "The filename, directory name, or volume label syntax is incorrect."
(error code 0x0000007B ERROR_INVALID_NAME)

The query was for the SRV record for _ldap._tcp.dc._msdcs.192.168.26.11
0
 
PAULADAMSJRAuthor Commented:
so, it should I go put my host file back to original condition before I run the registry update ? what is this going to do for the server?
0
 
Darrell PorterEnterprise Business Process ArchitectCommented:
Since your domain name is numerical, it allows for numerical domains, which are not normally acceptable.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.