Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Assuming that the same binaries/configs work one-way but not the other would tell me something amiss in the networking side of the house to start with. </p> <ul> <li>You're using IP addresses - double check the bound addresses on target machine against config/code with IPCONFIG /ALL. </li> <li>Does the "server" machine have multiple NICs? Is the service bound to one NIC not both for example?</li> <li>pinging the server will tell you that ICMP is routable between machines - can you create session orient requests e.g. opening UNC paths on the server from the client. </li> </ul> <p>Beyond Firewall, the only other connection refused experiences I've had have been:</p> <ul> <li>Name Resolution - preexisting host entry was wrong. Shouldn't be an issue here though.</li> <li>IPSEC oriented - different policies between machines prevented one from accepting inbound connections from the other. Possible if you work in a corporate secured environment. If you do work in an IPSec environment check for simple stuff like clocks, valid machine certs. All of these can prevent IPSec sessions from being established.</li> <li>stress issue - IP stack exhausted free TCP control blocks through misconfiguration of a server. Equally sounds like you can't get any connection going - probably not the issue.</li> </ul> <p>I'd start with Firewall 1st - either by setting policy to exempt inbound requests on that socket, trust all sockets from the source IP, or by disabling it all-together. (personally the latter is quick and dirty as a test, but I would do the former in a production environment)</p> <p>Beyond that event logs, audit trail if you do have firewall enabled but punched through. Netmon etc. all become your friends.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload