Can ping vpn server but not other remote resources

I have set up a Windows 2003 server Standard edition using Remoting
and remote access as a VPN server.
The client is able to connect to the vpnserver, and ping the internal
ip of the vpn server, but not any other server on the lan
Internal nic: 10.18.15.31
External nic: 200.200.166.137

The vpn client is using local ip in the 10.0.0.x range and get
assigned a 10.18.15.x ip from the vpn server

There are no ip conflicts
Attempted to connect to the internal nic using port forwading in our
router, got connected, but still unable to access the other computers
in the network

The server is connected to the internet through an inhouse router
(200.200.166.1)
Settings from Routing and Remote access
if-vpn2 properties
General: enable this computer as s router (Lan and demand-dial
routing), Remote access server
ip: Enable ip routing, allow ip based remote access and demand-dial
connections
Dynamic host configuration protocol
Enable broadcast name resolution, Adapter: LAN
PPP: all checked
ports properties - wan miniport pptp: Remote access connections
(inbound only), demand-dial routing conections (inbound and outbound)


Complete ipconfig and routingtables available at http://andreas.ringdal.no/vpn.html

I have attempted to add a static route in Routing and Remote Access
destination 10.18.0.0
mask 255.255.0.0
Gateway: 10.18.15.31
Interface: lan

IGMP Both interfaces LAN and Internal er set to Router V3 protocol

My theory is that it has something to do with either static routes or
some other setting that blocks routing from the vpn server to the LAN.

Any suggestions?


Andreas

Assign your internal DNS servers (Domain Controllers, typically) as the VPN
client's DNS server. This way, VPN cleints will be using your internal DNS
for name resulution.

-Frank

"Andemann" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
>I have set up a Windows 2003 server Standard edition using Remoting
> and remote access as a VPN server.
> The client is able to connect to the vpnserver, and ping the internal
> ip of the vpn server, but not any other server on the lan
> Internal nic: 10.18.15.31
> External nic: 200.200.166.137
>
> The vpn client is using local ip in the 10.0.0.x range and get
> assigned a 10.18.15.x ip from the vpn server
>
> There are no ip conflicts
> Attempted to connect to the internal nic using port forwading in our
> router, got connected, but still unable to access the other computers
> in the network
>
> The server is connected to the internet through an inhouse router
> (200.200.166.1)
> Settings from Routing and Remote access
> if-vpn2 properties
> General: enable this computer as s router (Lan and demand-dial
> routing), Remote access server
> ip: Enable ip routing, allow ip based remote access and demand-dial
> connections
> Dynamic host configuration protocol
> Enable broadcast name resolution, Adapter: LAN
> PPP: all checked
> ports properties - wan miniport pptp: Remote access connections
> (inbound only), demand-dial routing conections (inbound and outbound)
>
>
> Complete ipconfig and routingtables available at
> http://andreas.ringdal.no/vpn.html
>
> I have attempted to add a static route in Routing and Remote Access
> destination 10.18.0.0
> mask 255.255.0.0
> Gateway: 10.18.15.31
> Interface: lan
>
> IGMP Both interfaces LAN and Internal er set to Router V3 protocol
>
> My theory is that it has something to do with either static routes or
> some other setting that blocks routing from the vpn server to the LAN.
>
> Any suggestions?
>
>
> Andreas
>

DNS is not yet the problem, I can't even ping the internal servers
from the client using ip address. Cannot even reach the DNS servers
from the inside.

Andreas

Frankster wrote:
> Assign your internal DNS servers (Domain Controllers, typically) as the VPN
> client's DNS server. This way, VPN cleints will be using your internal DNS
> for name resulution.

This is routing issue. Have you enable Ip routing?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Andemann" <(E-Mail Removed)> wrote in message news:(E-Mail Removed) oups.com...
I have set up a Windows 2003 server Standard edition using Remoting
and remote access as a VPN server.
The client is able to connect to the vpnserver, and ping the internal
ip of the vpn server, but not any other server on the lan
Internal nic: 10.18.15.31
External nic: 200.200.166.137

The vpn client is using local ip in the 10.0.0.x range and get
assigned a 10.18.15.x ip from the vpn server

There are no ip conflicts
Attempted to connect to the internal nic using port forwading in our
router, got connected, but still unable to access the other computers
in the network

The server is connected to the internet through an inhouse router
(200.200.166.1)
Settings from Routing and Remote access
if-vpn2 properties
General: enable this computer as s router (Lan and demand-dial
routing), Remote access server
ip: Enable ip routing, allow ip based remote access and demand-dial
connections
Dynamic host configuration protocol
Enable broadcast name resolution, Adapter: LAN
PPP: all checked
ports properties - wan miniport pptp: Remote access connections
(inbound only), demand-dial routing conections (inbound and outbound)


Complete ipconfig and routingtables available at http://andreas.ringdal.no/vpn.html

I have attempted to add a static route in Routing and Remote Access
destination 10.18.0.0
mask 255.255.0.0
Gateway: 10.18.15.31
Interface: lan

IGMP Both interfaces LAN and Internal er set to Router V3 protocol

My theory is that it has something to do with either static routes or
some other setting that blocks routing from the vpn server to the LAN.

Any suggestions?


Andreas

You say that the client machine has a local IP in the 10.0.0.0 range. Is
it using an 8-bit netmask?

If it is, it is not likely to send any 10.x.y.z packets across the VPN
link. It will regard them as local and try to deliver them directly "on the
wire".


"Andemann" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
>I have set up a Windows 2003 server Standard edition using Remoting
> and remote access as a VPN server.
> The client is able to connect to the vpnserver, and ping the internal
> ip of the vpn server, but not any other server on the lan
> Internal nic: 10.18.15.31
> External nic: 200.200.166.137
>
> The vpn client is using local ip in the 10.0.0.x range and get
> assigned a 10.18.15.x ip from the vpn server
>
> There are no ip conflicts
> Attempted to connect to the internal nic using port forwading in our
> router, got connected, but still unable to access the other computers
> in the network
>
> The server is connected to the internet through an inhouse router
> (200.200.166.1)
> Settings from Routing and Remote access
> if-vpn2 properties
> General: enable this computer as s router (Lan and demand-dial
> routing), Remote access server
> ip: Enable ip routing, allow ip based remote access and demand-dial
> connections
> Dynamic host configuration protocol
> Enable broadcast name resolution, Adapter: LAN
> PPP: all checked
> ports properties - wan miniport pptp: Remote access connections
> (inbound only), demand-dial routing conections (inbound and outbound)
>
>
> Complete ipconfig and routingtables available at
> http://andreas.ringdal.no/vpn.html
>
> I have attempted to add a static route in Routing and Remote Access
> destination 10.18.0.0
> mask 255.255.0.0
> Gateway: 10.18.15.31
> Interface: lan
>
> IGMP Both interfaces LAN and Internal er set to Router V3 protocol
>
> My theory is that it has something to do with either static routes or
> some other setting that blocks routing from the vpn server to the LAN.
>
> Any suggestions?
>
>
> Andreas
>