I recently had WebSockets running on my laptop with XSockets. I then had to rebuild my laptop, installed just like before, and now WebSockets don't work.
I have Norton Internet Security installed just like before. I looked at all my acive ports, checked out my firewall rules, what have ya, and I'm dead in the water. When I try to connect to my server, it immediately closes.
I dont know what else to check. I even turned off firewall protection from norton, and still it doesn't work.
Any help on what else to check, I surely would appreciate it. I'm running Windows 7.
Related
I have a problem with Windows 10 and I am kinda clueless on why and how I should fix it.
I have a work laptop that was upgraded to windows 10 last month. Ever since I got it I have been having problems with my Internet connection. About every one or 2 hours I stop being able to access the internet. I try and run the Windows diagnostic tool but there are of no help. Only restarting the computer helps, which is a major pain.
I have installed Wireshark to monitor my connections but unfortunately I am not really savvy with it. I can however see that there are quite a few broadcasts being made (they make 90% of all connections being made) but I cannot see from where they come.
I have tried disabling all energy saving options, updating the drivers for the network adapter, reinstalling the antivirus and even a hardware test. Nothing helped. My next step would be to reinstall Windows but I only want to do that as a last resort.
Any ideas what I could do next?
So, I actually fixed my problem. I didn´t really figure out exactly why it happened but I found a work around.
In Windows 10, I opened the Event log to see if there was an error being logged. Thankfully I have been documenting when I lost connection so this was easy to find. I saw that everytime I lost connection, Event 4231 was being logged. I googled the Id and found a solution on this website.
I followed the instructions there and had no more problems ever since.
I have a client with a server using IIS 7.5. They have an FTP service for their customers for use with their software package.
The server has been working flawlessly for years. Just over the last week the svchost.exe(ftpsvc) process is using 100% cpu. Until you reboot. Then it is good for a day or so and happens again.
The ftp site has anonymous connections disabled, and just basic passthrough authentication. When the server is at 100% I can remote into the server and see in IIS under FTP Current Sessions a few (10 maybe) of their customers hung in a RETR command. I am not sure if this is what is causing the issue or something else.
If anyone knows the best way to find the root cause of the problem I would appreciate any help you could give.
All windows updates have been installed.
Good afternoon Brian,
I experimented same behavior.
Can you check if you have KB4338818 installed?
It's seems to be the origin of this behavior.
I found this information here:
https://social.technet.microsoft.com/Forums/Lync/en-US/08662831-952f-4d86-b8e8-67874f117d98/july-2018-update-kb4338815-and-kb4338824-causes-issues-within-world-wide-web-publishing-service-on?forum=winserver8gen
After uninstall this update (KB4338818) the problem is gone.
I downloaded the latest version of Appium from the GitHub. I have installed it on two Windows PCs,
On first one it works fine.
But on the second one, just by clicking "Start server v1.7.2" a window appear showing "The server is stopped".
What is wrong with the configuration?
I found the solution for above error.
It was due to firewall modified by an antivirus, it disables all open ports on this PC.
There can be around three solutions:
Format the PC will help us to get open ports, but it is not a recommended solution.
Uninstalling Antivirus can open blocked ports, by recovering firewall to its original state.
If the 2nd solution does not help then Uninstalling Antivirus and create a new User Account on PC, helps me to run Server successfully.
Every attempt to connect to Wired.com is met with a certificate error.
I've checked the usual suspects and even done things that probably have nothing to do with it.
Browsers tried
Safari=failed
Chrome=failed
Brave=failed
Firefox=success
Verified no Chrome extensions interfering (incognito w/ no approved incog extensions)
Same with Safari.
Flushed DNS
Rebooted
Time settings obv correct
I started to get paranoid thinking that something is hijacking my connection, but the only active ports I've got open and connected are... well, supposed to be open. And then the fact that it works with Firefox is even stranger. Firefox is my proxy browser, but it works via proxy w/out.
This is a recently upgraded Sierra machine. I'm not an avid wired reader, so I couldn't tell you if it was happening previously, but I can say I've got 4 other mac test machines here and none of them are experiencing the same issue.
Sierra vs Capitan doesn't make a difference. And this is now going on a 2 week issue. Wired appears to be literally the only site effected. At this point it's more a curiosity at getting to the bottom of this than anything else, since it does appear to be something isolated to this machine.
Also, I think we can rule out a CDN issue. As all my other machines are connecting from this same wanIP.
Man, just absolutely any suggestions for more internals I could go digging through to try and get to the bottom of this would be oh so greatly appreciated. Because I've about relegated myself to keyboard head smashing.
The problem (most likely) is caused due to recent issue at GlobalSign as they incorrectly revoked their cross-certificates. Full statament from GlobalSign: Certificate Revocation Issue
Thanks guys. That GlobalSign certificate was cached.
Removing the cache at
/var/db/crls worked
I backed it up first just in case, but sudo wiping the cache didn't cause any problems.
sudo rm /var/db/crls/crlcache*
sudo rm /var/db/crls/ocspcache.db*
I have a strange issue. Have a windows service running on Windows Server 2008 that receives files over TCP and saves to disk. Initially service was running as Local System account. It worked ok for 7 days and stopped receiving. From the sender side connection succeeds but send fails. The service blocks forever on receive and connection times out.
I changed the user account to "Network Service" and it started working again for 7 days and stopped. I then changed it to run as administrator. It ran for 4 days and stopped again. Now whatever I try it does not work. Rebuilt the code re-installed the service but same issue.
Does anybody ever face such an issue? is it a virus or something? Is windows blocking it? any suggestions will be greatly appreciated.
Note: If I run it as a windows form application it just works fine. Also disabled the firewall but it did not help. While debugging the code I never see any issues. Because it works as a forms app and also worked perfectly as a service for 15-20 days now.
I figured out the problem. When the issue started happening I ran the Filemon utility and figured that the service was failing to access a temp file created using GetTempFileName().
This seems to be a known issue with Windows server 2008R2 and happens randomly.
Here is a solution/Hotfix from Microsoft: http://support.microsoft.com/kb/982613