Forum Replies Created
-
Posts
-
UPDATE
How do I dislike this freaking product,,,,, let me counts the ways. OK so let me count how many times I’ve reinstalled this stupid thing.
This time I had to manually remove the program along with all the reg keys and reinstall.
I HATE WINFAX!
Client firewalls have been turned off, they are wide open. Something is jacked up with the Host but I can’t figure it out. I can swap the roles making the client a host and the host a client everything works fine. Once I swap the roles back again that’s when I get the error. Everything was working fine two weeks ago but now we’ve got problems. Of cource the client says nothings changed it just stopped working……
The host is running Win2K SP4 it’s also an ACT server, SQL7 with a custom app, file server for the LAN and the DC for the domain EVERYTHING IS RUNNING HOT STRAIGHT AND NORMAL EXCEPT WINFAX????
I’ve reinstalled the host it works fine, it can send and receive without an issue but the clients keep failing when they try to connect.
ANY IDEAS?????
Thanx
After many hours of troubleshooting I’ve found that when “Check for new events on startup” is enabled WinFax crashes but when it’s disabled everything works fine. Does anyone have any information regarding “Check for new events on startup” What fires off? What port is it communicating to the host on? What could be causing this problem???
Thanx
I think the holding the queue and manually releasing idea is going to be an issue, why well because they’re users..
Do you have any details, how-tos, infomation regarding adding a second line? I can just see how much fun this is going to be, WinFax has issues just running one modem never mind a second. :O
It really bothers me that Symantec sells WinFax knowing that it has problems. I’ve found so many other people with the same problems but no fix. The problem is they have the market share and they don’t give a rats ass, if they did they would fix it or at lease point us to the problem. All their tech notes say rebuild the logs. Stop it, the db has nothing to do with it. I guess it’s what I should expect from Symantec, their AV products are weak and cause all kinds of other problems. I’m really concerned about the damage they’ll do to Veritas now that they own it. I’ve been using Veritas for years now, the first version released under Symantecs control is 10D I’ve been testing it for two weeks now and it’s got problems. WHY, WHY, WHY?
I’m not a programer but I wish I was so I could design and produce a product that would work and not hang when it receives a fax.
I wish someone could tell me why it hangs, what is the root cause?????
Is there reg hacks out there that I don’t know about?
HELP ME PLEASE I HATE WINFAX but I have to support it.
I’ll try what you suggest but I think I’ve tweaked the IS a million times and I’ve got the latest drivers and firmware for the modem. I thought US robitic was the best modems one could buy but I guess I’m wrong. What is the best modem for use with winfax?
While I’ve got you do you know how to correct winfax margins? From what my customer is telling me faxes are sent out kicked over to the lefthand side of the page?
Thanx
95% of the time the hang is caused but the same sending fax machine but it’s not consistant. I’m not sure what type of system the faxes that hang are coming from.
WinFax info
IS
1. AT&F&D2&C1&H1&R2&I0S7=55
2. ATS36=0FC AT&H1&R2&I0
I really appreciate the help.
Thanx
Finally got the thing to hang, below are the log entries. Can someone take a look to see what the problem might be.
Thanx, Paul
104937.4 :=========DCS==========
104937.4 :res : Low
104937.4 :doc res:ok
104937.4 :rate : 14400 V17
104937.4 :padding : 0
104937.4 :length: unlimited
104937.4 :width: 1728
104937.4 :coding: 2D
104937.4 :compr : No
104937.4 :ecm : No
104937.4 :frame : 256
104937.4 :T.6 coding: No
104937.4 :bft : No
104937.4 :
104937.6 :train = 2754
104937.6 :bad = 15
104937.6 :Open Rx file
104937.6 :Send CFR
104937.6 :+FTH=3
104937.6 :>+FTH=3
104937.8 :<CONNECT
104939.0 :getOK resp : OK
104939.0 :AT+FRM=146104939.0 :Receiving page (MR)…
104940.2 :<CONNECT
104950.8 :stop reception
104951.0 :+FRH=3
104951.0 :Wait for last buffer
104956.0 :15% error limit exceededTHANK YOU VERY MUCH 🙂
I’m enable debug first thing Monday morning and see what happens.
Again thank you for the info I never knew there was a debug for WinFax.
UPDATE:
I still dislike WinFax
I wish I had more time to dig into why and which items caused the problem but it’s solved for the moment. I ran Ad-aware and things are hot, straight and normal again. So if you run into the problem I outlined above take a moment and run your favorite flavor of spyware removal solution and see if that helps.
If you can help it stay away from WinFax in the first place.
Thanx, Paul
I’ve been digging around trying to find a solution to my problem. I just found a post on another group that states the following.
You can’t use ip addresses with either 0’s or 1’s by them selfs in an octet because WinFax will change the system MAC.
WTF are they out of their minds.
Check out this Symantec link.
http://service1.symantec.com/SUPPORT….&csm=noWHO WAS THE BRIGHT ONE WHO DID THIS CODING????
Would someone like to call Symantec tech support and inform them of the most commonly used private ip schemes????
Man it just keeps getting funnier and funnier.
Reboots where the first things I did and still no luck. I searched symantecs kb’s and found the info on upgrading to 10.03 and then .04 The only thing that has changed on the client is possibly a new NAV 2005 update but then again it would be the first time NAV and WinFax had issues. Hey aren’t they made by the same company, hey wouldn’t ya think the development teams would communcate with each other????
I wish there was some way log what’s going on in the background with WinFax that way I could get to the bottom of the problem.
The thing I find amazing is I’m not the only one with problems, there are hundreds of users out there with WinFax problems. I wish there was another product out there so I could bump this lousy good for nothing ………
Thanx, Paul
