Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

Categories

In this Discussion

Home › Help
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Servers can't ping each other?

TheRealMakanTheRealMakan Member
in Help

I bought another server from SoYouStart so I can host a database on it. For some reason the two servers cannot communicate with each other and always timeout whenever I try to send a database request to each of them or ping from one server to the other, but when I ping from my own PC to both of the servers it works fine. I sent in a ticket and still awaiting a response, I just wanted to know if others had these issues and how they solved them?

Thanks a bunch.

Comments

  • IshaqIshaq Member

    Try a traceroute to see where it ends?

  • MikeAMikeA Member, Patron Provider

    Main IP of system or a failover IP that isn't working?

  • TheRealMakanTheRealMakan Member
    edited September 2017

    @Ishaq

    SERVER A -> SERVER B

    raceroute to SERVER B (SERVER B), 30 hops max, 60 byte packets 1 192.99.35.252 (192.99.35.252) 2.842 ms 2.865 ms 2.905 ms 2 10.34.64.76 (10.34.64.76) 0.151 ms 0.185 ms 0.187 ms 3 10.74.8.12 (10.74.8.12) 0.156 ms 0.162 ms 10.74.8.14 (10.74.8.14) 0.151 ms 4 * * * repeat until 30.

    SERVER B -> SERVER A

    traceroute to SERVER A (SERVER A), 30 hops max, 60 byte packets 1 * * * repeat until 30.

    The second one is a complete timeout correct? I don't know why they differ.

  • TheRealMakanTheRealMakan Member

    @MikeA said:
    Main IP of system or a failover IP that isn't working?

    Both main IPs.

  • IshaqIshaq Member

    Have you messed around with your routing table?

    IPs starting with 10 are reserved private IPs.

    Thanked by 1Falzo
  • TheRealMakanTheRealMakan Member

    @Ishaq said:
    Have you messed around with your routing table?

    IPs starting with 10 are reserved private IPs.

    Nope, haven't touched a single thing. Pinging Google shows this:

    traceroute to google.com (216.58.217.110), 30 hops max, 60 byte packets
 1  192.99.35.252 (192.99.35.252)  0.886 ms  0.993 ms  1.108 ms
 2  10.34.64.72 (10.34.64.72)  0.156 ms 10.34.64.76 (10.34.64.76)  0.167 ms  0.172 ms
 3  10.74.8.10 (10.74.8.10)  0.161 ms 10.74.8.12 (10.74.8.12)  0.177 ms 10.74.8.10 (10.74.8.10)  0.160 ms
 4  10.95.81.10 (10.95.81.10)  1.055 ms  1.887 ms *
 5  be100-1319.nwk-1-a9.nj.us (198.27.73.205)  8.958 ms  8.996 ms  9.038 ms
 6  be100-1007.ash-5-a9.va.us (198.27.73.219)  14.406 ms be100-1039.ash-5-a9.va.us (198.27.73.203)  14.126 ms be100-1007.ash-5-a9.va.us (198.27.73.219)  14.688 ms
 7  * * *
 8  108.170.246.65 (108.170.246.65)  14.277 ms  14.330 ms 108.170.246.33 (108.170.246.33)  14.366 ms
 9  72.14.233.21 (72.14.233.21)  14.338 ms 66.249.95.21 (66.249.95.21)  14.362 ms 72.14.233.21 (72.14.233.21)  14.348 ms
10  iad23s42-in-f110.1e100.net (216.58.217.110)  14.674 ms  14.779 ms  14.654 ms
Sign In or Register to comment.