We are hosting an application for a remote client. Right now the clients VPN into through Microsoft SBS 2003 and attempt to access the application running on the same server. We have two significant issues:
1) The application we're running has a proprietary database, and a client/server configuration. When the users VPN into the network and open their application client they need to first associate their client with the server side database. Unfortunately when they try this (by IP or by server name) they cannot find the server.
We tried some preliminary testing... When the WAN users VPNs into the network they can see their own local domain through My Network places but cannot see the remote domain we've setup for them. They can ping the remote domain, and if they enter the server in the address bar (i.e. \\remoteserver) they can access the server.
2) We have very poor performance over the WAN. Both sides have Dual T1 lines, and we have monitored the server and run the application locally to address any hardware issues (i.e. CPU, RAM, etc.). I suspect that there is some kind of DNS / WINS replication issues; however, I believe that if they VPN into our network they should be receiving the correct IP Config from the remote domain... right?
Obviously there are no easy answers here, and this response is going to take some attention from experienced EE members. Because of this, I'm assigning this question 500 points.