VPN Win2k Server - Why won't it work? Out of ideas

  • Thread starter Thread starter dkurman
  • Start date Start date
D

dkurman

Here's the setup

Office:
1 cable modem and router (192.168.2.1 default gateway)
1 server with 1 NIC (192.168.2.17)

Home
Windows XP Pro
ip range 10.0.0.x
Use default gateway on remote unchecked

I am able to login to the VPN with
username/password/domain. I receive an ip of 192.168.2.20
and can ping the server. I cannot browse any shared
folders and cannot configure my Outlook to use MS Exchange
on my server.

I've read all the posts tried it all...what am I missing?

If someone can reply via private mail I'd appreciate it. I
don't know what else to do.

-David Kurman
(e-mail address removed)
 
Hi David,

dkurman said:
Here's the setup

Office:
1 cable modem and router (192.168.2.1 default gateway)
1 server with 1 NIC (192.168.2.17)

Home
Windows XP Pro
ip range 10.0.0.x
Use default gateway on remote unchecked

I am able to login to the VPN with
username/password/domain. I receive an ip of 192.168.2.20
and can ping the server. I cannot browse any shared
folders and cannot configure my Outlook to use MS Exchange
on my server.
Click to expand...

Did you try to create the shares using the servers IP address? I'm using VPN
from home, too, and first of all I have to use the raw IP address (no DNS or
WINS over my VPN), second I have to recreate the shares everytime by
providing an explicit user name and password due to my "offline" windows
login. I have to mention here, that I'm not using Windows VPN but I'm sure
the problems are pretty much the same.

Christoph
 
Can you ping machines on the office LAN by IP address? Does the office
network use DNS and/or WINS? Does your client receive the correct DNS/WINS
addresses when it connects?
 
I have the same issue. I have to trick my home computer using nslookup
("server office_dns.domain.com") in order to map drives to machines on the
network. An error is given when attempting to browse the network via
Network Neighborhood. In addition, I noticed the DNS server list granted to
the VPN connection is the exact *reverse* of the list in the server's DHCP
settings.

Exchange will not work through VPN for me as well.

Our setup is DSL with a Netgear broadband router with 1723 open to the VPN
server.
 
Aside from the reverse DNS entry, I have an answer to my own questions now.
After reading some posts below, I noticed the repetition of the fact that
name resolution does not occur over a VPN connection and that w.x.y.z format
should be used for mapping drives.
 
DNS will work, as long as the client has the correct DNS address and the
correct domain suffix. If it is not getting the correct values from the VPN
server, set them manually in the connection properties of the client.
 
Should the client use the public IP address of the VPN server or the
internal network address for the VPN server? The public IP is actually a
router that forwards port 1723 to the VPN server with an internal address of
192.168.x.y.

Thanks.
 
Additionally, do you know why the DHCP settings from the VPN server override
the manual settings on the client machine? If I set the VPN connection to
have a DNS server of w.x.y.z, an ipconfig /all after connection shows that
the manual settings are merely appended to the list from the VPN server.

Also, as noted before, the DNS list is exactly the reverse of the order
given to client machines on the internal work network. Any ideas why?
 
It depends on how you configure the client. Set it to use manual DNS
config (not obtain from server), then go into advanced TCP/IP config and
manually set the DNS IP addresses and domain suffix(es) you want the
connection to use.
 
Thanks for all your help so far, by the way.

The VPN server is now set to issue from a static pool and the test client
outside the business is using manual DNS settings to the IP of the machine
on the other side of the firewall--that is, a private IP of 192.168.etc.
Still no name resolution. I then changed the DNS configuration to the
external IP address--still did not work.

The name of the VPN server itself resolves and I can map shares without
using the IP address, but no other machines resolve.
 
Back
Top