I have been trying to upload to my personal site but every time I tried to I keep facing two issues. First one I get a winsock error and the second error is a network connection issue. Has anyone come across this problem before? I use webeasy for my site builder and than a third party as my domain instead of using them. Any help would be apreciated. I have made sure all ips are the same, I double check our ftp's for our network (verizon fios). I have also disabled my entire webroot (I have the entire packaged installed).
Everything seems to match so not sure why I keep getting these two errors.
Any input would be great.
Thanks in advance.
Page 1 / 1
Hello ytnyc2,
Welcome to the Community Forum,
Can you please do a clean reinstall of WSA and Please follow the steps closely!
Please let us know if that resolves your issue?
Kind Regards,
Welcome to the Community Forum,
Can you please do a clean reinstall of WSA and Please follow the steps closely!
- Make sure you have a copy of your 20 Character Alphanumeric Keycode! Example:SA69-AANA-A783-DE78-C584
- KEEP the computer online for Uninstall and Reinstall to make sure it works correctly
- Download a Copy Here (Best Buy Subscription PC users click HERE)
- Uninstall WSA and Reboot
- Install with the new installer, enter your Keycode and don't import any settings if asked to as you can set it up as you like once it's done
- Let it finish it's install scan
- Reboot once again
Please let us know if that resolves your issue?
Kind Regards,
Hi ytnyc2
If I may take a different approach to what Sherry has recommended/look for the issue in a different are, namely, that WSA my be being 'overprotective' in terms of the system components of the apps that you are using?
There are essentially 3 key areas where this can happen/a user can override WSA. These are essentially reached, from the main WSA panel, as follows:
1. PC Security > Quarantine > Detection Configuration
2. Identity & Privacy > Protected Applications
3. Utilities > System Control > Control Active Processes
and once there the user usually has the options to:
A. "Allow"
B. "Protect/Monitor"
C. "Block/Deny"
In the case of 1. Detection Configuration
If an item is set to:
- "Allow", WSA ignores it during scans and shield actions, meaning if it's a virus that has been allowed, it can continue acting as a virus acts. Be careful of what you allow in this area and ensure it's something you trust implicitly if you are going to change the status from Block to Allow.
- "Monitor", WSA will watch the item to determine if it is legitimate or related to malware. It is not necessary to add files into this list or set files to monitor manually unless you are changing them from a Block or Allow status. This might be useful if for example you think Webroot might have had a false positive on something and you want to check again at a later time to see if the determination has changed. You could set it to Monitor and have Webroot check it again.
- "Block", then WSA will treat the items as it would detected malware. It will not be executed, and it will not be written to your hard drive. Detected infections are automatically set to a Block status.
In the case of 2. Protected Applications (Internet Security & Complete version ONLY)
In this case:
- "Allowed applications" are not secured against information-stealing malware, and also have full access to protected data on the system. Many applications unintentionally access protected screen contents or keyboard data without malicious intent when running in the background. If you trust an application that is currently marked as "Deny," you can change it to "Allow."
- "Protected applications" are secured against information-stealing malware, but also have full access to data on the system. By default, web browsers are assigned to the "protected" status. If desired, you might also want to add other software applications to "protected," such as financial management software. When you run a protected application, the Webroot icon in the system tray displays a padlock.
- "Denied applications" cannot view or capture protected data on the system, but can otherwise run normally.
And finally, in the case of 3. Control Active Processes
If a process is set to:
- "Allow" it means WSA allows it to run on the system. It's important to note that if an item is already allowed here, that's because Webroot knows already from seeing the file before that it's ok to allow.
- "Monitor" status means WSA will journal what that program is doing and keep a very close eye on it for any suspicious activity. Basically it would treat it as if it wasn't already sure about it one way or the other, and it wants to monitor it closely until it's sure about it.
- "Block" means just that...iWSA does not allow it to run on the syste. Be very careful about what you block in this area and ensure that anything you decide to block is a non-essential process. Otherwise, you could be setting yourself up for a lot of grief if you block something critical.
Now, hopefully that has given you a consolidated low down on where to look and what you can do to affect how WSA 'interferes' with files, objects & processes on your system...and so wil help you get to the bottom of what is causing you grief.
Do post back with any specific questions that you may have re. the above, if I happen to be on the right track. ;)
Regards, Baldrick
If I may take a different approach to what Sherry has recommended/look for the issue in a different are, namely, that WSA my be being 'overprotective' in terms of the system components of the apps that you are using?
There are essentially 3 key areas where this can happen/a user can override WSA. These are essentially reached, from the main WSA panel, as follows:
1. PC Security > Quarantine > Detection Configuration
2. Identity & Privacy > Protected Applications
3. Utilities > System Control > Control Active Processes
and once there the user usually has the options to:
A. "Allow"
B. "Protect/Monitor"
C. "Block/Deny"
In the case of 1. Detection Configuration
If an item is set to:
- "Allow", WSA ignores it during scans and shield actions, meaning if it's a virus that has been allowed, it can continue acting as a virus acts. Be careful of what you allow in this area and ensure it's something you trust implicitly if you are going to change the status from Block to Allow.
- "Monitor", WSA will watch the item to determine if it is legitimate or related to malware. It is not necessary to add files into this list or set files to monitor manually unless you are changing them from a Block or Allow status. This might be useful if for example you think Webroot might have had a false positive on something and you want to check again at a later time to see if the determination has changed. You could set it to Monitor and have Webroot check it again.
- "Block", then WSA will treat the items as it would detected malware. It will not be executed, and it will not be written to your hard drive. Detected infections are automatically set to a Block status.
In the case of 2. Protected Applications (Internet Security & Complete version ONLY)
In this case:
- "Allowed applications" are not secured against information-stealing malware, and also have full access to protected data on the system. Many applications unintentionally access protected screen contents or keyboard data without malicious intent when running in the background. If you trust an application that is currently marked as "Deny," you can change it to "Allow."
- "Protected applications" are secured against information-stealing malware, but also have full access to data on the system. By default, web browsers are assigned to the "protected" status. If desired, you might also want to add other software applications to "protected," such as financial management software. When you run a protected application, the Webroot icon in the system tray displays a padlock.
- "Denied applications" cannot view or capture protected data on the system, but can otherwise run normally.
And finally, in the case of 3. Control Active Processes
If a process is set to:
- "Allow" it means WSA allows it to run on the system. It's important to note that if an item is already allowed here, that's because Webroot knows already from seeing the file before that it's ok to allow.
- "Monitor" status means WSA will journal what that program is doing and keep a very close eye on it for any suspicious activity. Basically it would treat it as if it wasn't already sure about it one way or the other, and it wants to monitor it closely until it's sure about it.
- "Block" means just that...iWSA does not allow it to run on the syste. Be very careful about what you block in this area and ensure that anything you decide to block is a non-essential process. Otherwise, you could be setting yourself up for a lot of grief if you block something critical.
Now, hopefully that has given you a consolidated low down on where to look and what you can do to affect how WSA 'interferes' with files, objects & processes on your system...and so wil help you get to the bottom of what is causing you grief.
Do post back with any specific questions that you may have re. the above, if I happen to be on the right track. ;)
Regards, Baldrick
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.