Re: 832894 phish fix -- TCP broken
From: Clyde (b26440510_at_DELETEyahoo.com)
Date: 02/04/04
- Next message: Matt: "Re: 832894 phish fix -- TCP broken"
- Previous message: Clyde: "Re: 832894 phish fix -- TCP broken"
- In reply to: Clyde: "Re: 832894 phish fix -- TCP broken"
- Next in thread: Clyde: "Re: 832894 phish fix -- TCP broken"
- Reply: Clyde: "Re: 832894 phish fix -- TCP broken"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 04 Feb 2004 17:08:45 -0500
I still have the ghost image of the bad system.
I'm interested of the "plethera[sic] of things" that would cause local
port access to be refused.
I also forgot to mention that I performed 3 virus scans (Norton 2004,
Norton online and AVG) as well as Ad aware. All came up clean.
>"Scott Harding - MS MVP" <scrockel@**NO_SPAM**hotmail.com> wrote:
>
>>Most likely the problem was there before the patch and the reboot was a
>>coincidence. Since you don't have the issue anymore we can't help
>>troubleshoot but there could have a plethera of things to look at. Thanks
>>for posting at least I guess to let people know to be carefuly?!?!? I cannot
>>telnet to 127.0.0.1 25 either on my Exchange server ...............
>
- Next message: Matt: "Re: 832894 phish fix -- TCP broken"
- Previous message: Clyde: "Re: 832894 phish fix -- TCP broken"
- In reply to: Clyde: "Re: 832894 phish fix -- TCP broken"
- Next in thread: Clyde: "Re: 832894 phish fix -- TCP broken"
- Reply: Clyde: "Re: 832894 phish fix -- TCP broken"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|