Internal interface in RRAS non-operational

[Guest]

My internal interface for RRAS on my windows 2000 server is non-operational.
What does this mean? DNS works because I can try to ping microsoft.com from
a client computer and the server gives an IP but I get timed out errors. I
can't browse the internet from my clients. DHCP is also working. I don't
know what this means and my server is usless without it, it seems. Any
advice would be of great help.

Aaron

 

[Robert L [MS-MVP]]

can the server access the internet?

--
For more and other information, go to http://www.ChicagoTech.net

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.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
Networking Solutions, http://www.chicagotech.net/networksolutions.htm
VPN Solutions, http://www.chicagotech.net/vpnsolutions.htm
VPN Process and Error Analysis, http://www.chicagotech.net/VPN process.htm
VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
This posting is provided "AS IS" with no warranties.

 

[Guest]

Yes, the server has internet access. I deleted the internal interface and
tried to recreate it, but the server says that no new interfaces are
available.

Aaron

 

[Bill Grant]

The internal interface is the interface to which your remote access
clients connect. It will not become operational until a remote client
connects to this RRAS server.

 

[Guest]

Thanks. Do you mean remote clients incoming from the internet/dialup or my
clients that connect directly to the server through the LAN? Also, might you
have any advice on why I can't connect to the internet from my LAN client
computers, which are running XP Pro. I can ping my server's DNS name and
browse the server from the clients. I just can't connect to the internet
from the LAN clients. My network is as follows: Cable modem to server to hub
to two different routers, one wired and one wireless, then all client
computers are connected to the routers. This setup has worked in the past on
an older server I had and previously on this server. I reinstalled the Win
2000 Server and now I can't get the server to share the internet access. I
tried bypassing my router and connecting my client computer to the hub, but
the ping error just changes to destination host unreachable from request
timed out from behind my router. Both routers get IP addresses from my
server and I can join the domain from my LAN clients. I fear a hardware
problem, but if someone has an idea that would be cool. Thanks again.

Aaron

 

[Bill Grant]

The internal interface is only concerned with remote clients. LAN clients
use the LAN interface of the server.

How your LAN clients access the Internet depends on your setup. What is
the default gateway setting on the LAN clients? Do they use the server as
their gateway or a router?

 

[Guest]

I think the gateway setting was the problem. I put my servers ip private/LAN
address in as the gateway IP when I setup DHCP on my server and everything
works now. I joined all my LAN clients to the domain and they now have
internet access. Sweet. Thanks for all your help. I was starting to get
frustrated.