Error 633. The Port is already open .... HELP!!
x
I've installed SBS V.4.0 at several locations and I have the same problem
at each site. The clients can hit the WWW thru Proxy Server (V.1.0) the
first (and sometimes second and third) time without a problem. Proxy will
automatically disconnect after the time out period. The next time a client
goes to surf, you get the message (only on the server) "Error 633: The port
is can't be opened or is already in use ... yada yada yada" (I don't recall
the exact message). There is no way to reset the modem (I've tried many
brands on the SBS HCL) and all the Proxy services are hung. You have to
shutdown and reboot the server in order to reset the modem(s).
Anybody else having this much fun? Will the Service Pack (V.4.0a) resolve
this?
Any suggestions would be GREATLY appreciated.
Leon Hemeryck
DAC Ltd.
le...@dacweb.com
Rob Galatidis
Make sure the username and password specified for the account are correct. It
seems that if you don't get authorised by the host server, the connection
doesn't disconnect.
Also in "winnt.sbs\system32\ras" edit the rasphone.pbk file manually:
idledeiscnnectseconds must not = 0.
I set the value to 3 seconds and it hung up after about a minute or so, so you
may have to play around with it a little, but that should fix your problem.
good luck
Patrick Kirk
You have a problem with the way your modem handles failures during login
and/or unexpected terminations by the ISP. The fix for this is a post sp3
rasscrpt.dll which I will send you direct and to anyone else suffering from
the Error 633 problem.
Patrick Kirk
x wrote in message <01bd89cf$0c079120$1ce3a4cf@leon>...
Mike Smith
>x wrote in message <01bd89cf$0c079120$1ce3a4cf@leon>...
>>I've installed SBS V.4.0 at several locations and I have the same problem
>>at each site. The clients can hit the WWW thru Proxy Server (V.1.0) the
>>first (and sometimes second and third) time without a problem. Proxy will
>>automatically disconnect after the time out period. The next time a client
>>goes to surf, you get the message (only on the server) "Error 633: The port
>>is can't be opened or is already in use ... yada yada yada" (I don't recall
>>the exact message). There is no way to reset the modem (I've tried many
>>brands on the SBS HCL) and all the Proxy services are hung. You have to
>>shutdown and reboot the server in order to reset the modem(s).
>>
>>Anybody else having this much fun? Will the Service Pack (V.4.0a) resolve
>>this?
I wish they'd put this in the KB
Mike
"Clive Rothwell" <clive_r...@netteam.co.uk> wrote:
>I periodically get a 633 error after a scheduled dial up to my ISP. The
>result is that I can no longer dial out through that particular com port. I
>have tried many combinations of machines and modems and have come to no
>conclusions whatsoever other than certain combinations produce more of
>these errors than others The worst offendinding machine is a Dell Poweredge
>2100. Incidentally I am running NT4 service pack 3 as suggested to resolve
>the 633 error. I admit that they dont occur as frequently as they did but
>they do still occur.
>
>Any suggestions.??
Its more than likely your script. You need to rewrite it correctly, to
include the 'waitfor' command, and test the success of each 'waitfor'
command before the script proceeds to the next command.
Heres a sample of the sort of thing you should be doing
proc main
waitfor "ervice?" until 90
if $SUCCESS then ; Checking whether this is successful...
transmit "p^M"
waitfor "sername:" until 60
if $SUCCESS then ; Checking whether this is successful...
transmit $USERID, raw
transmit "^M"
waitfor "assword:" until 60
if $SUCCESS then ; Checking whether this is successful...
transmit $PASSWORD, raw
transmit "^M"
endif
endif
endif
endproc
From Microsoft KB - Article ID: Q175410 which was based on the
following usenet posting...
From: "David Turner" <dtu...@digitalengineering.com>
References: <01bcbc64$72afb300$827ff6cd@baw-station>
Subject: Re: error 633
Date: Tue, 9 Sep 1997 08:40:27 -0400
Lines: 82
Organization: Digital Engineering, Inc.
X-Newsreader: Microsoft Outlook Express 4.71.1008.3
X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3
Message-ID: <ejE4H3R...@uppssnewspub04.moswest.msn.net>
Newsgroups:
microsoft.public.windowsnt.domain,microsoft.public.windowsnt.protocol.ras,microsoft.public.windowsnt.protocol.tcpip
Path: uppssnewspub03.moswest.msn.net!uppssnewspub04.moswest.msn.net
Xref: uppssnewspub03.moswest.msn.net
microsoft.public.windowsnt.domain:18526
microsoft.public.windowsnt.protocol.ras:14822
microsoft.public.windowsnt.protocol.tcpip:14464
Boris A. Wessely wrote in article
<01bcbc64$72afb300$827ff6cd@baw-station>...
>
>Running NT 4.0 and MS proxy 1.0 - error 633 (port in use) keeps
>re-occuring?
>
>Service pack 3 was supposed to fix this but to no avail.
>
>Help - webm...@culpeper.org
>
I have been following mutliple threads regarding the 633 problem.
'IPC SCOTT KAPPELE' posted the following in one and I'm including it
here. From the thread, it is assumed it is the dial-up scripting
tool, in particular, the script itself. Unless written wisely, a
possible lock out condition can occur, forcing the error. I have
applied what is recommended and I am seeing good result (no errors for
5 days). If you are having a RAS 633 error, try this and respond with
your results.
By changing all lines that wait for a sequence of characters from the
host, I was able to clear up my 633 problem.
What looked like:
transmit "^M"
waitfor "Host:"
transmit "CIS^M"
waitfor "login:"
transmit $USERID, raw
waitfor "password:"
transmit $PASSWORD, raw
became:
transmit "^M"
;Give the host 10 seconds to respond
waitfor "Host:" until 10
; Check the return value
if $SUCCESS then
transmit "CIS^M"
waitfor "login:" until 10
if $SUCCESS then
transmit $USERID, raw
waitfor "password:" until 10
if $SUCCESS then
transmit $PASSWORD, raw
endif
endif
endif
The problem was that the waitfor lines waited indefinitely for
the expected string. The connection would get forcibly closed at some
point, and the script processor would never get a chance to tell NT to
release it's handle on the port, resulting in an error 633 condition.
My suspicion is that a variety of errors can cause this condition as
well, not only the Remote Modem Hung Up event, as long as they occur
while the script is executing. The script processor probably doesn't
encounter these errors often, as it only gets executed after a
successful connect.
While the updated script would still function properly without them,
the "if $SUCCESS then" lines are there to speed up the disconnect when
there are problems on the line. If the host never sends "Host:", this
script finishes in 10 seconds. Without the conditional lines the
disconnect would take 30 seconds.
Finally, I can't believe I missed the script issue when I first
did my Modem 1 to Modem 2 tests. Thanks, Michael for your insight and
participation, your comments really made me think about what was going
on in the NT box. Identifying the remote modem hung up event, and the
fact that sometimes you wouldn't get validated by your host ( waitfor
"Password:" only gets 1 try at it!) were crucial pieces of info in
diagnosing this situation. Turns out it's not even a bug per se, just
a predictable behavior. The documentation for creating scripts is
located in the Windows directory on Win95, and in the
WINNT\SYSTEM32\Ras folder in NT. It is called script.doc.
Shaun Gaskell
Hi,
I am experiencing a similar type of problem. I have two modems, one for
faxing and one for Internet dialup. The proxy uses the same port as the
mail (Exchange Server). All is well till Proxy dials up. This then gives
the error 633 The port is not configured or still in use..., which,
according to tech support is fixed in service pack 3.
I would be grateful if you could mail the fix to me Patrick. My email is
Mailto://Sh...@marval.co.uk
Thanks,
Shaun
Patrick Kirk wrote in message ...