Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...I wish I knew about this site years ago. It would have saved me a lot of heartaches..."

Geography

Where in the world do Tek-Tips members come from?
EntilzaSte (TechnicalUser)
12 Aug 03 11:57
Hi,

We have a remote site to which we need to create a "as needed" connection.  We have attempted to use a vpn connection through our respective firewalls, but the remote end could not handle it (old software that wont be replaced).  I remembered reading about a feature of RRAS in Win2K server that handles demand dialing really well.

So anyway, I set it up and am now having the following problem.  When a machine on the lan attempts to ping a remote machine (at the other end of the remote dial) it times out (ping **** /t) .  The link is initiated on the RRAS server, and the rras box CAN ping around the remote network.  Machines on my lan cant ping the remote end.

I realise that its bound to be something really silly, but I cant spot it at all.  Can anyone help?

Thanks

Steve
 
PorkyPete (Programmer)
16 Oct 03 18:34
Steve
This will always happen on the first ping to the outside world as Ping will not wait for the connection to be established. If you wait about 30 secs for the dial up to get sorted, a second ping should then work. You will see this if you are using Dial On Demand for a shared internet connection as well - Explorer (or whatever) will always return page not found as it can't be bothered waiting, the second fetch should work OK. This is a known limitation of DOD - see Microsoft knowledge base for more info - search for ICS.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close