Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 26 subscribers
  • Views 3675 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

S2S - no connection to remote server

Philipp Marx

Hey,

I would like to connect to a remote server via VPN. The s2s connection works but Iam unable to reach the server on the other side (the remote site is one host only).

I can see that the outgoing traffic goes through the firewall rule LAN to WAN, if I will connect from the local subnet 172.20./16 to the remote server 172.20.200.49.

So whats missing / wrong? Do I have to create a further rule/route - where ?

Thanks in advance!



This thread was automatically locked due to age.
Parents
  • 0

    There are two possible issues there:

    • To support federation / s2s, an XMPP server must be available on the internet, and not associated to a local IP. Ideally, you should have set DNS SRV record for that XMPP service.
    • The second issue seems that your DNS resolution seems incorrect as ejabberd gets a local address for the domain from your DNS, when you seem to expect a public IP. You need to make sure the DNS service on the XMPP server is set up and properly working.
Reply
  • 0

    There are two possible issues there:

    • To support federation / s2s, an XMPP server must be available on the internet, and not associated to a local IP. Ideally, you should have set DNS SRV record for that XMPP service.
    • The second issue seems that your DNS resolution seems incorrect as ejabberd gets a local address for the domain from your DNS, when you seem to expect a public IP. You need to make sure the DNS service on the XMPP server is set up and properly working.
Children