I keep getting this error when I try to upload my web
pages. "426 unknown socket event while writing".

It started after my ISP did some updates. It will update
some of my pages but not all of them. I checked with my
ISP and they gave me a couple of things to check and none
of them worked so they said that the problem was with
Microsoft not them.
Any ideas.

ISP did updates to what??

Also is it a server error or a local machine error, and if 2K or XP what shows in the event logs??

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

"Suzi" <(E-Mail Removed)> wrote in message
news:16e8401c448ba$83a93d40$(E-Mail Removed)...
> I keep getting this error when I try to upload my web
> pages. "426 unknown socket event while writing".
>
> It started after my ISP did some updates. It will update
> some of my pages but not all of them. I checked with my
> ISP and they gave me a couple of things to check and none
> of them worked so they said that the problem was with
> Microsoft not them.
> Any ideas.

Not sure what updates they did....I believe updated the
mail server and also moved the web page servers.
Everything worked great before they did their updates.

I am running XP Pro. I do not know if it is a server
error or a local machine error. Still pretty new to
it......where would the event logs be?

>-----Original Message-----
>ISP did updates to what??
>
>Also is it a server error or a local machine error, and
if 2K or XP what shows in the event logs??
>
>--
>Steve Easton
>Microsoft MVP FrontPage
>95isalive
>This site is best viewed............
>........................with a computer
>
>"Suzi" <(E-Mail Removed)> wrote in
message
>news:16e8401c448ba$83a93d40$(E-Mail Removed)...
>> I keep getting this error when I try to upload my web
>> pages. "426 unknown socket event while writing".
>>
>> It started after my ISP did some updates. It will
update
>> some of my pages but not all of them. I checked with my
>> ISP and they gave me a couple of things to check and
none
>> of them worked so they said that the problem was with
>> Microsoft not them.
>> Any ideas.
>
>
>.
>