Proxmox unable to log in with administrator to controller domain there no connexion

[rmazouzi]

Hello ,

Please should be informed that i moved a VM windows 2016 Server Active directory from server proxmox to another everything works fine when i start in safe mode with netwroking, but there is no connxion in normal use and i can not log in,i installed virtio driver and driver are up can u help me please because itried everything to solv this issue

 

[dcsapak]

hi,

so from what i understand networking does not work when you boot up normally?

what is the vm config (qm config ID) ?
what is the output of `pveversion -v` ?

did you try with different network models for the vm (e.g. e1000 instead of virtio) ?

 

[rmazouzi]

hi,

so from what i understand networking does not work when you boot up normally?

what is the vm config (qm config ID) ?
what is the output of `pveversion -v` ?

did you try with different network models for the vm (e.g. e1000 instead of virtio) ?

Hi i would like to thank u for ur reply please find below the requested informations
what is the vm config (qm config ID) ?

bios: ovmf
boot: order=sata0;ide2
cores: 2
cpu: x86-64-v2-AES
efidisk0: DATASTORE:vm-100-disk-1,efitype=4m,pre-enrolled-keys=1,size=1M
ide2: local:iso/virtio-win-0.1.240.iso,media=cdrom,size=612812K
machine: pc-i440fx-8.0
memory: 6000
meta: creation-qemu=8.0.2,ctime=1722303534
name: SRVDCLMV01
net0: e1000=BC:24:11:E9:2D:12,bridge=vmbr0,firewall=1
net1: rtl8139=BC:24:11:08D:47,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win10
sata0: DATASTORE:vm-100-disk-0,size=350G
scsihw: virtio-scsi-single
smbios1: uuid=7e41f868-2944-4558-8992-a9d2ec784bf6
sockets: 2
vmgenid: cf85a52a-51e8-498f-be79-d9479a246154


what is the output of `pveversion -v` ?


proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve)
pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916)
pve-kernel-6.2: 8.0.2
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.0.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.0.3
pve-docs: 8.2.2
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.2
pve-i18n: 3.2.2
pve-qemu-kvm: 8.0.2-3
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1


yeah tried diffirent network interface.but the problem remain the same

 

[dcsapak]

proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve)
pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916)

it's a bit of an older version, i'd recommend upgrading

yeah tried diffirent network interface.but the problem remain the same

then it's probably a configuration issue inside the vm, since e1000 should work out of the box in windows and the config looks normal

 

[rmazouzi]

im going to upgrade and will see the result thank you very much

 

[rmazouzi]

i just come to upgrade the pve but the problem still the same



proxmox-ve: 8.2.0 (running kernel: 6.8.8-4-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.8: 6.8.8-4
proxmox-kernel-6.8.8-4-pve-signed: 6.8.8-4
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.0-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.3
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1

 

[dcsapak]

sorry not sure whats the problem exactly (seemingly inside windows) can you try and see maybe there is some info in the windows event viewer?

 

[rmazouzi]

i will now go towards the plan B, i keep the controller domain windows server 2016 on proxmox 1 which work well,and i m installing windows 2022 server to do the migration.