Re: [TCLUG:4167] DIALD & IP Forwarding

["Paul Hocker" <phocker@visi.com>]

Well, that did it!!! So for everyone out there who has ever had this
problem. Make sure that you have DNS running on the server, and that the
client machines all have to do name lookups before anything else. Also, make
sure that you have a HOSTS/LMHOSTS file setup on your win clients to ensure
that they won't startup diald on the name lookups. If anybody needs any
guidance in this area, please let me know.

Thanks for everybody's help.

Paul.

-----Original Message-----
From: Paul Hocker <phocker@visi.com>
To: tclug-list@listserv.real-time.com <tclug-list@listserv.real-time.com>
Date: Monday, February 15, 1999 6:48 PM
Subject: Re: [TCLUG:4167] DIALD & IP Forwarding


>Thanks, I will try that. However I think that I was having problems with
>that before because on every DNS request, even on the local network, it
>would dial out to the internet.
>
>Paul
>
>-----Original Message-----
>From: John J. Trammell <trammell@nitz.hep.umn.edu>
>To: tclug-list@listserv.real-time.com <tclug-list@listserv.real-time.com>
>Date: Monday, February 15, 1999 10:22 AM
>Subject: Re: [TCLUG:4167] DIALD & IP Forwarding
>
>
>>Hello all:
>>
>>Scott K. Johnson <skj@visi.com> wrote (in part):
>>
>>> My experience with IP Forwarding and dial on demand is that the
>>> first request triggers the modem to dial and connect, and that
>>> first connection request almost always times out.
>>>
>>> I'm thinking it is something to do with the time it takes for the
>>> modem to dial, connect and establish a ppp connection...
>>
>>That it may, but it doesn't have to.  :-)
>>
>>IANANetworkAdmin, but my understanding is that if the "triggering"
>>request is a name resolution request (for your non-static IP account),
>>everything can be OK.
>>
>>If the triggering request is, say, an FTP request, the first packet
>>goes out with your default (bogus) system IP address.  The resulting
>>PPP (or whatever) connection clobbers your bogus default IP address,
>>so the response to that first packet can't get back to your machine,
>>because its address is different.
>>
>>IIRC, the solution is to empty out your /etc/hosts so that the first
>>packet out the door is a DNS request.
>>
>>ISTR that a better explanation (written by One Who Knows) is in the
>>Diald FAQ.
>>
>>Peace,
>>John
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tclug-list-unsubscribe@listserv.real-time.com
>>For additional commands, e-mail: tclug-list-help@listserv.real-time.com
>>Try our website: http://tclug.real-time.com
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tclug-list-unsubscribe@listserv.real-time.com
>For additional commands, e-mail: tclug-list-help@listserv.real-time.com
>Try our website: http://tclug.real-time.com
>
>