Additional IPs don't work with new VMs created

Discussion in 'General Questions' started by helenedwards, Oct 28, 2016.

  1. helenedwards

    helenedwards Bit Poster

    Messages:
    4
    Hi,

    I am setting up new VMs using owned created VM template for windows 2008 server. Everything works smooth when I am using the IPs from same block as bare metal. I have a few IP blocks purchased from my parent hosting company.

    for instance, my bare metal is on 173.158.90.125, all the VMs created with 173.158.90.xxx will work perfectly fine.

    But if I use an IP from a different block range, let's say 50.45.85.xxx, the VM won't connect be accessible via RDP.

    I know I am doing something wrong, but I need to know that.

    Please if anyone can help. I appreciate it.

    Thanks

    ------------------------------------------------------------------------------
    Relax : jazz ringtone, hip hop ringtone, instrumental ringtone . Good fun!
     
    Last edited: Dec 2, 2016
  2. Pavel

    Pavel A.I. Auto-Responder Odin Team

    Messages:
    403
    Hello Helen,

    That's a matter of a routing on both your VM and on your hoster's infrastructure. Please contact your hoster to help you configure proper routing inside of a VM and ensure infrastructure is able to route those IPs.
     

Share This Page