I've run into a problem adding IP's to an SME server VM.
Determining if ip address xxx.xxx.xxx.xx is already in use for device eth3...
Error, some other host(mac address) aleady uses address xxx.xxx.xxx.xx.
Now, of course, I started looking at other servers hosted in Proxmox and outside of it as well, finding no other device using the IP addresses in question.
You could ping one of the addresses, but not the other.
More precisely I could ping the local address, but not the public one.
I realised that the device using the IP's is actually Proxmox itself. When I disabled the interfaces in the host (ifdown vmbr6) I could assign the address to the server in question after that.
The IP's are configured like this in the Proxmox network tab.
vmbr6 Linux Bridge enp5s0f0 xxx.xxx.xxx.xx 255.255.255.0
Now I might add that the SME server is being migrated using this guide:
https://www.caretech.io/2017/10/17/migrating-virtualbox-vdi-to-proxmox-ve-5/
Though I don't think it's related to the networking issue.
So steps that I've taken to try and fix the issue are:
Rebooted the SME server
Restarted the networking service on the SME server
Rebooted Proxmox
Removed network interfaces from the SME server
Changed the interface model from VirtIO to IntelE1000
Tried changing the MAC addresses
I've been battling this issue for 2 days and any and all help would be appreciated. Kind of in a hurry to migrate our services from VirtualBox to Proxmox.
Thank you.
Related
So a little background of what I'm trying to accomplish. I'm basically trying to setup a Windows File Server using GCP VM Windows Instance. I have the VM setup and I have created a VPN connection between our office network and to the GCP VM network.
Now I'm trying to communicate between the two different subnets and I have to admit I'm kinda lost.
My office subnet is 192.168.72.0/24 and my GCP IP is 10.123.0.0 with my server being at 10.123.0.2
If I understand networking correctly I need to setup a route between 192.168.72.0 to 10.123.0.2? Or do I just need to create a firewall rule?
I'm using a SonicWall Firewall to establish the VPN connection to the GCP network.
I think I've been working at this too long for one day. I'm steaping away for a bit.
Thanks in advance.
If you set up a Site to Site, you should not need to include a route, you will if you setup a Tunnel Interface. But to me, it sounds like you just need to do a site to site. I dont think the tunnel will come up without the correct subnets, but just verify that the tunnel is up and then I would setup a packet monitor to see what route the traffic is taking when you try to ping from 192.168.72.0/24 to IP is 10.123.0.0.
I have a bit of a bizarre problem. I have a Hyper-V VM and I cannot connect to it via IP address on the host computer.
I intend to use it as an SQL server to host a database for a website while I test it, and the first step I can see in this endeavour is to make sure the IP addresses work externally.
Other PCs on the LAN appear to be able to connect just fine via the IP address on Remote Desktop. I cannot do so. I also cannot connect through SQL Management Studio (named pipes or TCP/IP). Although named pipes gives an error relating to being denied access as opposed to IPs which are just not found.
I have tried pinging both ways:
VM => Host : Always gives a "Destination Host Unreachable" error
Host => VM: Always gives a "Request Timed Out" error
As for netstat -a -n, I can see that the VM is listening to 3389 (default Hyper V port, which makes sense).
Regarding Firewalls, all have been turned off on all machines. I can tell that the firewall is not the issue.
If you need any more information to help me to diagnose and treat the problem, please ask me as I would like to get this sorted as quickly as possible.
Thanks a lot in advance.
Which windows server version do you use?
Windows Server 2016 blocks insecure RDP connections (https://support.microsoft.com/en-us/help/4295591/credssp-encryption-oracle-remediation-error-when-to-rdp-to-azure-vm).
Since RDP uses CredSSP you have to install the current Windows Patches.
Do you can ping the DNS server by IP address from your VM?
Is ICMP (ICMP = the thing you need for ping) on your host enabled?
Here is a Checklist for ICMP:
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc749323(v=ws.10)
Solved,
Just switched to another physical computer and it was fine.
I've got a few web servers running on my local network and, I wanted to change a specific port on a web server into IP address so that I can easily proxy them over nginx and also have access to them locally via Bind. I've got a server [HTTPD] with a few WordPress sites running on different ports [i.e 80, 8080 ETC] and I would like to change those into a private IP address locally. This is a complicated problem of the fact that I cannot specify port numbers on my local DNS, and I also don't want to install another nginx server on the local sites. Thanks guys
Search the web for "Centos 7 IP Aliasing" and set up a new IP address that connects to your machine. Then configure a new virtual host to listen on that new IP address.
I would give you more info, except A) IP aliasing on Centos 7 is more involved than I like (much easier on Solaris), and B) I'm not familiar at all with configuring Nginx (very easy on Apache).
#Tarun Lalwani asks a good question regarding whether this is a home or local network vs. a public one. You have to pay $$ for a public IP address as they are a scarce, managed resource, whereas your local network can accommodate almost as many IP's as you can think of. Anyone on your local network can access your service on your machine using those extra IP's. However, accessing those local IP's from the Public Internet is a separate topic altogether, involving router configurations and NAT addressing.
It may not be the precise answer you're looking for, but at least it should give you a direction to continue looking.
First I must say that I have no idea what kind of problem it is (Ubuntu/Windows/vmware/secureW2), so I hope anyone can select the necessary information from this mess.
I am running an Ubuntu 15.04 guest on a Windows 10 host using the vmware Virtual Machine. The Ubuntu internet icon in the right hand corner claims that it has a (wired) connection, yet I can't browse or ping google. Windows 10 is successfully connected by wi-fi, vmware uses a bridged connection (automatic) and my router enables DHCP. I can successfully ping my router from within the VM (at least, I assume 192.168.1.1 still refers to my actual router, and not some virtual router). In windows I can see two network adapters running (VMnet1 and VMnet8), both of which say they're enabled but have no internet access. I tried installing the bridge protocol in them, I tried using NAT instead of a bridge, but all to no avail. I was still connected just a few days ago when I was at school, which makes me think SecureW2 (a program responsible for connecting me to the school wi-fi) could also be involved somehow.
Everyone thanks in advance!
Turns out it was DNS related, caused by Ubuntu and SecureW2. The /etc/resolv.conf file was set up specifically for the LAN at school, for which I blame SecureW2. I "solved" it by adding my router IP to (the top of) the name server list, though I know this is only a practical solution.
Okay, so I'm hosting a VPS for someone using Virtualbox. I've setup a server for that guy with a NAT network type ( this way I could port forward the entire thing so it can be used for what the guy wants ). The guy can use remote desktop to connect to the server, however. Everyone who tries to join his game, gets the same IP. I guess this has something to do with the guest settings, if I'm not mistaken.
Could anyone provide me any more information about the reason behind these IP's?
I'm running on the latest version of Virtualbox with a windows 7 enterprise 64bit version where a SA-MP server is being hosted on.
Everyone who connects to his server gets the ip; 10.0.2.2. Any help would be really appreciated
If a machine is located behind NAT, then all of the incoming connection will always be recorded only from a single source, that is you router's IP. It's normal since all of the incoming connection will have to go to the router first.