RAS Configuration

  • Thread starter Thread starter Jon Bone
  • Start date Start date
J

Jon Bone

Recently we have moved offices taking the servers to their new home.

I am trying to get RAS working since the move and am have a little trouble.
Previously we used to us ISA server to to the routing and firewall but have
changed to a hardware firewall and router, all the appropriate holes have
been punched in the firewall.

What happens is you connect successfully to the server and are able to ping
machines and generally do stuff for about 2 minutes, after that the systray
icon maintains you are connected but you are unable to ping any servers on
the network either by name or ip.

As I have remote users whoe need to use this service on a day to day basis
(and I'd like to be one of them) I would appreciate it if someone could
point me in the direction of the part I'm missing.

Thanks,

Jon.
 
Are there any events logged on the server or client? Have there been any
session timeout or idle timeout set in the server or client? What is the OS
running on the server and on the client?

--

Thanks
Sharoon
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi Sharoon,

Thanks for your reply. Both the client and server are running Windows 2000
Server. There are no idle timeouts on either the client or server and I can
find no events in the app log regarding ras.

The connection appears to be still connected when I check the properties
however I am unable to ping any server within the network.
 
I have the same problem at home when connecting to my work via pptp. I have
two routers doing NAT inline to segregate my wireless traffic. But my
problem did not start until I switched out one my routers, if I put my old
router back it works fine. Sound familiar. I know they are home routers,
but it sounds so similar and routers are no longer rocket science.

I would switch out the network cables to your firewall and possibly consider
the fact it may also be the firewall itself seeing as how it worked fine
before. You can always count on the last thing that is changed to be the
problem, if your lucky.

You could also change the nic on your server or update the drivers. (I doubt
this is it, but you never know.)
 
Can you check the routes if there are any changes in it for a period of 2-3
minutes? Also check the tracert output which will give details on where the
packets are being discarded.
--

Thanks
Sharoon
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top