I have a OpenVPN Server where a lot of diffrent machine are connecting to it and getting their own IP. Thus, we can access any machine from the server. Until now everything worked fine. But now we have some machines which have a C behind the IP (e.g. 10.111.8.1C). We can no longer connect to these machines. Does anyone have an idea what this C stands for? I could not find anahltspunkt on the Internet.
Related
So we have a team at works who manages the firewall. To connect to the network, we use openVPN, which assigns us with an IP to enter the network.
Whilst connected via VPN, I can ping every single machine (including my own), and I can rdp to every PC (excluding my own). This is the problem. I have asked a colleague to try to ping and RDP to my machine from their home via VPN, and they can. So it's a problem with my machine. (My machine is running windows 11.)
Any tips?
Thanks :)
Well I figured it out... Someone in my house had the same IP as the machine at work. I had to change my subnet to a different one to my local ethernet and the one provided by via the VPN for it to work. Because instead of pinging the VPN server then the host machine, it was straight up pinging the person in this house lol.
This may be a very obvious question to a lot of people on here. Unfortunately I'm PRETTY bad with networking, nuff said:
I have a local webservice running on PC A, that I can without a problem access (via the lan/the local ip address:port of PC A) from PC B.
What I'm trying now is to connect the same two PC's, while using the same VPN and being in two different physical networks.
My gut tells me, that I need to reconfigure the local webserver (PC A) to the (local) VPN address that got assigned to it, right? Reality is, this solution is not working. Any suggestions?
Cheers.
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.
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.
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.