internal website authentication errors

Posted on 2011-05-12
Last Modified: 2012-05-11
I have two users that VPN in to our corporate network daily.  A couple of weeks ago they started running into some odd authentication errors.  I have not been able to find any changes to AD or DNS that may have caused this issue.

The user connects via VPN and puts in the internal website address (ex - intranet1-server/EDI).  An authentication box pops up and the put in their AD credentials and the box simply reappears.  It does not pass authentication.  If they use the IP address (ex - they get the same authentication box, but are now able to log in.

Users from within the corporate network are able to access these sites without needing the IP address.  A NSLookup on the computers with the issues show proper DNS resolution to one of our domain controllers and ping/ping -a both return the same information as a computer from within the network.

A check through their event viewer shows nothing of value.

Right now they are able to somewhat function using IP addresses, but these particular employees are programmers and need to have full functionality returned to them.

Anyone have any ideas on how to troubleshoot this issue?  I've searched Google and Microsoft TechNet and didn't turn up anything that helped.
Question by:Twelfelt
    LVL 11

    Expert Comment

    did you try to put the domainname in front of the username ?
    We do have to do it often when using internal webapps

    Username: domain\username
    Password: xxxx


    Author Comment

    I haven't tried that....  I will have the user give that a try tomorrow AM and we will see what we get.  Thanks!

    Accepted Solution

    OK - had them try the domain\username - didn't work.  Did some more in-depth digging on the event viewer and found some GP errors, but those were primarily because the computers couldn't reach the domain and was likely at a time that the computers were not connected through the VPN.  The only other errors I'm showing in event viewer are DNS 1014 errors which indicate the system is unable to locate a DNS server.  Once they are connected through VPN there are no further errors.  I have had them do an ipconfig /flushdns then /registerdns and did not see any errors after the fact.  
    LVL 74

    Expert Comment

    by:Glen Knight
    This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Better Security Awareness With Threat Intelligence

    See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

    BIND is the most widely used Name Server. A Name Server is the one that translates a site name to it's IP address. There is a new bug in BIND (, affecting all versions of BIND 9 from BIND 9.1.0 (inclusive) thro…
    Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

    761 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

    Need Help in Real-Time?

    Connect with top rated Experts

    12 Experts available now in Live!

    Get 1:1 Help Now