Subnet Mask problem?



I have configured Remote Access on a Windows Server 2003 machine.

I can do a VPN connection remotely by connecting to the server's IP address
without any problems - it connects successfully. Howevere, I can not ping the
server's internal ip address, or any other internal addresses on the network.

I believe it is because of the subnet mask that I am being assigned, but I
may be incorrect. My ipconfig info for the PPP adaptor is as follows:

PPP adapter ECI:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . :
Subnet Mask . . . . . . . . . . . :
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

The subnet mask of the internal network is,, but the vpn
client is beign assigned Is this the cause of my problem
with not being able to ping or browse the internal network once connected? If
so, then how do I make it assign the proper submnet mask. If not, then what
are possible causes? Thanks in advance.



Robert L [MS-MVP]

the mask looks ok. it could be the VPN settings issue. quoted from
Why my XP VPN client's subnet mask is

This is by design. Since this connection is point to point, not point to net
or net to net, VPN server assigns mask to the client.
For more and other information, go to

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
Networking Solutions,
VPN Solutions,
VPN Process and Error Analysis, process.htm
VPN Troubleshooting,
This posting is provided "AS IS" with no warranties.


I have the same problem. The only thing that is different is that I have an
NT4 server instead. Can anyone help me to solve it?

"GreginBR" skrev:



Bill Grant

The subnet mask is not the problem. That just indicates that you are
using a point to point connection. All traffic for the LAN should be going
over the VPN connection and the server should act as a proxy for the remote
client on the LAN.

Communication with machines on the LAN should just work. From memory
there was an option to disable this in NT (ie communicate with the server
only), but I haven't used NT for a while so I could be wrong about that.

The usual cause of this is firewall settings on the server and/or the
remote client.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question