M
Mike Morgan
I'm having a problem with our win2k routing and remote access server. I can
get the dialup clients to connect, but they can't see past the remote access
server. The server can ping the lan and the remote client. But, the client
can't ping anything on the lan besides the remote access server. Tracert
reveals that the route dies at the RAS server. How do I make the RAS server
route traffic to and from the lan for the clients? I used the wizard to
setup RRAS on the server. I'm using DHCP to assign the remote client
addresses. The clients are pulling IPs fine, but they aren't getting the DNS
server IP for some reason. Authentication is done with IAS. I do have ISA
installed in cache mode for a web proxy. It seems to work fine. I found an
article at support.microsoft.com that said to turn the IPEnableRouter DWORD
to 1 in the registry. I set that and rebooted with no joy. Have I missed
something obvious? Is there a problem with RRAS coexisting with ISA? If so,
is it fixable? I'd really like to leave all of this on the same machine if
possible.
get the dialup clients to connect, but they can't see past the remote access
server. The server can ping the lan and the remote client. But, the client
can't ping anything on the lan besides the remote access server. Tracert
reveals that the route dies at the RAS server. How do I make the RAS server
route traffic to and from the lan for the clients? I used the wizard to
setup RRAS on the server. I'm using DHCP to assign the remote client
addresses. The clients are pulling IPs fine, but they aren't getting the DNS
server IP for some reason. Authentication is done with IAS. I do have ISA
installed in cache mode for a web proxy. It seems to work fine. I found an
article at support.microsoft.com that said to turn the IPEnableRouter DWORD
to 1 in the registry. I set that and rebooted with no joy. Have I missed
something obvious? Is there a problem with RRAS coexisting with ISA? If so,
is it fixable? I'd really like to leave all of this on the same machine if
possible.