Forum Replies Created
-
Posts
-
I assume you’ve heard about the fact that there are issues with XPsp2 and Winfax. Version 10.04 fixes them but you have to get 10.03 from tech support first before you can upgrade to 04. You can’t upgrade from 10.02 or earlier.
Well, it finally works!!! I went through both computers and compared the registries (whew) with much difficulty in the keys that have a string like {55BEC173-4A71-442F-85BF-640B558ED871} in the key.
I didn’t make any changes there because the keys weren’t exactly the same on your list or any of my computers. I think the significant changes I made were:
"UseDomainNameDevolution"=dword:00000001
"EnableICMPRedirect"=dword:00000001These were not in the failing computer and when I added them and rebooted, I was able to configure the client! I’m still puzzled why the notebook works with 10.03 and my desktop took so much work even with 10.04 which was itself supposed to fix the problem. Thanks again for working through this!
I hadn’t tried the reset catalog before so I tried it, but still no luck. I’ve also run the guided help to restore Winsock2 and tried the manual method too. Thinking that maybe my Winfax install disks were bad, I tried a fresh install of 10.03 on my notebook and it works fine there (XPsp2). I’m even able to install the fax sharing client without upgrading it to 10.04. I don’t understand why all of my networking and Internet access works fine over TCP/IP but Winfax can’t do it. I”m on the verge of formatting the hard drive and just reinstalling everything (arggggh!).
I really appreciate your help here. Too bad Symantec doesn’t give a damn.
I renamed both registry keys then rebooted. The computer hung for a LONG time upon startup and a couple of apps complained about Winsock2 not being installed. After if finally came up, I check regedit and the Winsock2 key was rebuilt but the Winsock key was not. After a few reboots with the same results, I renamed both OLDs back to the originals and rebooted but the computer still hung (about 5 minutes to see desktop) and complained about Winsock2 missing. I had no Internet connectivity on that machine. On another machine I found a utility on the web called WinsockXPFix.exe and (thru the network) ran it from the damaged PC. It DID fix the problem and it now boots fine again. However, Winfax still complains about the TCP/IP problem when I try to config the fax sharing client.
Yes, however with XP you can’t really deinstall/reinstall TCP/IP. All you can do is reset it with NETSH. I’ve done that to no avail. Currently, after I deinstalled everything, then reinstalled 10.03 and 10.04, whenever I start the computer I get the setup script for CSID and the user info. I fill it out but it keeps asking each time I startup. Also, whenever I go to setup the client for fax sharing I get the TCP/IP Not Installed message. This is before I even get the chance to specify the fax server. I’ve read through all the great posts on the GetFaxing forums plus anything I could find at Symantec and Google and I’m stumped.
I’ve tried a couple of network fax systems but they really suck! Waaaay to complex for me. I just want a simple system (like Winfax was) to work with one phone line on one machine. I curse Microsoft (for SP2) and Symantec (for buying and dropping Winfax).
