Hang up RAS connection automatically
I have setup a new Microsoft proxy server 2.0 as a gateway for a workgroup to access the Internet via modem connection. It works well, such as to cache URLs, automatically dial the ISP ...
The problem is, it seems the RAS connection cannot be disconnected automatically when there is no user to access the net. Of course, I noticed there is an option in Modem properties, Disconnect a call if idle for more than n minutes, but it looks the option has no any effect. I also have tried to use Dial-up Networking to manually call an ISP, then do nothing to wait for the line disconnect, still with no luck. :-( So, I have to hang up the RAS connection manually every time the clients have no interest on the net. :-((
Also, the Dialing Hour Schedule has no any effects to control client's access to the net. Why?
Any idea?
The problem is, it seems the RAS connection cannot be disconnected automatically when there is no user to access the net. Of course, I noticed there is an option in Modem properties, Disconnect a call if idle for more than n minutes, but it looks the option has no any effect. I also have tried to use Dial-up Networking to manually call an ISP, then do nothing to wait for the line disconnect, still with no luck. :-( So, I have to hang up the RAS connection manually every time the clients have no interest on the net. :-((
Also, the Dialing Hour Schedule has no any effects to control client's access to the net. Why?
Any idea?
It's possible, thatsome applications generate some traffic -- for example, some mail client, checking mail-box every 10 min, when default tim-out for dial-up is 20 min.
Best regards, Eizens
Best regards, Eizens
ASKER
Thanks for your comment.
I have already disabled all the Server, Workstation and NetBIOS binding to the RAS WAN Wrapper, and I am sure there is no other traffic such as email checking, they are all stopped. But, no help! :-(
I have checked M$ newsgroups, and discovered that there were a lot of discusses on this topics there. It looks that is really a problem!
Any idea?
I have already disabled all the Server, Workstation and NetBIOS binding to the RAS WAN Wrapper, and I am sure there is no other traffic such as email checking, they are all stopped. But, no help! :-(
I have checked M$ newsgroups, and discovered that there were a lot of discusses on this topics there. It looks that is really a problem!
Any idea?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Did you try to stop the RAS service according the schedule you specified in order to disconnect the phone line? Or some other ways? Of course, I don't like the way to timely shutdown this server. :)
Also, did you notice that if you dial-up manually, the connection will be hang on time.
So, I think it is possible but needs more thinking. Anyway, it looks that is a bad egg made by M$. :-(
BTW, why M$ did not refund your money?
Also, did you notice that if you dial-up manually, the connection will be hang on time.
So, I think it is possible but needs more thinking. Anyway, it looks that is a bad egg made by M$. :-(
BTW, why M$ did not refund your money?
>Did you try to stop the RAS service according the schedule
Would be no problem but did not fit the bill in our case.
>Also, did you notice that if you dial-up manually, the connection will be hang on time.
You´re lucky. This thing I am hacking at had the no-hangup bug with manual dialing while Proxy 2.0ß was installed...
>bad egg made by M$. :-(
Well, as I said it should be easy for the Proxy team to fix - have Proxy issue the hangup himself - and as proxy has far better data to estimate future usage it could do so more intelligently than RAS... I still like Proxy but would prefer to deploy it in conjunction with an external ISDN router.
>BTW, why M$ did not refund your money?
Probably my fault - too p&%$ed off & overworked to press it. I had only 1 installation showing the prob, and as those people could not wait I had NT reinstalled 5 times over when the MS guy called, so I could not test easily... My own Proxy started being nasty some time after the case was closed.
Have fun
Would be no problem but did not fit the bill in our case.
>Also, did you notice that if you dial-up manually, the connection will be hang on time.
You´re lucky. This thing I am hacking at had the no-hangup bug with manual dialing while Proxy 2.0ß was installed...
>bad egg made by M$. :-(
Well, as I said it should be easy for the Proxy team to fix - have Proxy issue the hangup himself - and as proxy has far better data to estimate future usage it could do so more intelligently than RAS... I still like Proxy but would prefer to deploy it in conjunction with an external ISDN router.
>BTW, why M$ did not refund your money?
Probably my fault - too p&%$ed off & overworked to press it. I had only 1 installation showing the prob, and as those people could not wait I had NT reinstalled 5 times over when the MS guy called, so I could not test easily... My own Proxy started being nasty some time after the case was closed.
Have fun
ASKER
I got it to work!
One of your comments is most important for me: Furthermore, it needs to have the same timeout entered both under 'user options' AND under 'login options'.
It looks, the Logon Preferences is for Auto-dial, Auto-logon?
BTW, sometimes, the proxy dial-up to the Internet without any client request. What is it doing? For active caching? I use system default caching options.
Thanks!
One of your comments is most important for me: Furthermore, it needs to have the same timeout entered both under 'user options' AND under 'login options'.
It looks, the Logon Preferences is for Auto-dial, Auto-logon?
BTW, sometimes, the proxy dial-up to the Internet without any client request. What is it doing? For active caching? I use system default caching options.
Thanks!
>I got it to work!
Nice to hear.
>needs to have the same timeout...
>It looks, the Logon Preferences is for Auto-dial, Auto-logon?
As I said - not logical. The doc for this option dialog clearly states its values are used only in the case where you log in to a network via RAS from the Ctrl-Alt-Del Login box. But perhaps these values need to be read by a service which does not have access to the interactive user´s registry hive - so it looks in the .DEFAULT hive instead.
>BTW, sometimes, the proxy dial-up to the Internet without any client request. What is it doing? For active caching? I use system default caching options.
Apart from the fact that you should restrict active caching anyway (to keep proxy´s dialing behavior predictable) you may also have Exchange clients causing the proxy to dial. The pre-outlook (and outlook perhaps as well) will always use a winsock.dll if it finds one, even if not configured to do so. If your client is using Winsock Proxy via IPX, starting the Exch. Client will force the Proxy to dial... I´m too lazy right now to look it up, please do so yourself - check the proxy FAQ first (tells you how to tell the proxy client DLL to ignore Exchange), then KB articles Q152344, Q167030 (how to prevent Exchange Cl. to make TCP/IP calls).
Nice to hear.
>needs to have the same timeout...
>It looks, the Logon Preferences is for Auto-dial, Auto-logon?
As I said - not logical. The doc for this option dialog clearly states its values are used only in the case where you log in to a network via RAS from the Ctrl-Alt-Del Login box. But perhaps these values need to be read by a service which does not have access to the interactive user´s registry hive - so it looks in the .DEFAULT hive instead.
>BTW, sometimes, the proxy dial-up to the Internet without any client request. What is it doing? For active caching? I use system default caching options.
Apart from the fact that you should restrict active caching anyway (to keep proxy´s dialing behavior predictable) you may also have Exchange clients causing the proxy to dial. The pre-outlook (and outlook perhaps as well) will always use a winsock.dll if it finds one, even if not configured to do so. If your client is using Winsock Proxy via IPX, starting the Exch. Client will force the Proxy to dial... I´m too lazy right now to look it up, please do so yourself - check the proxy FAQ first (tells you how to tell the proxy client DLL to ignore Exchange), then KB articles Q152344, Q167030 (how to prevent Exchange Cl. to make TCP/IP calls).
(keeping the points)
ASKER
?
bbao, you're wondering about my comment?
Well, it's just a trick to view this question as often as I like without paying the points again.
Will work as long as the programmers at E-E don't check the date.
I don't worry about the points, but I have a link now to this question, and want to see it immediately.
I'm using E-E as my knowlege-base too ;-)
Well, it's just a trick to view this question as often as I like without paying the points again.
Will work as long as the programmers at E-E don't check the date.
I don't worry about the points, but I have a link now to this question, and want to see it immediately.
I'm using E-E as my knowlege-base too ;-)
ASKER