- This topic is empty.
-
Posts
-
Same thing is happening to me here. I think it’s due to the Windows 2003 Server being upgraded to SP1. That’s when my troubles started.
Anyone know a possible fix?
@Boen wrote:
Same thing is happening to me here. I think it’s due to the Windows 2003 Server being upgraded to SP1. That’s when my troubles started.
Anyone know a possible fix?
Symantec will claim that Windows Advanced Server 2003 is not compatible with WinFax…you might want to try version 10.04 if you haven’t already.
I have a host and 5 clients running XP with SP2. After following all the directions at symantec for SP2 permissions, and changing the host to static IP, I still get the following message at startup of controller on clients: “Winfax PRO is unable to connect to the Winfax PRO Host Station called Yab2 (faxserver). Make sure an account has been created for you on the host station (using the same name/password used to login on your client station)”. When I go to Modems and Communications Devices and try to browse for the host or enter its static IP address, I get this error message: “Setup cannot connect to Winfax PRO on Yab2 (Reason: Access is Denied) Check that this is the correct host name”. I have tried everything I can think of an no luck. I have been running this program for years with a glitch here or there, but nothing like this.
Can anyone help? Symantec Technical Support is a waste of time.:angry:
@piloto wrote:
I have a host and 5 clients running XP with SP2. After following all the directions at symantec for SP2 permissions, and changing the host to static IP, I still get the following message at startup of controller on clients: “Winfax PRO is unable to connect to the Winfax PRO Host Station called Yab2 (faxserver). Make sure an account has been created for you on the host station (using the same name/password used to login on your client station)”. When I go to Modems and Communications Devices and try to browse for the host or enter its static IP address, I get this error message: “Setup cannot connect to Winfax PRO on Yab2 (Reason: Access is Denied) Check that this is the correct host name”. I have tried everything I can think of an no luck. I have been running this program for years with a glitch here or there, but nothing like this.
Can anyone help? Symantec Technical Support is a waste of time.:angry:
I am also having the same issue. I have found out that if you logon with the same user account that the winfax host is loged on with i get connected. unfortunately that means all my users would have to be logged on with the same account and that is just unacceptable. any help with this would be apreceated.
I am recieving the access denied on one computer and another computer will not work unless I use my logon. I tried using the regaccess to give her access, but it still will not work.
Same problems here. I had my network working great but had to upgrade the workgroup server from XP to Windows 2003 because of the number of users. When I did that I took an older computer formatted it, put on Windows XP SP2 and WinFax (Host) 10,03 then upgraded to 10.04. Now none of the clients can connect, get the same old same old (Reason: Access is denied)
If I am reading the 10.04 instructions correctly, you need to make a new user account with administrator privileges on each computer sharing the WinFax. Then apply 10.04 to 10.03. Symantec also claims users need NOT logon as the new user. Refer to : http://service1.symantec.com/SUPPORT….&src=_w
Where the instructions are fuzzy is
1. Do you setup the Host when logged on as the new user?
2. Do you setup each Client when logged in as the new user?Confused. I am…and still unable to get connected.
@Wade wrote:
If I am reading the 10.04 instructions correctly, you need to make a new user account with administrator privileges on each computer sharing the WinFax. Then apply 10.04 to 10.03. Symantec also claims users need NOT logon as the new user. Refer to : http://service1.symantec.com/SUPPORT….&src=_w
Where the instructions are fuzzy is
1. Do you setup the Host when logged on as the new user?
2. Do you setup each Client when logged in as the new user?Confused. I am…and still unable to get connected.
No, you should install the clients with the users logon, not the logon you created. The same with the host.
Has there ever been a solution found to this problem? I’ve been searching this forum, but haven’t found the answer yet.
Thanks,
MichelineSame question – anybody have anything new to add? I spent ALL day fighting with this problem and found this forum at 5:00… I tried all of the things listed and of course a few others, including fiddling around with the DCOM permissions and making them match those on a working machine. No dice.
i’ve found that anti-virus like Norton Worm protection, or other firewalls are the major cause this access denied message
make sure you check for these
- You must be logged in to reply to this topic.
