[sims] Solus3 - Connection Refused

[Steve21]

Morning All,

 

Weird one here, Solus3 been installed the other day for the new upgrades. Everything seems to be working fine, but a few random machines just seem to refuse to do anything, even with exact same firewall rules etc as others.

 

The error is this:

 

2016-08-05 09:26:01.4160|Error|System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:8739/. The connection attempt lasted for a time span of 00:00:02.0012001. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:8739.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:8739
  at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
  at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
  at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
  --- End of inner exception stack trace ---

 

Tried the normal restart of services etc, but just to clarify is it supposed to be a local address it's connecting to? Not server? Also does it need any local bypasses proxy wise if it's connecting locally or should be fine?

 

Thanks,

Steve

[mukz]

Hi Steve, it shouldnt be local address, it should be the solus servers IP, well at least our one is.

 

Try checking the solus install log file on the machine in question and see if it has installed properly.

[Steve21]

Where was that set originally? As I wonder if it's the auto update of Solus that Capita put on that's made some break then :s

 

Can't see any of our clients having the server address within their config files, assuming it's the sims.solus3.agent.ui one? (or as in where do you see your server IP set?)

 

Thanks,

Steve

[mukz]

Urm - thats a good question! I will check my setup, just driving into work. Stuck in bloody London traffic!

 

P.S i turned off auto update by the way.

[Steve21]

Urm - thats a good question! I will check my setup, just driving into work. Stuck in bloody London traffic!

 

P.S i turned off auto update by the way.

 

Ah no rush Appreciate if you could check when you're in.

 

The other option I was looking at was another post that said ipv6 on local client can upset it so will test that in the mean time. (Turned it all off apart from Solus updates as apparently there's an issue with the current one and they're releasing a fix to resolve it "soon")

 

http://www.edugeek.net/forums/mis-systems/152825-has-anybody-else-had-misfortune-using-solus3-deploy-sims-clients-2.html#post1310376

 

Steve

[mukz]

Ah no rush Appreciate if you could check when you're in.

 

The other option I was looking at was another post that said ipv6 on local client can upset it so will test that in the mean time. (Turned it all off apart from Solus updates as apparently there's an issue with the current one and they're releasing a fix to resolve it "soon")

 

http://www.edugeek.net/forums/mis-systems/152825-has-anybody-else-had-misfortune-using-solus3-deploy-sims-clients-2.html#post1310376

 

Steve

 

Hey Steve,

 

Please see attached.

 

Also, has the solus agent started on the workstation which is having issues?

Edited August 5, 2016 by mukz

[Steve21]

Hey Steve,

 

Please see attached.

 

Mmm strange, looks same as ours just without FQDN :s Just don't see where the clients get the information that points to server unless it's hidden registry wise. Thank you for that though appreciated.

 

Gonna have a play with that ipv6 version and thrown Capita a line to see if they have ideas too.

 

Thanks,

Steve

[mukz]

Mmm strange, looks same as ours just without FQDN :s Just don't see where the clients get the information that points to server unless it's hidden registry wise. Thank you for that though appreciated.

 

Gonna have a play with that ipv6 version and thrown Capita a line to see if they have ideas too.

 

Thanks,

Steve

 

Open the file in the following Location on the workstation it is refusing to connect to:

C:\Program Files\Solus3\AgentService\Sims.Solus3.Agent.AgentService.exe.config

 

Look under the XML TAG

 

If all else fails, this is what i usually do to get me working.

1) Remove the computer from solus

2) ipconfig /flushdns on the server

3) do a ping to workstation and make sure that it is correct ip

 

That normally sorts it for me

Edited August 5, 2016 by mukz

[Boredguy]

When I get the error, I just run the ipconfig /flushdns on the server and it's happy. Most of the time it's when stations have been offline for a bit and picked up a new IP but our DNS was not scavenging correctly

[Steve21]

Thanks guys, will have a play and see what deploys and what doesn't over weekend

 

Steve

[danelyoung]

2016-08-05 09:26:01.4160|Error|System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:8739/. The connection attempt lasted for a time span of 00:00:02.0012001. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:8739.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:8739

This exception message says you're trying to connect to the same host ( 127.0.0.1 ), while you're stating that your server is running on a different host. This 127.0.0.1 represents a 'loopback' . It allows the computer to communicate with itself via network protocol .Dns.GetHostEntry(IPAddress.Loopback).HostName returns the host name of your machine. When you pass a host name to TcpClient , it will resolve it to one or more IP addresses using Dns.GetHostAddresses(hostName) . This includes the public and local IP addresses of your machine (e.g. 192.168.12.10), but not 127.0.0.1 (loopback address). So your client is trying to connect to any of the non-loopback addresses of your machine, while your server is listening only on the loopback address . So, no connection can be established. The solution to this problem is that connect to the same end point your server is listening on.