Server 2003 VPN browsing problem

I have 2 nics on server 2003 vpn. public 71.41.x.x private 192.168.15.103

DHCp assigns to VPN client :IP 192.168.15.130 Server 192.168.15.129 subnet
255.255.255.255
After connecting i cannot browse the remote network nor can i ping any
computer on the remote network. Any ideas would be appreciated.
--
TS

A VPN client just gives you an IP connection. It doesn't automatically
give you name resolution.

You should be able to ping a LAN machine by its IP address. You should
also be able to ping by FQDN if the LAN is running DNS. To ping by Netbios
name you will probably need WINS or an LMHOSTS file on the client. Broadcast
name resolution doesn't work across routers or WAN links.


"TS" <(E-Mail Removed)> wrote in message
news:5ACEA3A7-ACB7-4374-BACD-(E-Mail Removed)...
>I have 2 nics on server 2003 vpn. public 71.41.x.x private
>192.168.15.103
>
> DHCp assigns to VPN client :IP 192.168.15.130 Server 192.168.15.129
> subnet
> 255.255.255.255
> After connecting i cannot browse the remote network nor can i ping any
> computer on the remote network. Any ideas would be appreciated.
> --
> TS

I do have DNS and Wins running. Is this normal to have a subnet of
255.255.255.255? Seems to me that i'm not even on the same subnet as the
remote lan. My remote lan is 255.255.255.0
Problem is if this is the case i can't seem to change the subnet on the VPN
client.
Maybe i'm completely wrong?
--
TS


"Bill Grant" wrote:

> A VPN client just gives you an IP connection. It doesn't automatically
> give you name resolution.
>
> You should be able to ping a LAN machine by its IP address. You should
> also be able to ping by FQDN if the LAN is running DNS. To ping by Netbios
> name you will probably need WINS or an LMHOSTS file on the client. Broadcast
> name resolution doesn't work across routers or WAN links.
>
>
> "TS" <(E-Mail Removed)> wrote in message
> news:5ACEA3A7-ACB7-4374-BACD-(E-Mail Removed)...
> >I have 2 nics on server 2003 vpn. public 71.41.x.x private
> >192.168.15.103
> >
> > DHCp assigns to VPN client :IP 192.168.15.130 Server 192.168.15.129
> > subnet
> > 255.255.255.255
> > After connecting i cannot browse the remote network nor can i ping any
> > computer on the remote network. Any ideas would be appreciated.
> > --
> > TS
>
>

subnet 255.255.255.255 is not issue here. Can you ping a remote computer by
IP? If not, post the routing table here. Also check these search results.

tcp/ip settings for vpnx.x.x; Subnet Mask - 255.255.255.255. This is because
your VPN server doesn't have DHCP to assign IP so that the the VPN server
uses APIPA to provides an ...
www.chicagotech.net/vpntcpipsettings.htm

VPN IssuesQ: I just setup VPN on my windows server for my clients to
VPN into my network. The one issue I'm noticing is that all their DNS
requests flow through the ...
www.chicagotech.net/vpn.htm



--
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
"TS" <(E-Mail Removed)> wrote in message
news:B043DA44-CEB6-4859-AC7F-(E-Mail Removed)...
>I do have DNS and Wins running. Is this normal to have a subnet of
> 255.255.255.255? Seems to me that i'm not even on the same subnet as the
> remote lan. My remote lan is 255.255.255.0
> Problem is if this is the case i can't seem to change the subnet on the
> VPN
> client.
> Maybe i'm completely wrong?
> --
> TS
>
>
> "Bill Grant" wrote:
>
>> A VPN client just gives you an IP connection. It doesn't automatically
>> give you name resolution.
>>
>> You should be able to ping a LAN machine by its IP address. You
>> should
>> also be able to ping by FQDN if the LAN is running DNS. To ping by
>> Netbios
>> name you will probably need WINS or an LMHOSTS file on the client.
>> Broadcast
>> name resolution doesn't work across routers or WAN links.
>>
>>
>> "TS" <(E-Mail Removed)> wrote in message
>> news:5ACEA3A7-ACB7-4374-BACD-(E-Mail Removed)...
>> >I have 2 nics on server 2003 vpn. public 71.41.x.x private
>> >192.168.15.103
>> >
>> > DHCp assigns to VPN client :IP 192.168.15.130 Server 192.168.15.129
>> > subnet
>> > 255.255.255.255
>> > After connecting i cannot browse the remote network nor can i ping any
>> > computer on the remote network. Any ideas would be appreciated.
>> > --
>> > TS
>>
>>

--


"Robert L. (MS-MVP)" wrote:

> subnet 255.255.255.255 is not issue here. Can you ping a remote computer by
> IP? If not, post the routing table here. Also check these search results.

No i cannot ping any remote computers from the vpn client.

DHCP IP addresses from the VPN Server are correct on the VPN client.
I just can't browse the remote network or ping the private ip's
I will post the Routing table from the server.
Thanks
>
> tcp/ip settings for vpnx.x.x; Subnet Mask - 255.255.255.255. This is because
> your VPN server doesn't have DHCP to assign IP so that the the VPN server
> uses APIPA to provides an ...
> www.chicagotech.net/vpntcpipsettings.htm
>
> VPN IssuesQ: I just setup VPN on my windows server for my clients to
> VPN into my network. The one issue I'm noticing is that all their DNS
> requests flow through the ...
> www.chicagotech.net/vpn.htm
>
>
>
> --
> 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
> "TS" <(E-Mail Removed)> wrote in message
> news:B043DA44-CEB6-4859-AC7F-(E-Mail Removed)...
> >I do have DNS and Wins running. Is this normal to have a subnet of
> > 255.255.255.255? Seems to me that i'm not even on the same subnet as the
> > remote lan. My remote lan is 255.255.255.0
> > Problem is if this is the case i can't seem to change the subnet on the
> > VPN
> > client.
> > Maybe i'm completely wrong?
> > --
> > TS
> >
> >
> > "Bill Grant" wrote:
> >
> >> A VPN client just gives you an IP connection. It doesn't automatically
> >> give you name resolution.
> >>
> >> You should be able to ping a LAN machine by its IP address. You
> >> should
> >> also be able to ping by FQDN if the LAN is running DNS. To ping by
> >> Netbios
> >> name you will probably need WINS or an LMHOSTS file on the client.
> >> Broadcast
> >> name resolution doesn't work across routers or WAN links.
> >>
> >>
> >> "TS" <(E-Mail Removed)> wrote in message
> >> news:5ACEA3A7-ACB7-4374-BACD-(E-Mail Removed)...
> >> >I have 2 nics on server 2003 vpn. public 71.41.x.x private
> >> >192.168.15.103
> >> >
> >> > DHCp assigns to VPN client :IP 192.168.15.130 Server 192.168.15.129
> >> > subnet
> >> > 255.255.255.255
> >> > After connecting i cannot browse the remote network nor can i ping any
> >> > computer on the remote network. Any ideas would be appreciated.
> >> > --
> >> > TS
> >>
> >>
>
>

Ok apparantly one of those things that everything is set correctly yet does
not work.
Uninstall then reinstall and bingo.
It works now.
I disabled RRAS then reinstalled .
Instead of using DHCP this time i used Static assigned ip addresses.
The client can now ping the the remote network nodes, and i actually mapped
network drives and started transfering files. What's different before
compared to now? Only the static assigned Ip addresses for the vpn clients
and the defaults with RRAS.

I have had this problem for three weeks now and was looking all over the
internet for answers and found none. I hope this helps someone else.