Z
Zul J
Hi,
We are running RAS only (router is not enable) on a Windows Server 2003 SP1.
The issue that we are having is that only certain pc or notebook having no
routing issue when connecting through the RAS server but some pc are having
problem with routing where the routes stops at the RAS server (the ip or
gateway of the dial-in interface), it can't go further than that, in other
words, it can't get connected to other servers. They all can authenticate
successfully but some are having routing issue.
I have tested where I use the same login name on 2 pc (same OS, same
patches) but only one works. I use a different login on the 2 pc but still
only one works (the same pc that did not work previously). It seems that the
issue caused by the pc or somehow the RAS server rejected the pc.
Help...
Regards,
Zul
We are running RAS only (router is not enable) on a Windows Server 2003 SP1.
The issue that we are having is that only certain pc or notebook having no
routing issue when connecting through the RAS server but some pc are having
problem with routing where the routes stops at the RAS server (the ip or
gateway of the dial-in interface), it can't go further than that, in other
words, it can't get connected to other servers. They all can authenticate
successfully but some are having routing issue.
I have tested where I use the same login name on 2 pc (same OS, same
patches) but only one works. I use a different login on the 2 pc but still
only one works (the same pc that did not work previously). It seems that the
issue caused by the pc or somehow the RAS server rejected the pc.
Help...
Regards,
Zul