Jump to content

stevang

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by stevang

  1. Ok, i was able to send a quick fax.. it is all looking good again! removed the exclusions as well and it is still working. so, the capi-over-tcp is looking for the fritz.box ip on the network and failes due to mwb3 ransom protection to locate the fritz.box after telling the capi via regedit where the fritz.box is located IP-wise, the problem is solved cause the capi dos not need to search for the fritz.box and does not trigger the mwb3 protection anymore. Thanks for your time! i hope it helps other people with Fritz.Fax and MWB3 as well!
  2. i came from before mwb3 2.somthing the capi error on Fritz.fax startup is gone after editing the registry and adding „FoundFritzBoxes„=“XXX.XXX.XXX.XXX“ (xxx replaced with the fritz.box IP) according to the blog post. still strange that this was no problem without mwb3 i'm still curious if the fax realy works or if the software has been fooled by giving it the fritz.box location via registry.. i have no fax to send right now.. do you have a fax nr?
  3. 21.03.17 23:23:46 FRITZ!fax 21.03.17 23:23:46 Version 3.07.61 21.03.17 23:23:46 ComDir = C:\Users\xxxxx\AppData\Roaming\FRITZ!\Fax 21.03.17 23:23:46 Nebenstelle = 0 21.03.17 23:23:46 Amtsholung = 0 21.03.17 23:23:46 Amtziffern = 4 21.03.17 23:23:46 MSN = xxxxxxx 21.03.17 23:23:46 Annahmeverzögerung = 0 21.03.17 23:23:46 Wiederholungen = 0 21.03.17 23:23:46 Pause = 1 21.03.17 23:23:46 Ausdruck einkommender Faxe = 0 21.03.17 23:23:46 Kopfzeile = FRITZ!fax via ISDN 21.03.17 23:23:46 Teilnehmerkennung = +49 xxx xxxxxxx 21.03.17 23:23:46 Anzahl der Controller = 5 21.03.17 23:23:46 CAPI-Profile Protokollmaske(5) = 0x8000 21.03.17 23:23:46 CAPI-Profile Protokollmaske(5) = 0x8000 21.03.17 23:23:46 CAPI-Profile Protokollmaske(4) = 0x4000 21.03.17 23:23:46 FRITZ!Box: ISDN = 1, Analog = 4, Internet = 5 21.03.17 23:23:46 Anzahl der Controller = 5 21.03.17 23:23:46 CAPI-Profile Protokollmaske(5) = 0x8000 21.03.17 23:23:46 CAPI-Profile Protokollmaske(5) = 0x8000 21.03.17 23:23:46 CAPI-Profile Protokollmaske(4) = 0x4000 21.03.17 23:23:46 FRITZ!Box: ISDN = 1, Analog = 4, Internet = 5 21.03.17 23:23:46 CApplicom[1]::InitIsdn(pWnd 0x36EAE0) 21.03.17 23:23:46 NumberOfController: 5 21.03.17 23:23:46 Controller: -3 -> 5 21.03.17 23:23:46 m_pIsdn AppId = 7 21.03.17 23:23:46 Profileabfrage(): G3 = 0 G3Ext = 0 21.03.17 23:23:46 CAPI Hersteller: AVM Berlin 21.03.17 23:23:46 CAPI Version: 2.0 (3.11.07) 21.03.17 23:23:46 CAPI Seriennummer: 0004711 21.03.17 23:23:46 Empfangsbereitschaft aktiviert 21.03.17 23:23:46 CApplicom[2]::InitIsdn(pWnd 0x36EAE0) 21.03.17 23:23:46 NumberOfController: 5 21.03.17 23:23:46 Controller: -3 -> 5 21.03.17 23:23:46 m_pIsdn AppId = 8 21.03.17 23:23:46 Profileabfrage(): G3 = 0 G3Ext = 0 21.03.17 23:23:46 Empfangsbereitschaft aktiviert pml file has beend send as forum message C: exclusion has been removed again
  4. 21.03.17 23:02:04 FRITZ!fax 21.03.17 23:02:04 Version 3.07.61 21.03.17 23:02:04 ComDir = C:\Users\stevang\AppData\Roaming\FRITZ!\Fax 21.03.17 23:02:04 Nebenstelle = 0 21.03.17 23:02:04 Amtsholung = 0 21.03.17 23:02:04 Amtziffern = 4 21.03.17 23:02:04 MSN = xxxxxxx 21.03.17 23:02:04 Annahmeverzögerung = 0 21.03.17 23:02:04 Wiederholungen = 0 21.03.17 23:02:04 Pause = 1 21.03.17 23:02:04 Ausdruck einkommender Faxe = 0 21.03.17 23:02:04 Kopfzeile = FRITZ!fax via ISDN 21.03.17 23:02:04 Teilnehmerkennung = +49 xxx xxxxxxx 21.03.17 23:02:06 Anzahl der Controller = 0 21.03.17 23:02:06 FRITZ!Box: ISDN = 0, Analog = 0, Internet = 0 21.03.17 23:02:06 Anzahl der Controller = 0 21.03.17 23:02:06 FRITZ!Box: ISDN = 0, Analog = 0, Internet = 0 21.03.17 23:02:06 CApplicom[1]::InitIsdn(pWnd 0x3EAE0) 21.03.17 23:02:06 NumberOfController: 0 21.03.17 23:02:06 Controller: -3 -> 1 21.03.17 23:02:06 m_pIsdn->Register = 0x1009 21.03.17 23:02:06 CApplicom[2]::InitIsdn(pWnd 0x3EAE0) 21.03.17 23:02:06 NumberOfController: 0 21.03.17 23:02:06 Controller: -3 -> 1 21.03.17 23:02:06 m_pIsdn->Register = 0x1009 and well, exluding C: didn't change anything so excluding files seems not to be a solution
  5. Yes.. i have added the whole FRITZ! folder as well. but still the same error
  6. the first one belongs to a chipcard reader (www.reiner-sct.com) that has nothing to do with fax functionality and FriFax32.exe is already excluded.
  7. i guess not fritz.fax itself is the problem but the capi over tcp . since there are less and less isdn lines and all is going thru voip connections.. the capi works over tcp now. maybe that triggers some protection mechanism in mwb3 pml file has been send as forum message
  8. Ransomware Protection off seems to solve the problem, but how can i now make an exception for fritz.fax and keep Ransomware Protection on? sure, as a workaround i could turn Ransomware Protection off, set fritz.box Capi off and on again and start Fritz.fax, send my fax and turn Ransomware Protection back on again, but thats not realy handy.
  9. i thought i remove the logs first, before i reproduce the error with detailed logs turned on. but it seems 7zip left out that file you are looking for anyway.. so once again (password protected file, password via forum message) logs.zip
  10. Turning off Web Protection did not help. logs.zip
  11. Since Malwarebytes updated to 3.0.6 i can use my Fritz.Fax (together with my Fritz-Box DSL Router) only if i close Malwarebytes. When Malwarebytes is running i get an error that the Capi 2.0 Driver is not installed (wich is not true). So i tried to exlude the Fritz.Fax Folder etc from the Malwarebytes Checks, but still no luck. Malwarebytes is somehow blocking the Capi Driver from loading/running and this breaks my Fax Software Fritz.Fax Any Idea why this happens and what to do about it? FritzFax /FritzBox is a brand of www.avm.de . They do Routers etc and are wide spread in Germany. Regards, Stephan
  12. Please check if the blocking on this is wrong. It should point to www.ritlabs.com where i want to get my update for the "The Bat" Email Client, but can't as it is blocked now. thanks!
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.