|
|
ru.networks- RU.NETWORKS ------------------------------------------------------------------ From : Sergei Shumakov 2:5005/47 17 Jul 2001 17:13:47 To : Serge Rodovnichenko Subject : Ответ модема --------------------------------------------------------------------------------
Friday July 13 2001 10:00, Serge Rodovnichenko wrote to Edward A.Ivanov:
SR> NT RAS? Регистры править бесполезно. Там в registry был ключик. Вот
SR> какой не помню. :-) Hо, также помню, что ничего путного все равно не
SR> получается -- RAS начинает через некоторое время вообще не брать
SR> трубу. Я пришел к выводу, что лучше вообще его по AT запускать и
SR> останавливать.
читаем Q176209
=== Cut ===
RAS or RRAS Server Fails to Answer Incoming Calls After Inbound Call is
Interrupted Before NumberOfRings Setting is Reached
Q176209
-------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Windows NT Server version 4.0
Microsoft Windows NT Workstation version 4.0
Microsoft Routing & Remote Access Service Update for Windows NT Server version
4.0
-------------------------------------------------------------------------------
SYMPTOMS
Your Windows NT Remote Access Service (RAS) Server or Routing and Remote Access
Service (RRAS) server fails to answer incoming calls on a particular port. You
have your RAS or RRAS server configured to answer calls after a specific number
of rings.
For additional information, please see the following article(s) in the Microsoft
Knowledge Base:
ARTICLE-ID: Q170825
TITLE : RAS Auto-Answer Behavior in Windows NT
CAUSE
A RAS client attempted to connect to your server and the connection was
interrupted before the specified number of rings for the RAS or RRAS server
could occur.
For example, you have your server configured to answer after five rings. A
client dials and the call is interrupted before it reaches the fifth ring. The
server will not answer any more calls on that port until the RAS or RRAS server
is restarted.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or
Windows NT Server 4.0, Terminal Server Edition. For additional information,
please see the following article in the Microsoft Knowledge Base:
Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed this to be a problem in Windows NT 4.0 and Windows NT
Server 4.0, Terminal Server Edition. This problem was first corrected in Windows
NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition
Service Pack 4.
=== Cut ===
P.S. какой SP стоит?
Sergei e-mail: sergei.shumakov@altavista.net
ICQ: 14192519
--- GoldED+/W32 snapshot-2000.12.24
* Origin: Visual Systems. Tomsk. Russia. (2:5005/47)
Вернуться к списку тем, сортированных по: возрастание даты уменьшение даты тема автор
Архивное /ru.networks/18513b540216.html, оценка из 5, голосов 10
|