"Idle disconnect" not working with demand-dial (RRAS, NAT)
htal...@my-deja.com
I am using Win2K build 2195 and experiencing some trouble with the RRAS
Demand-dial feature in combination with NAT.
I have configured the routing interface to hang up after 5 minutes of
idle time. Unfortunately, my ISDN connection stays connected once it
has been opened and I have to disconnect it manually. Thus, the idle
feature doesn't help in saving on my telco's charge-by-minute costs... :
(
I have three clients on the LAN and there is no apparent activity from
any of them during the idle period. I suspect there is some internal
DNS (or other) activity that keeps the line open. I haven't found a way
to debug this in any way.
I checked the MS knowledge base and found only one article, which
didn't directly address the problem but informed about not bothering to
try the demand dial filters since they don't work when used with NAT!
(see <a
href="http://support.microsoft.com/support/kb/articles/Q254/2/45.ASP?
LNG=ENG&SA=ALLKB&FR=0">Q254245</a>).
Previously, I used to have MS Proxy 2 but when I learned about the
Win2K NAT feature I thought it would give me the same (or better)
functionality for basic internet connection sharing. The idle hangup
worked fine with MS Proxy, so isn't there really some easy way of
making the idle disconnect work somehow with NAT/RRAS?
Harri
Sent via Deja.com http://www.deja.com/
Before you buy.
htal...@my-deja.com
When I turned on the debugging options I found out what is keeping my
connection opened.
I keep getting these events, but I don't know how to disable the
activity:
----
A packet from 169.254.96.202 destined to 169.254.255.255 over protocol
0x11 caused interface XTELNET Remote Router Interface to be brought up.
The first 8 bytes of the packet are in the data.
----
What is "protocol 0x11"?
According to my RRAS "IP Routing" / "General" section, the
169.254.96.202 is an "Internal interface" (my LAN card uses IP
192.168.0.1).
In article <88uqv9$frv$1...@nnrp1.deja.com>,