RAS connection cannot ping

you mentioned he can dial in, connect and authenticate just fine,[I assume after authentation, he logs in]. If he logs into the domain can he browse the network and find other computers via My Network Places? Does he have access to shared resources, [??? is there a problem accessing resources???] {ping is a utility not a requirement.] Yes, inability to ping within the LAN and out to the WAN indicates a problem in connectivity and may be due to the computer's NIC card and MAC address not showing when the IPconfig/all utility is run. The NIC should be shown, not a PPP adapter.

After further testing, it only seems to happen to this one user. I cannot find anything in his profile that would cause this, so I deleted his username and recreated it. Guess what, it still does the same thing. He cannot access any network resources at all. So for now I am having him use someone else's logon as a temporary fix. I am sure it is something very stupid that I have overlooked, but I have been looking at it for too long to find a solution today. I would still welcome any fresh ideas.

ok..when you run ipconfig/all from the command prompt what is the NIC "Name" & MAC address showing? Is it the NIC installed on the computer? If not, That is most likely the problem. PPP adapter isn't the NIC card installed on the computer.

The NIC card is the one showing when I type Ipconfig/all. This user belongs to the Domain Users and everyone groups. What is really weird is that other users can access network resources using RAS from that same computer, but he can't. I even deleted his account and copied one that works to a new account for him and it still does not work.

The information you have given is not enough to resolve your issue. What scope have you configured on the RAS service, are you using DHCP to assign the addresses? Have you enabled the clients to access the network or just the local PC? How many concurrent connections do you have? How many addresses are in the scope.

PPP authentication is a layer 2 process, and therefore successful communication just means layer 2 is successfully communicating, but not IP - layer 3.

You can however try the following: Assign another subnet to the scope (one of the private addresses, 192.168.1.0/24 for RAS).

let the machine specify the ip address to use. You will probably want to specify the WINS / DNS servers (if you have them) for name resolution

let the client access the whole network. For windows NT, I have sometimes found it necessary to download RRAS from the microsoft site for successful routing. This could be your issue. You have to reapply your service pack after installing RRAS, don't even attempt to dial-in before you re-apply the service pack

if this doesn't work, post the details back here.

This question was closed by the author