After few days again and again below mentioned issue will occurred
I am totally frustrated with this error.
The server configuration file(s) could not be found:
\192.168.20.10\ERP10.2.100.0Deployment\Client\config\E10Production.sysconfig, \192.168.20.10\ERP10.2.100.0Deployment\Client\config\default.sysconfig.
1st condition: The client machine should be in the same domain with respect to your E10Production instance has configured from where you are trying to login.
2nd condition: If the client machine is in the same domain then login with a domain user and try.
3rd condition: If above both conditions are exist then check AppServerURL in the .sysconfig file on your client machine should be with your domain alias as below.
I agree with @hmwillett. Sometimes Windows does not fully flush/reset the DNS cache when connecting/disconnecting from the VPN. Especially if they only put the computer to sleep at night. The Hosts file entry will solve the problem if it is simply DNS.
Forgive me for my lack of networking diction, but does their network and the network that they are VPN-ing into have the same subnet mask or DHCP pool.
For example is their local ip 10.0.0.1 before they connect to the VPN and then your Epicor App server is on 10.0.0.10 on your network that they are VPN-ing to?
I have seen this issue when that is the case. It’s almost as if their computer looks first on their own subnet. @jdewitt6029 could explain it better.
I have seen it with certain VPN setups (assuming this topic was started back up again by user using VPN) where systems get confused when the local network is the same as work. (ex 10.0.0.0/23) Comcast by default now seems to use 10.0.0.0/23 now if you use their equipment. That used to be used pretty much just by businesses but not anymore. So check to see if the user’s network is the same as your work one. Otherwise the system may try to use local first before it tries to use path over vpn no matter how hard you try to tell it otherwise.
Also, if you are attempting to resolve over DNS, i recommend setting the DNS suffix for the domain. Helps.
I have had to at least once create a script for a user to run every time they connected to the vpn to flush out their DNS.
Also, make sure they have permission to read that share location and make sure the VPN is setup to allow the VPN connection to access that share too. That can be controlled through VPN policies usually set on the firewall or vpn provider depending how crazy/secure you set things up. And of course, check firewall rules primarily between private vs public vs domain. So many things to check