KB911280 Version2 problem

I have a strange problem after applying this patch to our RAS-Server (W2K
SP4). The Dial-Back function is not working anymore. The Dial-back code is
shortened by the last number, eg. instead of 1234 the RAS-server would dial
123 only.


After removing the patch the server would dial-back normally.

We use ISDN cards in our RAS-Server.
We are not affected by the scripting problem of 911280 V1 - we just use the
"normal" dial-up connection to RAS.
Any ideas?

AndreasN <> wrote:

> I have a strange problem after applying this patch to our RAS-Server
> (W2K SP4). The Dial-Back function is not working anymore. The
> Dial-back code is shortened by the last number, eg. instead of 1234
> the RAS-server would dial 123 only.
>
> After removing the patch the server would dial-back normally.
>
> We use ISDN cards in our RAS-Server.
> We are not affected by the scripting problem of 911280 V1 - we just
> use the "normal" dial-up connection to RAS.

I suggest you raise this as a support incident with Microsoft.

--
Robin Walker [MVP Networking]

Please append any addtional digit (like ZERO) to the call back number for a
work around and see if it helps.

That is instead of 1234 use 12340 as call back number.

Thanks
Sarada

"AndreasN" wrote:

> I have a strange problem after applying this patch to our RAS-Server (W2K
> SP4). The Dial-Back function is not working anymore. The Dial-back code is
> shortened by the last number, eg. instead of 1234 the RAS-server would dial
> 123 only.
>
>
> After removing the patch the server would dial-back normally.
>
> We use ISDN cards in our RAS-Server.
> We are not affected by the scripting problem of 911280 V1 - we just use the
> "normal" dial-up connection to RAS.
> Any ideas?

Yes, I tried this already, in fact that would help - but it isn't the
solution. How we would communicate this to our customers?

Andreas


"Sarada" wrote:

> Please append any addtional digit (like ZERO) to the call back number for a
> work around and see if it helps.
>
> That is instead of 1234 use 12340 as call back number.
>
> Thanks
> Sarada
>
> "AndreasN" wrote:
>
> > I have a strange problem after applying this patch to our RAS-Server (W2K
> > SP4). The Dial-Back function is not working anymore. The Dial-back code is
> > shortened by the last number, eg. instead of 1234 the RAS-server would dial
> > 123 only.
> >
> >
> > After removing the patch the server would dial-back normally.
> >
> > We use ISDN cards in our RAS-Server.
> > We are not affected by the scripting problem of 911280 V1 - we just use the
> > "normal" dial-up connection to RAS.
> > Any ideas?

"AndreasN" <> schrieb:

> Yes, I tried this already, in fact that would help - but it isn't the
> solution. How we would communicate this to our customers?

You've contacted Microsoft support directly in the meantime? If not,
please open a case with them. Since the issue seems to be caused by
an security update, you even shouldn't have to pay anything.

Bye,
Freudi

I have the same issue re dial-back as AndreasN.
Although Sarada's suggestion to append an additional digit works, a
permanent solution needs to be found.

Is Microsoft aware of this dial-back problem caused by the first release of
KB911280? (I have installed the v2 release of KB911280 and it has not
corrected the issue)

Chris Driver

"Sarada" wrote:

> Please append any addtional digit (like ZERO) to the call back number for a
> work around and see if it helps.
>
> That is instead of 1234 use 12340 as call back number.

Chris Driver <Chris > wrote:

> I have the same issue re dial-back as AndreasN.
> Although Sarada's suggestion to append an additional digit works, a
> permanent solution needs to be found.
>
> Is Microsoft aware of this dial-back problem caused by the first
> release of KB911280? (I have installed the v2 release of KB911280 and
> it has not corrected the issue)

Unless you tell them, they will not know about it. Please raise a support
incident on this issue.

--
Robin Walker [MVP Networking]

We experienced the same problem. With great difficulty, we convinced Microsoft South Africa PSS to open a support case (they point blank refused to do so, stating that Windows 2000 is in extended support, and they don't care if it's a security fix.) The case reference number was SRQ060704600726.

It took LOTS of convincing and escalating to managers to get them up to speed on their own policy. The engineer that eventually logged the call said "I'll sneak it through for you, don't tell anyone I logged it free of charge."

They summarily closed the call two days later with a workaround of "add another digit to the dial-back number" and a freebie of "we'll call you when we get an update on the issue."

I'm trying to re-open the call six months later now, as we never got the promised update.

Shocking.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com