After installing the MS03-026 patch, Win2K/XP client computers can no longer
connect to the SBS2K server via modem. I can tell the modems aren't
negotiating properly by listening to them -- the modems seem to be stuck
(they make sort of a single continuous sound). Dial-up networking is not
completely broken because these clients can dial into other ISPs (NetZero,
or EarthLink for instance) without trouble. I have one Win2K machine that I
haven't patched yet, and it is still able to dial in. The patched computers
were able to dial into the network prior to the patch being installed. The
server has been patched. I am not sure if a patched client was able to dial
in to the server prior to patching the server itself.

This is an important issue because these remote users use this dial-up to
access their email (Exchange). Any help would be appreciated.

TIA,
Kevin

Re: Remote Access broken after MS03-026 by Marina

Marina
Tue Sep 02 16:39:58 CDT 2003

I have never heard of this patch breaking RAS and I've got several SBS 2K's
with several W2K-clients that are dialing into the server without any
problem at all. What are the eventlogs on the server and the client telling
you?

Marina

"Kevin Rains" <krains@tisinc.com> schreef in bericht
news:eranuaWcDHA.2284@TK2MSFTNGP12.phx.gbl...
> After installing the MS03-026 patch, Win2K/XP client computers can no
longer
> connect to the SBS2K server via modem. I can tell the modems aren't
> negotiating properly by listening to them -- the modems seem to be stuck
> (they make sort of a single continuous sound). Dial-up networking is not
> completely broken because these clients can dial into other ISPs (NetZero,
> or EarthLink for instance) without trouble. I have one Win2K machine that
I
> haven't patched yet, and it is still able to dial in. The patched
computers
> were able to dial into the network prior to the patch being installed.
The
> server has been patched. I am not sure if a patched client was able to
dial
> in to the server prior to patching the server itself.
>
> This is an important issue because these remote users use this dial-up to
> access their email (Exchange). Any help would be appreciated.
>
> TIA,
> Kevin
>
>



Re: Remote Access broken after MS03-026 by Matthew

Matthew
Tue Sep 02 17:24:22 CDT 2003

Hi Kevin,

What happens if you try to connect again?

Can you use rasdiag to give us a little more info on what is happening? You
just have to launch the exe on winxp and reproduce the problem. Then attach
the rasdiag file (filename.rdg) that is created. Here's how to use it in
more detail:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;309553

Rasdiag.exe can be installed from your XP cd.
Here's how to install it:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;306794


--
Matthew Huynh

This posting is provided "AS IS" with no warranties, and confers no rights.


"Kevin Rains" <krains@tisinc.com> wrote in message
news:eranuaWcDHA.2284@TK2MSFTNGP12.phx.gbl...
> After installing the MS03-026 patch, Win2K/XP client computers can no
longer
> connect to the SBS2K server via modem. I can tell the modems aren't
> negotiating properly by listening to them -- the modems seem to be stuck
> (they make sort of a single continuous sound). Dial-up networking is not
> completely broken because these clients can dial into other ISPs (NetZero,
> or EarthLink for instance) without trouble. I have one Win2K machine that
I
> haven't patched yet, and it is still able to dial in. The patched
computers
> were able to dial into the network prior to the patch being installed.
The
> server has been patched. I am not sure if a patched client was able to
dial
> in to the server prior to patching the server itself.
>
> This is an important issue because these remote users use this dial-up to
> access their email (Exchange). Any help would be appreciated.
>
> TIA,
> Kevin
>
>



Re: Remote Access broken after MS03-026 by Kevin

Kevin
Wed Sep 03 11:06:51 CDT 2003

I ran the rasdiag utility -- the resulting file is somewhat large (302KB).
Is there a particular section of the file you would like to see?

The error message that appears (after about a minute) when trying to connect
is:
"Error 678: The remote computer did not respond. For further assistance,
click More Info or search Help and Support Center for this error number."

