I am running my TCPIP remoting server application (.net version 4.5.1, VS 2013) in windows 10 but I got one server side crash given below, infact it’s perfectly working in windows 7
We have checked port details by "netstat" command and found that the server side port(9092 is my server port) is in listening state, even though we got following error
Error : System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:9092
I hope the issue will come when the client try to register on the server listening port.
Is there any change in TCPIP connection/security settings in Windows 10 ?
Related
I am running currently a webserver with ASP.NET Core 3.1 and a Blazor project.
Recently when upgrading to .NET 6.0 I encountered (even with a blank Blazor project) some problems with a websocket error message in the browser only when deployed on my webserver (see message below).
Locally (on Windows 11 x64, VS 22 Preview 4) there are no error messages...
Webserver: Debian 10 x64, .NET 6.0 SDK installed, running on NGINX with websockets enabled (reverse proxy).
Do I miss out on something or is it a problem with the current state of .NET 6.0 and NGINX? I already tried to access the webpage locally on the debian server and the same error message occurs.
Help would be much appreciated!
Greetings!
Error messages within order:
Information: Normalizing '_blazor' to 'http://192.168.178.35/_blazor'.
blazor.server.js:1 WebSocket connection to 'ws://192.168.178.35/_blazor?id=wnPt_fXa9H4Jpia530vPWQ' failed:
Information: (WebSockets transport) There was an error with the transport.
Error: Failed to start the transport 'WebSockets': Error: WebSocket failed to connect. The connection could not be found on the server, either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets. If you have multiple servers check that sticky sessions are enabled.
Warning: Failed to connect via WebSockets, using the Long Polling fallback transport. This may be due to a VPN or proxy blocking the connection. To troubleshoot this, visit https://aka.ms/blazor-server-using-fallback-long-polling.
Here is the solution described again, maybe a little bit more convenient:
To fix this problem, I changed in the site-configuration (/etc/nginx/sites-available) of nginx the following variables:
proxy_set_header Connection $connection_upgrade;
to
proxy_set_header Connection $http_connection;
For me this solved the problem.
I've setup an Ubuntu image on VirtualBox on a Windows 10 host. On the Ubuntu guest I've installed Redis which runs on port 6379 (TCP) by default.
I tried to follow the tutorial from youtube https://www.youtube.com/watch?v=rXQRqek3kLw but i get a "No connection could be made because the target machine actively refused it 127.0.0.1:6379".
I've setup port forwarding using virtualbox and setting redis.conf.
What should I do?
I've created a windows form app in visual studio 2015.
I'm running on windows 10.
My app will connect to a UDP Socket, using UdpClient object, on the client machine.
The app then will do a receive on the port, external system sends message to the port.
When running debug within Visual Studio 2015 the app works with no issues.
When I run either the debug or release .exe from the bin folder a SocketException occurs on the receive.
Error:
ErrorCode=10060
HResult=-2147467259
Message=A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
NativeErrorCode=10060
I tried this tutorial for .NET TopShelf: http://lourenco.co.za/blog/2013/08/wcf-windows-service-using-topshelf-and-servicemodelex/ and everything works fine on localhost, but when I run Client app on other PC with host IP in app.config aplication return an exception in Program.cs in Client app in line:
var response = proxy.Service.Introduce(request);
The error message says: "tcp error code 10061 no connection could be made because the target machine actively refused it"
I've got windows firewall off. What can I do to connect two computers in LAN network using TopShelf?
Built a simple MVC3 web app to ping a few of our servers for small bits of JSON data and report in a quick UI as a monitoring solution, deployed on Windows 2008 to IIS 7.
All of the outbound HTTP requests via the WebRequest class end up in a error: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:25946
Code works fine when running on a console app on the same server, or as console or web app running on a dev machine. Its only when running as a web app in IIS on the production server that this error happens.
The web app can connect to SQL server and MongoDB but fails at any plain HTTP request. Using an empty WebProxy set to localhost. (with the period) changes the reported error to a 404.
Try looking at the Host (or LMHost) files and make sure that there are no issues wit them.