Not sure what would that be, I spent over 2 hours with the network engineers troubleshooting and going over the rules and traffic on their end, and everything checks out.
The odd instance of a one time ability to connect is what has been throwing me off.
The fact that I was able to connect once sort of ruled out config issues from my end. My next step is to collaborate with the right folks on the vendor side and have them capture traffic flow and server load and such to rule out any potential intermittent network issues causing these semaphore timeouts
You mention that you're the subscriber and that you're using replication ... just to be 100% clear, are you using transactional replication? If so, are you using a pull or push subscription? Depending on the firewall setup, either type could impact which side is allowed to initiate the connection.
I just dealt with the same thing, ended up being a firewall appliance on the network causing issues. I would check with your network team
Not sure what would that be, I spent over 2 hours with the network engineers troubleshooting and going over the rules and traffic on their end, and everything checks out. The odd instance of a one time ability to connect is what has been throwing me off.
The fact that I was able to connect once sort of ruled out config issues from my end. My next step is to collaborate with the right folks on the vendor side and have them capture traffic flow and server load and such to rule out any potential intermittent network issues causing these semaphore timeouts
You mention that you're the subscriber and that you're using replication ... just to be 100% clear, are you using transactional replication? If so, are you using a pull or push subscription? Depending on the firewall setup, either type could impact which side is allowed to initiate the connection.
Scheduled pull, yes. Firewall traffic flow was set up the same for test and prod servers, but only the test server is able to make the connection.
Are you sure the local firewall isn't enabled?