This is quite odd.
I have a windows service that works OK, but when the computer is restarted the service get stuck on a call to WebRequest.GetSystemWebProxy for 11 minutes. About 11 minutes, on XP and on Vista, where it was tested so far, all the time. If the computer is connected to the company's domain, it works. But when it's not, I'm facing this issue.
Some other weird things happens on Vista as well. For instance, it doesn't have an active network connection (disconnected) during this time and some other Windows system warnings appears just after these 11 minutes. Before 11 minutes the system seems more or less hanged, waiting for something.
It's not about my machine, because I've tested it on XP, and Vista, and also on some VMs of them.
I'm pretty sure that the call to WebRequest.GetSystemWebProxy in your case actually tries to connect to some system on your company network to
Actually find out if the Proxy server is found
Get the script that automatically configures these settings on your system
Please try to use a tool like Fiddler or WireShark to see which outgoing connections are attempted. The url will point out the location it tries to connect to and the reason for the call.
Related
I have code in many Microsoft Access Applications that populate a list with the names of all available printers using code like this:
For Each ptr In Application.Printers
...
While running an application locally, procedures using this code run very quickly.
While running the same application in a Remote Desktop session it takes usually only a few seconds.
For one client, this one line of code takes 90 seconds to execute, but only the first time each day per user, even after the remote desktop session is properly terminated and restarted. The problem then resurfaces for me hours later or the next day.
The Server is Windows Server 2008 R2 Datacenter, SP1
Microsoft Office Professional Plus 2010 14.0.7188.5002
What have I missed?
If you allow the remote RDP session to include your LOCAL printers in that list, then it stands to reason that grabbing the printer list over the network going to be rather slow.
When you launch the RDP client, you can disable this “feature” of the remote system being able to use your LOCAL printer(s) for software running on that remote server. And even worse is your local session might have several printers on YOUR network - this whole process thus can take considerable time - and it can be rather slow.
So disable your local printer use - that option allows the remote server to communicate with and use your local printers - a slow process.
I would suggest you un-check this option when they launch the RDP client:
It turns out that a bad or faulty or somehow uncooperative printer driver set up on the Remote Desktop Server was the culprit. Even when local printers were turned off the 90 second delay was experienced. Removal of the bad printer setup on the server resolved the issue. Using local printers resulted in only a few seconds delay. Everyone's suggestion that the issue might be with Local Printers led to turning them off which then eliminated local printers as the culprit, so thanks all for your input.
Let me start by saying that I have no experience with Linux and this is my first attempt at getting into the IoT with a raspberry pi3. My question is why can I connect via ssh to my pi when I use the ip address but not the hostname?
After getting everything set up at home, I tried to remote in via PuTTY from my laptop. (The laptop is less than 6 months old and if I need to provide the specs on it, I can. It is running windows 10 if that matters). It worked when I entered the ip address of the pi, but when I tried again with the host name (which is clearly defined in the raspberry pi configuration) it said host does not exist. I used hostname.local and still failed.
Today, I brought the whole setup to work to try a few more scenarios. From my work desktop, which is running windows 7 and not wireless, I could remote in via hostname.local. I then tried again on a different laptop running windows 7 and it worked too. Next attempt was on another new (less than 3 months old) laptop running windows 10 and it failed to remote in via the hostname.
This would tell me that there is nothing wrong with my home network or the network at work, and it also makes me think that this has nothing to do with the pi, since other computers can resolve the hostname to the ip address and successfully login. What the hell am I doing wrong or missing?
I spent 2 nights googling and browsing forums trying to find an answer for this but cant, so instead of bashing this post, please poke me for more information you think might be helpful for a solution.
EDIT I gave my computer and PI to my cousin to fix. He installed Samba, though I don't know what it does differently. After doing more research, it sounds like the problem I was having was a DNS issue. I don't know how it was resolved by downloading samba on the pi, but I can now connect via the hostname.
So if I understand correctly it would appear that there is some particular settings on that laptop preventing you from using SSH if that is the only thing you are changing? I think this is likely to be something to do with the security settings on the laptop but Windows isn't my thing sorry.
So I am connecting to my work computer from home and the Remote Desktop Connection app is annoyingly slow.
I pinged my work pc from my computer and it returned at a reasonable time of 50ms~ with 0 loss. I then attempted to ping my home IP from the RDP session and it timed out every time. Not sure if this might help anyone come to a conclusion but hopefully it does. Note I am also using it in conjunction with Cisco AnyConnect Secure Mobility Client if that helps at all. Work is Windows 7 and Home is Windows 8
I attempted switching off my home pc's firewall but that did nothing.
Any assistance would be great, surely a setting in the RDP file might make it run a little smoother.
I'll edit this post with further attempts at fixes below
Did three things and now RDP is running screaming fast:
Change RDP settings:
Run the RDP session and connect to the remote machine
Find mstcsc.exe in the Task Manager and and set priority to Realtime
I installed Ubuntu server XRDP. Went through Windows and terribly slowed down. I solved this problem. In the /etc/xrdp/xrdp.ini file, change crypt_level=high to crypt_level=None
Our remote chain is Citrix then RDP, target machine is Win 10.
I solved this issue by changing the mouse pointer scheme to None and disabling the pointer shadow.
In Windows 10. Go to Display Settings >> Scale and Layout >> Set the custom scale to 120 [you may need to experiment, try 110 - 150]
After that log in to your Remote Desktop, it should adjust the resolution and scaling factors.
It gave me a faster experience. If you need more then follow the answer of Mr. B
I'm using Apache 2.4.4 as a part of WAMP in Windows 2008 server. If I try to send a request while on the fringe of a wifi network using a smart phone and the phone transitions from wifi to 4g, my entire Apache service will freeze until it is restarted. Nothing is written to the access log or error log after the service stops working.
Is there a way to protect my server against this?
Edit:
I did some more testing. This only occurs if I'm using the external IP to connect to the server ie. 60.60.60.60:8080, but not 192.168.0.5:8080.
I am able to recreate the issue 100% if I stand somewhere with slight packet loss (2%), send a request, and disconnect from wifi before a response is received.
The only thing that locks up is Apache. Everything else on the server works fine.
It seems this is an issue with Apache, Windows, and my network card. I tried the solution to this question which is a general solution for buggy Windows/Apache interactions. I'll try updating my network card drivers when I get that chance and that may also solve the issue without needing the above fix.
We have a program that uses QoS-sockets, our softphone application uses QoS for the RTP.
That application is normally left running, sometimes however it is restarted. (Stop, wait 300ms, start.)
We have found that when the softphone-application is stopped that the last one useing QoS on the server, so the RSVP QoS-service on windows is stopped as well.
When we restart our application the RSCP QoS-service normally starts really fast, however sometimes the service start takes a full 30 seconds, causing our application to start slowly as well.
Anyone know if I can configure the service not to stop each time?
The computer is Windows XP SP3, with Windows Firewall turned on. (Our application do have an exception in the firewall.)
Regards
Leif
In the end this was solved with a workaround.
In the main-application we now open a QoS-socket, which we keep open until the main-application ends. That way the RSVP service cannot be closed, since it's in use.
(I found that opening the socket without bind()-ing works, so we don't need any port.)