A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Printing and Faxing with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Win XP Pro Fax Doesn't Track Anything - !!FIXED!!



 
 
Thread Tools Display Modes
  #1  
Old April 21st 04, 09:57 AM
John Miller
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

After much finagling, I found how to fix the problem. At least, it worked for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" - "Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab). After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program Control list with full access rights, but it didn't accomplish anything. Looking through the logs generated by NIS reveals (by way of some time-correlation and second-guessing) that the incoming calls are judged to be Netspy Trojan horse attacks and are blocked. But for some reason, they're only blocked from Fax Monitor. The connection succeeds, and faxes can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The instructions they offered were vague, incomplete, and indecisive; sort of "try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group. Hopefully, you'll be able to disseminate this solution to what must be a horde of folks out there who are tearing their hair out trying to figure out why Fax Monitor appears to be broken.

- John
Ads
  #2  
Old April 21st 04, 10:04 AM
Russ Valentine [MVP-Outlook]
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

Thanks for the info. Pretty much what I thought. NIS is usually the problem
and Symantec has yet to provide solutions. I hope you told them.
--
Russ Valentine
[MVP-Outlook]
"John Miller" wrote in message
...
After much finagling, I found how to fix the problem. At least, it worked
for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet
Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" -
"Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab).
After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program
Control list with full access rights, but it didn't accomplish anything.
Looking through the logs generated by NIS reveals (by way of some
time-correlation and second-guessing) that the incoming calls are judged to
be Netspy Trojan horse attacks and are blocked. But for some reason,
they're only blocked from Fax Monitor. The connection succeeds, and faxes
can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The
instructions they offered were vague, incomplete, and indecisive; sort of
"try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group.
Hopefully, you'll be able to disseminate this solution to what must be a
horde of folks out there who are tearing their hair out trying to figure out
why Fax Monitor appears to be broken.

- John


  #3  
Old April 21st 04, 03:09 PM
John Miller
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

After much finagling, I found how to fix the problem. At least, it worked for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" - "Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab). After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program Control list with full access rights, but it didn't accomplish anything. Looking through the logs generated by NIS reveals (by way of some time-correlation and second-guessing) that the incoming calls are judged to be Netspy Trojan horse attacks and are blocked. But for some reason, they're only blocked from Fax Monitor. The connection succeeds, and faxes can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The instructions they offered were vague, incomplete, and indecisive; sort of "try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group. Hopefully, you'll be able to disseminate this solution to what must be a horde of folks out there who are tearing their hair out trying to figure out why Fax Monitor appears to be broken.

- John
  #4  
Old April 21st 04, 03:09 PM
John Miller
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

After much finagling, I found how to fix the problem. At least, it worked for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" - "Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab). After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program Control list with full access rights, but it didn't accomplish anything. Looking through the logs generated by NIS reveals (by way of some time-correlation and second-guessing) that the incoming calls are judged to be Netspy Trojan horse attacks and are blocked. But for some reason, they're only blocked from Fax Monitor. The connection succeeds, and faxes can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The instructions they offered were vague, incomplete, and indecisive; sort of "try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group. Hopefully, you'll be able to disseminate this solution to what must be a horde of folks out there who are tearing their hair out trying to figure out why Fax Monitor appears to be broken.

- John
  #5  
Old April 21st 04, 03:10 PM
John Miller
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

After much finagling, I found how to fix the problem. At least, it worked for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" - "Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab). After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program Control list with full access rights, but it didn't accomplish anything. Looking through the logs generated by NIS reveals (by way of some time-correlation and second-guessing) that the incoming calls are judged to be Netspy Trojan horse attacks and are blocked. But for some reason, they're only blocked from Fax Monitor. The connection succeeds, and faxes can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The instructions they offered were vague, incomplete, and indecisive; sort of "try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group. Hopefully, you'll be able to disseminate this solution to what must be a horde of folks out there who are tearing their hair out trying to figure out why Fax Monitor appears to be broken.

- John
  #6  
Old April 21st 04, 03:10 PM
John Miller
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

