• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 211
  • Last Modified:

internal website authentication errors

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.
  • 2
1 Solution
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

TwelfeltAuthor Commented:
I haven't tried that....  I will have the user give that a try tomorrow AM and we will see what we get.  Thanks!
TwelfeltAuthor Commented:
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.  
Glen KnightCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now