Win2003 - Simple Quest, big Problem - Can't ping anywhere

[Guest]

Hello,
Here is my Dilemna, I have uninstalled RRAS on a Windows 2003 server SP1 and
reinstalled it again without touching anything. I have a Windows XP Pro
machine I am trying to dial in on and connect. I get connected to the ras
server just fine, but I can only ping this server's NIC which is an inside
address. If I try to ping my RDP server which is on the same address space I
get request time out. Here is some more detail.
The three static addresses I have configured are part of the same server
network that is on the inside. The network they are on is a 10.10.48.*
255.255.254.0 I notice when I configure the static clients with ras as only
three addresses .240-.242 it automatically configures the subnet as
255.255.255.252

Now when I connect in and do a ipconfig/all I get one of the three addresses
above, my dns and wins server info is correct but my subnet shows
255.255.255.255 and the gateway shows the ip address that was given to me
from the ras in which this case it was .241.

Any help would be greatly appreciated,


It almost seems like the TCP/IP stack does not want to route correctly. I am
thinking of uninstalling/reinstalling TCP/IP but the other services on this
machine are working fine.

 

[Robert L [MVP - Networking]]

Have you enabled IP routing? This link may help

routing issues on vpnResolutions: 1) if you have two NICs in the VPN server, you may need to enable IP Routing. To do this, go to the RRAS>the Properties of the server>IP, ...
http://www.chicagotech.net/routingissuesonvpn.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
Hello,
Here is my Dilemna, I have uninstalled RRAS on a Windows 2003 server SP1 and
reinstalled it again without touching anything. I have a Windows XP Pro
machine I am trying to dial in on and connect. I get connected to the ras
server just fine, but I can only ping this server's NIC which is an inside
address. If I try to ping my RDP server which is on the same address space I
get request time out. Here is some more detail.
The three static addresses I have configured are part of the same server
network that is on the inside. The network they are on is a 10.10.48.*
255.255.254.0 I notice when I configure the static clients with ras as only
three addresses .240-.242 it automatically configures the subnet as
255.255.255.252

Now when I connect in and do a ipconfig/all I get one of the three addresses
above, my dns and wins server info is correct but my subnet shows
255.255.255.255 and the gateway shows the ip address that was given to me
from the ras in which this case it was .241.

Any help would be greatly appreciated,


It almost seems like the TCP/IP stack does not want to route correctly. I am
thinking of uninstalling/reinstalling TCP/IP but the other services on this
machine are working fine.

 

[Guest]

Yes, I have enabled IP Routing via the options in Routing and Remote Access
properties. I have also turned on the option in the registry.

Given the information below, would I have to add a couple access lists to my
switch that this RAS server plugs in to in order for those addresses to be
able to ping other machines in the network? I thought this was a fairly
simple process when I used to do this in the past. This server is behind the
firewall and the addresses that are bing handed out to the clients (3 avail)
are addresses from the same network all of the servers are on. Is there
anything I need to configure in the IGMP or OSPF sections? The client once
connected is hitting a brick wall and not getting past the internal nic of
the ras server. This server only has (and always had) one nic hooked up.
There are two nics in this server but I've always had one disabled. When I
set up the RRAS service, I pick the active one when it asks which network
adapter.

Thanks for your response,

 

[Robert L [MVP - Networking]]

Post back with the routing table here may help.

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
Yes, I have enabled IP Routing via the options in Routing and Remote Access
properties. I have also turned on the option in the registry.

Given the information below, would I have to add a couple access lists to my
switch that this RAS server plugs in to in order for those addresses to be
able to ping other machines in the network? I thought this was a fairly
simple process when I used to do this in the past. This server is behind the
firewall and the addresses that are bing handed out to the clients (3 avail)
are addresses from the same network all of the servers are on. Is there
anything I need to configure in the IGMP or OSPF sections? The client once
connected is hitting a brick wall and not getting past the internal nic of
the ras server. This server only has (and always had) one nic hooked up.
There are two nics in this server but I've always had one disabled. When I
set up the RRAS service, I pick the active one when it asks which network
adapter.

Thanks for your response,

 

[Guest]

Hello,
Just to give a little more info, When I do a route print from the server the
correct routes are in there. When I do a route print on my laptop when dialed
in, I only get the info below. Nothing really pointing to the 10.10.48.0
network as a whole. I noticed under interfaces configuration in RRAS, there
is a Local Area connection and then there is a Internal Connection which is
assigned the first of the three static addresses I put in the pool .240. You
will see in the routing table info below (client dialied in)that it specified
that address but nothing else. .242 is the assigned address to the client.

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.10.48.242 10.10.48.242 1
10.10.48.240 255.255.255.255 10.10.48.242 10.10.48.242 1
10.10.48.240 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.10.48.242 10.10.48.242 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.10.48.242 10.10.48.242 1
255.255.255.255 255.255.255.255 10.10.48.242 10.10.48.242 1
255.255.255.255 255.255.255.255 10.10.48.242 2 1
Default Gateway 10.10.48.242