After much finagling, I found how to fix the problem. At least, it worked for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" - "Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab). After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program Control list with full access rights, but it didn't accomplish anything. Looking through the logs generated by NIS reveals (by way of some time-correlation and second-guessing) that the incoming calls are judged to be Netspy Trojan horse attacks and are blocked. But for some reason, they're only blocked from Fax Monitor. The connection succeeds, and faxes can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The instructions they offered were vague, incomplete, and indecisive; sort of "try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group. Hopefully, you'll be able to disseminate this solution to what must be a horde of folks out there who are tearing their hair out trying to figure out why Fax Monitor appears to be broken.

- John
  #7  
Old April 21st 04, 03:10 PM
Russ Valentine [MVP-Outlook]
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

Thanks for the info. Pretty much what I thought. NIS is usually the problem
and Symantec has yet to provide solutions. I hope you told them.
--
Russ Valentine
[MVP-Outlook]
"John Miller" wrote in message
...
After much finagling, I found how to fix the problem. At least, it worked
for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet
Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" -
"Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab).
After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program
Control list with full access rights, but it didn't accomplish anything.
Looking through the logs generated by NIS reveals (by way of some
time-correlation and second-guessing) that the incoming calls are judged to
be Netspy Trojan horse attacks and are blocked. But for some reason,
they're only blocked from Fax Monitor. The connection succeeds, and faxes
can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The
instructions they offered were vague, incomplete, and indecisive; sort of
"try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group.
Hopefully, you'll be able to disseminate this solution to what must be a
horde of folks out there who are tearing their hair out trying to figure out
why Fax Monitor appears to be broken.

- John


  #8  
Old April 21st 04, 03:10 PM
Russ Valentine [MVP-Outlook]
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

Thanks for the info. Pretty much what I thought. NIS is usually the problem
and Symantec has yet to provide solutions. I hope you told them.
--
Russ Valentine
[MVP-Outlook]
"John Miller" wrote in message
...
After much finagling, I found how to fix the problem. At least, it worked
for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet
Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" -
"Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab).
After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program
Control list with full access rights, but it didn't accomplish anything.
Looking through the logs generated by NIS reveals (by way of some
time-correlation and second-guessing) that the incoming calls are judged to
be Netspy Trojan horse attacks and are blocked. But for some reason,
they're only blocked from Fax Monitor. The connection succeeds, and faxes
can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The
instructions they offered were vague, incomplete, and indecisive; sort of
"try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group.
Hopefully, you'll be able to disseminate this solution to what must be a
horde of folks out there who are tearing their hair out trying to figure out
why Fax Monitor appears to be broken.

- John


  #9  
Old April 21st 04, 03:10 PM
John Miller
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

After much finagling, I found how to fix the problem. At least, it worked for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" - "Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab). After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program Control list with full access rights, but it didn't accomplish anything. Looking through the logs generated by NIS reveals (by way of some time-correlation and second-guessing) that the incoming calls are judged to be Netspy Trojan horse attacks and are blocked. But for some reason, they're only blocked from Fax Monitor. The connection succeeds, and faxes can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The instructions they offered were vague, incomplete, and indecisive; sort of "try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group. Hopefully, you'll be able to disseminate this solution to what must be a horde of folks out there who are tearing their hair out trying to figure out why Fax Monitor appears to be broken.

- John
  #10  
Old April 21st 04, 03:10 PM
Russ Valentine [MVP-Outlook]
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

Thanks for the info. Pretty much what I thought. NIS is usually the problem
and Symantec has yet to provide solutions. I hope you told them.
--
Russ Valentine
[MVP-Outlook]
"John Miller" wrote in message
...
After much finagling, I found how to fix the problem. At least, it worked
for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet
Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" -
"Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab).
After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program
Control list with full access rights, but it didn't accomplish anything.
Looking through the logs generated by NIS reveals (by way of some
time-correlation and second-guessing) that the incoming calls are judged to
be Netspy Trojan horse attacks and are blocked. But for some reason,
they're only blocked from Fax Monitor. The connection succeeds, and faxes
can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The
instructions they offered were vague, incomplete, and indecisive; sort of
"try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group.
Hopefully, you'll be able to disseminate this solution to what must be a
horde of folks out there who are tearing their hair out trying to figure out
why Fax Monitor appears to be broken.

