Domain users across VPN can ping server but not connect to shared drives
Recently installed Open VPN which is part of our Untangle UTM gateway for the site. VPN connects and works as far as being able to ping any machine in the network, Browse internal IP for web app, or even RDP to other servers in the network.
When you try to connect to a server that has file shares on it we get (ipx.x.x.x\shared The system detected a possible attempt to compromise security. Please ensure that you contact the server that authenticated you.)
The VPN is launched after the user logs in to a domain profile on the laptop they are working from. I do not know if this is an issue that the system does not think that the user is authenticated or what?
We have deleted the drive maps from the individual machine and tried to put them back in but since we can not connect the system will not allow us to put them in.
With a stat run to the \\ip.x.x.x.\shared the system as for a username and password. Using proper domain credentials it will not connect.
For testing I logged off the domain user and then onto the machine as a local account Administrator and tested and it all worked fine. When connecting to the ipx.x.x.x\shared from the RUN command it asked for username and password. Gave it the same domain users account credential as above and it worked. Shares work the whole 9 yards.
What is blocking or keeping this from coming through? I have another client with the exact same setup just different domain and it works perfectly.
There have been nothing but problems from the get go with this new client, DEAD Exchange server, BAD BDC that died and was not removed, same with Old Exchange server not being removed, Upgraded exchange 2003 to 2010 but none of the addon options or database were upgrade etc. Exchange was removed to an outsourced solution, BDC removed properly, and cleanup of AD etc. I have done everything short of recreating the domain from scratch. DCDIAG showes no error for the domain.
Open to any and all suggestions.
When you try to connect to a server that has file shares on it we get (ipx.x.x.x\shared The system detected a possible attempt to compromise security. Please ensure that you contact the server that authenticated you.)
The VPN is launched after the user logs in to a domain profile on the laptop they are working from. I do not know if this is an issue that the system does not think that the user is authenticated or what?
We have deleted the drive maps from the individual machine and tried to put them back in but since we can not connect the system will not allow us to put them in.
With a stat run to the \\ip.x.x.x.\shared the system as for a username and password. Using proper domain credentials it will not connect.
For testing I logged off the domain user and then onto the machine as a local account Administrator and tested and it all worked fine. When connecting to the ipx.x.x.x\shared from the RUN command it asked for username and password. Gave it the same domain users account credential as above and it worked. Shares work the whole 9 yards.
What is blocking or keeping this from coming through? I have another client with the exact same setup just different domain and it works perfectly.
There have been nothing but problems from the get go with this new client, DEAD Exchange server, BAD BDC that died and was not removed, same with Old Exchange server not being removed, Upgraded exchange 2003 to 2010 but none of the addon options or database were upgrade etc. Exchange was removed to an outsourced solution, BDC removed properly, and cleanup of AD etc. I have done everything short of recreating the domain from scratch. DCDIAG showes no error for the domain.
Open to any and all suggestions.
databoks
Looks like you are accessing a share on a differnt domain - if so are there a trust between these two domains?
ASKER
Only the one domain listed in DNS server. When I searched I read that to and was puzzled as to why the machine would think that it trying to access another domain other than the parent. No Child domains.
Fine. So no other domains. And it does work with an administrator account?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My solution is what fixed the problem.