This connecting message that never connects means that you can’t connect to port 443 through all of the hops you see in the tracert; in other words you are not successful in you connection attempt.
I would then start to do the same process for the closest I.P. on the tracert and see if you can connect. If you are unsuccessful then you may have a port forwarding problem in your or one of the downstream routers.
I would recommend that you get your collegue to try the same tracert and then subsequent telnet to see if your hops are resolving the same way. You do not need to do any more of these tests this shows that your not making past there with your request.
I see. Well it is looking like a) either a router problem (with configuration or just compatability) or a downstream router issue. Clearly this is not so straight forward as you can connect to thttps on port 443 and your Payment Processor says they only use that, so write now - given that your other office can connect we need to see what’s the difference. At the other office I would:
Get the model of their router
Make sure they are using the same I.S.P.
If they are using the same router then log into the configuration of that router - you will need to get the admin password and may have to disconnect their network and plug it into a switch with (your laptop)->switch->router to access the admin; otherwise you may just be able to log into it from a computer connected to the network. Write down/take screen shots of the configuration.
You may also want to rule out a DNS problem. However you access the control panel to perform the payment upload, I would try this using the I.P. and not the host name; like:
I tried the IP suggestion real quick and am still getting the same issue. A strange thing though, when doing it that way, there was a red cross through the https lock and letters https. Not sure what that means…probably nothing as when I clicked it, it still said it secure.
As for the other recommendations, just a quick point. The ISP at my home office is different than the ‘real’ office. How does that affect your recommendations above when look at point 2.
The red cross is just telling you that the secure certificate does not match the domain you supplied - because you supplied an I.P. rather than the host name that the certificate is set under.
By doing the I.P. test we have ‘mostly’ ruled out DNS issues. I will elaborate if we need to look at this as a last resort
The ISP question is designed to determine what port filtering they perform. If using the same ISP then we would not need to look at the ISP as a piece in the troubleshooting puzzle, however as they are different then your home ISP is still in play.
Glad you think it is solved. One question though, if your laptop works from the office network and other computers on the office network work then, but your laptop doesn’t work from home, then how is it solved? It could still be something with your home router?
Anyhow I am glad you learned a few new tricks, and do really hope it is solved
No they most certainly won’t, but you, I and a couple hundred other people will know the real truth Glad you are on your way and excellent job on providing further (relavant) imformation, even some that you weren’t asked about.