ShadowColossus
asked on
Setup Remote Access/Microsoft VPN Server
Hi.
My VPN server crashed so I just configured Microsoft Windows 2003 VPN server Remote Access on another server but I have been running into some problems.
I can VPN and logged into the server and I could remote desktop into the other machines in the network block. However, I can't seem to get my mail using microsoft outlook express anymore. I was able to do this with the old Mircosoft VPN server. I must have missed something in my VPN setup. Please help me out.
My VPN server crashed so I just configured Microsoft Windows 2003 VPN server Remote Access on another server but I have been running into some problems.
I can VPN and logged into the server and I could remote desktop into the other machines in the network block. However, I can't seem to get my mail using microsoft outlook express anymore. I was able to do this with the old Mircosoft VPN server. I must have missed something in my VPN setup. Please help me out.
ASKER
I believe routing is enabled from properties i could see that LAN and demand dial routing is enabled and Remote Access server is enabled. I could ping the email server. With old vpn i could check my mail through microsoft outlook, with this new vpn server i can't.
What error do you get?
ASKER
"The connection to the microsoft exchange server is unavalaible." Hmm....it seems that i can ping the IP of the exchange server but i can't ping the name of the server. Do you know how i can resolve the name of the server to the IP?
This question comes up frequently and I have never seen a real fix. Though it shouldn't be necessary, you can usually resolve by adding the server name and IP to the LMHosts file of the conecting computer. See details as per the following instructions:
Setting up an LMHosts file.
There are a few oddities with the file, have a look at the following:
-Lmhosts file is useful for NetBIOS name resolution where other solutions are not available.
-LMHosts is located in the Windows directory under c:\Windows (or WINNT)\System32\Drivers\Et
192.168.0.101 CompName #PRE
-Hit enter when each line is complete (important), then save the file without a file extension. To be sure there is no extension ,when saving enclose in quotations like "LMHosts".
-PRE has to be capitalized, however you do not need it, though should give you faster resolution where it is "pre-loaded"
-use a Tab between entries in a line rather than spaces (recommended but not necessary)
-if adding the domain and or domain controller the # of spaces used is even critical. See:
http://support.microsoft.com/kb/q180094/
see also:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnfd_lmh_qxqq.mspx?mfr=true
ps- To check your LMHosts file entries are accepted at a command prompt enter
nbtstat -R
to purge and reload the local name cache
then enter
nbtstat -c
to display the current name cache which should include your LMHosts file entries.
Note; the nbtstat "switches" R & c are case sensitive.
The names will only show up if you used the 'PRE' option, or if not, if you have used the name with a ping or similar command enabling them to be cached.
Setting up an LMHosts file.
There are a few oddities with the file, have a look at the following:
-Lmhosts file is useful for NetBIOS name resolution where other solutions are not available.
-LMHosts is located in the Windows directory under c:\Windows (or WINNT)\System32\Drivers\Et
192.168.0.101 CompName #PRE
-Hit enter when each line is complete (important), then save the file without a file extension. To be sure there is no extension ,when saving enclose in quotations like "LMHosts".
-PRE has to be capitalized, however you do not need it, though should give you faster resolution where it is "pre-loaded"
-use a Tab between entries in a line rather than spaces (recommended but not necessary)
-if adding the domain and or domain controller the # of spaces used is even critical. See:
http://support.microsoft.com/kb/q180094/
see also:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnfd_lmh_qxqq.mspx?mfr=true
ps- To check your LMHosts file entries are accepted at a command prompt enter
nbtstat -R
to purge and reload the local name cache
then enter
nbtstat -c
to display the current name cache which should include your LMHosts file entries.
Note; the nbtstat "switches" R & c are case sensitive.
The names will only show up if you used the 'PRE' option, or if not, if you have used the name with a ping or similar command enabling them to be cached.
ASKER
i can ping the name of the mail server when I console into the machine, but once I vpn in, I can't ping the name of the mail server anymore. Will the solution above still fix my problem?
Can u ping to other servers or hosts through the VPN Server by using the server name ????
ASKER
hmm actually no i can't ping and server names when i logged into the vpn server (but i can when i console into the machine)
ok check the DNS Setting of the VPN Server as well as put a nslookup for the exchange server from VPN
then let me know if you get any error
then let me know if you get any error
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all of the help. Got it working.
Do you have the correct routing tables on the VPN server and on the e-mail server?