Window server 2003 install

  • Thread starter Thread starter Deleted member 2433
  • Start date Start date
D

Deleted member 2433

Guest
Ok, so I'm having trouble configuring the network interface on my windows server 2003 KVM install.

I've tried installing it using 'virtio' as the card which shows absolutely nothing under connections.

I've tried installing it using 'realtek8139' as the card which although gives me connections cannot acquire a DHCP lease and can only connect to other devices when it's manually configured. Except it can't be accessed (including RDP) from any other device on the network.


I've already successfully installed XP in a KVM on the same machine and that works fine.

Can anyone offer any advice on solutions?
 
Enicomb said:
Ok, so I'm having trouble configuring the network interface on my windows server 2003 KVM install.

I've tried installing it using 'virtio' as the card which shows absolutely nothing under connections.

I've tried installing it using 'realtek8139' as the card which although gives me connections cannot acquire a DHCP lease and can only connect to other devices when it's manually configured. Except it can't be accessed (including RDP) from any other device on the network.


I've already successfully installed XP in a KVM on the same machine and that works fine.

Can anyone offer any advice on solutions?
Click to expand...

I never had issues on win2003 with e1000, using the latest drivers from intel web site (Intel 1000 MT)
 
I tried using e1000 too, but that produced the same results as the realtek. However I didn't update the drivers.

Could you link me to the driver?
 
Thanks for the links! :)

Now just to get them on the VM... I was sure when I manually configured the network settings I had net access, but apparently I don't. I'm sure I read another way to get the file onto the VM, but can't find the article again, could you point me in the right direction?
 
Download the file you need and create an .iso cd image with the file inside. Then mount the .iso inside the VM

Voila! :)
 
Now why didn't I think of that. :s

Unfortunately it is still not working; I've installed the driver and the VM still can't lease an IP, even manual configuration doesn't work.
 
Enicomb said:
Now why didn't I think of that. :s

Unfortunately it is still not working; I've installed the driver and the VM still can't lease an IP, even manual configuration doesn't work.
Click to expand...

win2003 works always, so I assume the problem is not inside the win2003.


  • did you install your server from the ISO?
  • or is it in a data center?
post your Proxmox VE network config:

Code: 
cat /etc/network/interfaces
and also the output of:
Code: 
pveversion -v
 
Yea I'm struggling to see that it's a win2003 error too.

Here are the outputs you requested:

cat /etc/network/interfaces

auto lo
iface lo inet loopback
pre-up iptables-restore < /etc/iptables.up.rules

iface eth0 inet manual
iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.20
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_stp off
bridge_fd 0

auto vmbr1
iface vmbr1 inet static
address 192.168.1.21
netmask 255.255.255.0
bridge_ports eth1
bridge_stp off
bridge_fd 0


pverversion -v

pve-manager: 1.3-1 (pve-manager/1.3/4023)
qemu-server: 1.0-14
pve-kernel: 2.6.24-8
pve-kvm: 86-3
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.1-2
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1


I have physical access to the server, though I didn't install proxmox. I'm installing win2003 from an ISO uploaded through web admin page.
 
Like I say I didn't set up the server, but I can only assume the guy who did it was for fail over, but I am unsure to be honest/
 
I am pretty sure that the issue is due to your custom network setup on Proxmox VE.
 
Ok, so manually setting up the IP has now worked; it still can't lease one from DHCP though.

All I did since was install the Intel driver.
 
You must log in or register to reply here.
Top Bottom