Search results

For some reason Windows thinks my network is a pubic network. I changed it private and now remote desktop works.

I used traceroute from Mac terminal and from the router with no response. I have two instance of Windows 10 VM and the other one would respond to ping and tracerote. From the Windews 10 that cant be pinged, I can ping other computers from it. Looks like its a one way thing.

From the console I can ping the computer that I use for remote access but the remote computer can't ping the VM. From the remote computer I can access Proxmox, other VM. The OS is Win10 and I double check that remote access is turned on.

I installed debian just to test the network to ensure not a hardware issue. Network card tested good. Reinstalled Proxmox and set a IP After reboot, network is down. Using "ip link set enp2s0 up" to being up the network. Use "dhclient enp2s0" to get a temp IP address Use web browser I input my...

Finally some very good news. IT'S ALIVE!!! I like to thank everyone for your assistance and patience. I like to extend my special thanks to Emilien for being the first to respond.

I will give it a shot. I will be over the moon if I am able to just ping my router.

Installed debian to test network. Debian have no issues with the network interface. Will work on other suggestions sometime during the weekend.

I will. I will get to it as soon as I could.

I did that and the interface comes up but no IP.

I wish I could, but without a IP on the interface there is no internet connectivity. I am going to attempt the debian the Proxmox method.

Can i download that in a ISO?

I am trying my best to follow all of the ideas and instructions, but so far I am not able to get the network to work at all. I also tried two usb network adadpter that I have with no luck. Both of the adadpter all have Realtek chipsets. I find it puzzling that during the install process the...

The rc.local is now working on bring the interface up at boot. I change vmbr0 to emp2s0. The interface starts up in the up states, but no IP address is associated to the interface.

I am not sure where the system gets vmbr0. It may be left over from the previous install which is on a NUC. I thought I did a clean install. I am going to just use gparted boot usb to wipe the drive and start over.

The system is currently booting up with the interface down for some reason. Trying to fix that right now.

I will try it. By the way, looking at the output of "ip addr" even after enabling the interface there is no IP address on the interface. This is odd.

Yes

Emilien and Peter, Below is a screen shot of the network setting right after boot and when manually turned on. Emilien, adding the sleep 20 did not do anything.

The network is still down on boot. I think something is a miss on the install. I was observing the boot more carefully and notice a few things. After the below boot sequence the system paused for about 5 to 7 minutes 4.754966] [drm] Initialized amdgpu 3.41.0 20150101 for 0000:05:00.0 on minor...

ip link set enp2s0 up