- John


  #11  
Old April 21st 04, 03:10 PM
Russ Valentine [MVP-Outlook]
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

Thanks for the info. Pretty much what I thought. NIS is usually the problem
and Symantec has yet to provide solutions. I hope you told them.
--
Russ Valentine
[MVP-Outlook]
"John Miller" wrote in message
...
After much finagling, I found how to fix the problem. At least, it worked
for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet
Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" -
"Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab).
After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program
Control list with full access rights, but it didn't accomplish anything.
Looking through the logs generated by NIS reveals (by way of some
time-correlation and second-guessing) that the incoming calls are judged to
be Netspy Trojan horse attacks and are blocked. But for some reason,
they're only blocked from Fax Monitor. The connection succeeds, and faxes
can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The
instructions they offered were vague, incomplete, and indecisive; sort of
"try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group.
Hopefully, you'll be able to disseminate this solution to what must be a
horde of folks out there who are tearing their hair out trying to figure out
why Fax Monitor appears to be broken.

- John


  #12  
Old April 21st 04, 03:11 PM
Russ Valentine [MVP-Outlook]
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

Thanks for the info. Pretty much what I thought. NIS is usually the problem
and Symantec has yet to provide solutions. I hope you told them.
--
Russ Valentine
[MVP-Outlook]
"John Miller" wrote in message
...
After much finagling, I found how to fix the problem. At least, it worked
for my configuration.

I added my "local host" IP address (127.0.0.1) to the Norton Internet
Security's "Trusted Zone" (Under NIS, go to "Personal Firewall" -
"Configure" - "Networking" and add 127.0.0.1 under the "Trusted" tab).
After that, Fax Monitor worked fine.

I tried adding the Windows XP Fax and fax service executables to the Program
Control list with full access rights, but it didn't accomplish anything.
Looking through the logs generated by NIS reveals (by way of some
time-correlation and second-guessing) that the incoming calls are judged to
be Netspy Trojan horse attacks and are blocked. But for some reason,
they're only blocked from Fax Monitor. The connection succeeds, and faxes
can be reliably received.

Symantec's web site was of no use at all in troubleshooting this issue. The
instructions they offered were vague, incomplete, and indecisive; sort of
"try all this stuff and see if anything works".

Russ, it appears that you're pretty active in this discussion group.
Hopefully, you'll be able to disseminate this solution to what must be a
horde of folks out there who are tearing their hair out trying to figure out
why Fax Monitor appears to be broken.

- John


  #13  
Old April 21st 04, 10:23 PM
John Miller
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

Boy, did I ever...

- John

"Russ Valentine [MVP-Outlook]" wrote in message
...
Thanks for the info. Pretty much what I thought. NIS is usually the

problem
and Symantec has yet to provide solutions. I hope you told them.
--
Russ Valentine
[MVP-Outlook]



  #14  
Old April 21st 04, 10:23 PM
John Miller
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

Boy, did I ever...

- John

"Russ Valentine [MVP-Outlook]" wrote in message
...
Thanks for the info. Pretty much what I thought. NIS is usually the

problem
and Symantec has yet to provide solutions. I hope you told them.
--
Russ Valentine
[MVP-Outlook]



  #15  
Old April 22nd 04, 04:23 PM
John Miller
external usenet poster
 
Posts: n/a
Default Win XP Pro Fax Doesn't Track Anything - !!FIXED!!

Boy, did I ever...

- John

"Russ Valentine [MVP-Outlook]" wrote in message
...
Thanks for the info. Pretty much what I thought. NIS is usually the

problem
and Symantec has yet to provide solutions. I hope you told them.
--
Russ Valentine
[MVP-Outlook]



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 06:44 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.