No internet connection on my Root Server

    Hello,

    I'm contacting you because I'm experiencing a problem with my server. I received my login details this morning.

    I followed your tutorial to install Windows via this link: https://helpcenter.netcup.com/…rver/windows-installation

    Everything went fine, from installing Windows to installing the Ethernet driver so that my server could access the Web, but as soon as the driver was installed, my Internet access went from 'Not connected' to 'Verifying... No Internet' (see first image) over and over again.

    I also tried to switch the driver in the SCP's network interfaces from 'virtio' to 'e1000' by reinstalling the driver, but that didn't work either.

    I've followed all the tutorials and even looked at the netcup forum, but there's no answer to my problem.

    Quote from Kyzahoff

    my Internet access went from 'Not connected' to 'Verifying... No Internet' (see first image) over and over again.

    But the interface is visible in Windows? Then the driver seems to be working. What does the network configuration of the interface look like? By the way: which Windows Server version are we actually talking about?


    Edit: Ah. I see you've added the screenshots to the thread. As I said before, something seems to be wrong with your network configuration of the interface. You are probably missing the DNS server.

    Quote from Exception

    But the interface is visible in Windows? Then the driver seems to be working. What does the network configuration of the interface look like? By the way: which Windows Server version are we actually talking about?

    - What do you mean by interface?
    - about the network configuration, I've put up a new photo, is that what you're talking about?
    - Windows Server 2019 EN-US for Evaluation (180 Days)

    Quote from Exception

    But the interface is visible in Windows? Then the driver seems to be working. What does the network configuration of the interface look like? By the way: which Windows Server version are we actually talking about?


    Edit: Ah. I see you've added the screenshots to the thread. As I said before, something seems to be wrong with your network configuration of the interface. You are probably missing the DNS server.

    I just saw your edit... I was advised to use DNS 8.8.8.8, do you have another suggestion?

    Open the CMD and enter the following command: ipconfig /all


    Then check whether the IP address, subnet mask and gateway details are correct. Then check whether a correct DNS server has been entered. The DNS server 8.8.8.8 is from Google. Is ok for testing. However, I would always use the provider DNS, i.e. the Netcup resolvers.

    Quote from Exception

    Open the CMD and enter the following command: ipconfig /all


    Then check whether the IP address, subnet mask and gateway details are correct. Then check whether a correct DNS server has been entered. The DNS server 8.8.8.8 is from Google. Is ok for testing. However, I would always use the provider DNS, i.e. the Netcup resolvers.

    my IPV4 address displayed (attached file) is not the same as the one in SCP, which one should I use?

    How can I find Netcup's DNS provider? Thanks in advance

    Your server currently has an APIPA address, i.e. your server was probably unable to reach the DHCP server. You could open the console and enter the commands: ipconfig /release and ipconfig /renew. Or you could statically assign the IP address to the server.


    Sorry but as a server administrator you should know this. Please note that you bear sole and full responsibility for the server and that you may also be held liable if damage occurs due to negligence.

    Your 169.254.xxx.xxx Ip address is a link local IP, not a public IP. Such addresses are used, when there is no other, public IP address assigned to them (via DHCP) or manually configured. So, I guess either there is no DHCP-Server available or the server really doesn't have a working network connection. I would try the IP from the SCP (configure it manually). This is the IP meant for use with your server.


    What Windows version did you install? Probably no german version, those seem to have a problem with the network, while english/american versions seem to work. But I don't have any hands on experience with Windows on a netcup server, so take this with a big grain of salt.

    Quote from tab

    Your 169.254.xxx.xxx Ip address is a link local IP, not a public IP. Such addresses are used, when there is no other, public IP address assigned to them (via DHCP) or manually configured. So, I guess either there is no DHCP-Server available or the server really doesn't have a working network connection. I would try the IP from the SCP (configure it manually). This is the IP meant for use with your server.


    What Windows version did you install? Probably no german version, those seem to have a problem with the network, while english/american versions seem to work. But I don't have any hands on experience with Windows on a netcup server, so take this with a big grain of salt.

    I'm using Windows Server 2019 EN-US Version

    Not related to the network connection issue, but isn't Windows Server 2019 out of support since September last year?

    Unless you have purchased extended support, do you really want to connect this directly to the internet?

    RS 2000 G11 | VPS 1000 G11 | VPS 500 G8 Plus | RS X-Mas 2016 🎄 | VPS A Ostern 2017 | VPS [piko|nano|mikro] G11s | RS Cyber Quack 💗 | WH Expert Special 2018

    Quote from gem

    Not related to the network connection issue, but isn't Windows Server 2019 out of support since September last year?

    Unless you have purchased extended support, do you really want to connect this directly to the internet?

    EOSL since 9. Jan 2024 (extended end of life date 2029) but i am aware of city municipalities that deploy Windows Server 2019 this spring =O

    Quote from gem

    Not related to the network connection issue, but isn't Windows Server 2019 out of support since September last year?

    Unless you have purchased extended support, do you really want to connect this directly to the internet?

    Yes I really need to connect it to the internet

    Then you must not use Windows Server 2019 anymore. And you should really know what you are doing in terms of configuring the firewall of a Windows Server, since it is really a challenge to protect the server against attacks.

    Quote from frank_m

    Then you must not use Windows Server 2019 anymore. And you should really know what you are doing in terms of configuring the firewall of a Windows Server, since it is really a challenge to protect the server against attacks.

    What do you recommend using? I followed the netcup tutorial, which suggested using Windows

    Quote from Kyzahoff

    The ultimate goal is to run .exe applications

    That is usually not the case, since the functionality, that is provided by the exe files, is very likely also as a Linux service available, in a more secure and sophisticated way.


    You can operate a Windows Server, but I would recommend putting a small Linux Server in front of it and use it as a firewall. So you have a very good control, which packets are arriving on the Windows interfaces, and you can sort out all the hacker attempts (around one per second).

    You can upload your own installation ISO. If you're just evaluating your options, you can get a more current Windows version ISO from Microsoft. There are other official sources of evaluation ISOs. Please be aware that Windows is easily made vulnerable if connected directly to the internet without a firewall in front of it, and there is no firewall at Netcup except the one that is part of the operating system itself. From the moment it is turned on, your VM is directly connected to the wild internet.