Kevin
Tue Nov 02 09:31:35 CST 2004
And, who knows, Susan may have already won the lotto and can foretell the
future!
Oh, Susan, wherefore art thou???
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
"Geoff Dutch" <GeoffDutch@discussions.microsoft.com> wrote in message
news:8B1EA705-6E9E-44C8-905F-4FF92BA45835@microsoft.com...
> Gotcha - thought it may be the case but, damn, you can't knock me for
> trying
> !!
>
> 8-D
>
> "Kevin Weilbacher" wrote:
>
>> Geoff, not sure that Susan nor anyone else is a prognosticator of future
>> events ... if we were, we would have already won the lotto and would be
>> retired on our yacht somewhere without a phone or computer nearby.
>>
>> ;-)
>>
>> --
>> Kevin Weilbacher [SBS-MVP]
>> "The days pass by so quickly now, the nights are seldom long"
>>
>>
>>
>> "Geoff Dutch" <GeoffDutch@discussions.microsoft.com> wrote in message
>> news:66804D4D-EF85-4704-9DF5-121B3771A93D@microsoft.com...
>> > Hi Susan,
>> >
>> > I have a very similar problem to David Elders - if i install this fix
>> > will
>> > my problem be solved ? Or if it isn't solved will it make things worse
>> > ?
>> >
>> > Thanks
>> >
>> > "Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
>> >
>> >> Programs that connect to IP addresses that are in the loopback address
>> >> range may not work as you expect in Windows XP Service Pack 2:
>> >>
http://support.microsoft.com/default.aspx?kbid=884020
>> >>
>> >>
>> >> May want to try that.
>> >>
>> >> David Elders wrote:
>> >> > Hi all,
>> >> >
>> >> > Just a short heads up on this.
>> >> >
>> >> > XP SP2 *apparently* changes certain aspects with regards networking.
>> >> > Although its possible that most people may not even notice this, we
>> >> > experienced a particular issue regarding VPN working which I thought
>> >> > was
>> >> > worth flagging up in case anyone gets anything similar.
>> >> >
>> >> > XP Pro SP1 laptop would VPN into our SBS2K network - no problem. All
>> >> > OK
>> >> > so
>> >> > far.
>> >> > We would then connect an IP softphone on the laptop to our VoIP PBX
>> >> > [Avaya
>> >> > IP Office] which resides on our LAN. Again, all OK so far.
>> >> > VoIP operation worked fine both inwards and outwards.
>> >> >
>> >> > Upgraded to SP2
>> >> >
>> >> > Again, VPN in works fine.
>> >> > However, although VoIP operation outwards was fine, inwards was VERY
>> >> > choppy.
>> >> > We tried numerous things such as disabling the SP2 firewall entirely
>> >> > and
>> >> > reinstalling the IP softphone, in case either of these would help.
>> >> > Neither
>> >> > did. Ended up having to go back to SP1.
>> >> >
>> >> > Have emailed MS about this and am currently awaiting a response.
>> >> >
>> >> > From reading on various websites and other newsgroups, we understand
>> >> > that
>> >> > there *may* have been certain changes to certain parts of the
>> >> > 'standard' MS
>> >> > networking code and that various 3rd party VPN client software is
>> >> > also
>> >> > affected by similar delay issues. Although its in the final analysis
>> >> > down to
>> >> > the 3rd party vendors [in our case, Avaya] to resolve the issue by
>> >> > releasing
>> >> > fully SP2-compliant versions of their software, I though it was
>> >> > worth
>> >> > bringing to everyone's attention just in order to pre-warn them more
>> >> > than
>> >> > anything in case they are running anything over a VPN which is
>> >> > delay-intolerant such as VoIP.
>> >> >
>> >> > Oh yes, the the SP2 Bluetooth drivers built-into XP don't support
>> >> > audio...!
>> >> >
>> >> > <rant over> :-)
>> >> >
>> >> > David
>> >> >
>> >> >
>> >> >
>> >>
>> >> --
>> >>
http://www.sbslinks.com/really.htm
>> >>
http://www.msmvps.com/bradley
>> >>
http://www.threatcode.com
>> >> [let's get vendors to step up to the plate too]
>> >> https://www.ecora.com/ecora/jump/pm99.asp
>> >>
>> >>
>>
>>
>>