Also, I thought this affected all my Win2K/XP machines, but I was able to
connect with a Win2K machine. I thought I had tried this computer before
(and I couldn't connect), but now I'm not sure. This particular computer
has been patched. I know that this problem has appeared on 2 XP machines
and 1 2K machine -- I'm not sure if the error message listed above was
exactly the same on all three. I took that error message from one of the XP
computers. The other two computers are with their users, so I don't have
them here to test.

Note: VPN (PPTP) connections still seem to work fine -- only modem
connections appear to be affected.

Kevin

"Matthew Huynh (MSFT)" <mhuynh@online.microsoft.com> wrote in message
news:#7WNzDacDHA.1880@TK2MSFTNGP10.phx.gbl...
> Hi Kevin,
>
> What happens if you try to connect again?
>
> Can you use rasdiag to give us a little more info on what is happening?
You
> just have to launch the exe on winxp and reproduce the problem. Then
attach
> the rasdiag file (filename.rdg) that is created. Here's how to use it in
> more detail:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;309553
>
> Rasdiag.exe can be installed from your XP cd.
> Here's how to install it:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;306794
>
>
> --
> Matthew Huynh
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "Kevin Rains" <krains@tisinc.com> wrote in message
> news:eranuaWcDHA.2284@TK2MSFTNGP12.phx.gbl...
> > After installing the MS03-026 patch, Win2K/XP client computers can no
> longer
> > connect to the SBS2K server via modem. I can tell the modems aren't
> > negotiating properly by listening to them -- the modems seem to be stuck
> > (they make sort of a single continuous sound). Dial-up networking is
not
> > completely broken because these clients can dial into other ISPs
(NetZero,
> > or EarthLink for instance) without trouble. I have one Win2K machine
that
> I
> > haven't patched yet, and it is still able to dial in. The patched
> computers
> > were able to dial into the network prior to the patch being installed.
> The
> > server has been patched. I am not sure if a patched client was able to
> dial
> > in to the server prior to patching the server itself.
> >
> > This is an important issue because these remote users use this dial-up
to
> > access their email (Exchange). Any help would be appreciated.
> >
> > TIA,
> > Kevin
> >
> >
>
>



Re: Remote Access broken after MS03-026 by Matthew

Matthew
Wed Sep 10 02:30:24 CDT 2003

Can you try removing the modem and reinstalling it again?

--
Matthew Huynh

This posting is provided "AS IS" with no warranties, and confers no rights.


"Kevin Rains" <krains@tisinc.com> wrote in message
news:OfQY%23VjcDHA.3872@TK2MSFTNGP11.phx.gbl...
> I ran the rasdiag utility -- the resulting file is somewhat large (302KB).
> Is there a particular section of the file you would like to see?
>
> The error message that appears (after about a minute) when trying to
connect
> is:
> "Error 678: The remote computer did not respond. For further assistance,
> click More Info or search Help and Support Center for this error number."
>
> Also, I thought this affected all my Win2K/XP machines, but I was able to
> connect with a Win2K machine. I thought I had tried this computer before
> (and I couldn't connect), but now I'm not sure. This particular computer
> has been patched. I know that this problem has appeared on 2 XP machines
> and 1 2K machine -- I'm not sure if the error message listed above was
> exactly the same on all three. I took that error message from one of the
XP
> computers. The other two computers are with their users, so I don't have
> them here to test.
>
> Note: VPN (PPTP) connections still seem to work fine -- only modem
> connections appear to be affected.
>
> Kevin
>
> "Matthew Huynh (MSFT)" <mhuynh@online.microsoft.com> wrote in message
> news:#7WNzDacDHA.1880@TK2MSFTNGP10.phx.gbl...
> > Hi Kevin,
> >
> > What happens if you try to connect again?
> >
> > Can you use rasdiag to give us a little more info on what is happening?
> You
> > just have to launch the exe on winxp and reproduce the problem. Then
> attach
> > the rasdiag file (filename.rdg) that is created. Here's how to use it
in
> > more detail:
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;309553
> >
> > Rasdiag.exe can be installed from your XP cd.
> > Here's how to install it:
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;306794
> >
> >
> > --
> > Matthew Huynh
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Kevin Rains" <krains@tisinc.com> wrote in message
> > news:eranuaWcDHA.2284@TK2MSFTNGP12.phx.gbl...
> > > After installing the MS03-026 patch, Win2K/XP client computers can no
> > longer
> > > connect to the SBS2K server via modem. I can tell the modems aren't
> > > negotiating properly by listening to them -- the modems seem to be
stuck
> > > (they make sort of a single continuous sound). Dial-up networking is
> not
> > > completely broken because these clients can dial into other ISPs
> (NetZero,
> > > or EarthLink for instance) without trouble. I have one Win2K machine
> that
> > I
> > > haven't patched yet, and it is still able to dial in. The patched
> > computers
> > > were able to dial into the network prior to the patch being installed.
> > The
> > > server has been patched. I am not sure if a patched client was able
to
> > dial
> > > in to the server prior to patching the server itself.
> > >
> > > This is an important issue because these remote users use this dial-up
> to
> > > access their email (Exchange). Any help would be appreciated.
> > >
> > > TIA,
> > > Kevin
> > >
> > >
> >
> >
>
>