Active Member
Topics: 0 / Replies: 11
Reply
RE: dedibox sc 2016 - windows 2016 - no access after deploy

Thank you for this answer. No clue with the SC 2016 problem ?

5 years ago
Reply
RE: dedibox sc 2016 - windows 2016 - no access after deploy

Can you confirm that the dedibox XC 2016 will work with Windows 2016 server image ?

5 years ago
Reply
RE: dedibox sc 2016 - windows 2016 - no access after deploy

I had try Microsoft_Windows_Server_2012_R2_Datacenter_Evaluation_64-bit_US_English.gz with same result. No Ip by the DHCP online.net

5 years ago
Reply
RE: dedibox sc 2016 - windows 2016 - no access after deploy

And now, RDP exchange in Qemu mode. client RDP successfuly connect to server RDP-qemu-mode.jpg

5 years ago
Reply
RE: dedibox sc 2016 - windows 2016 - no access after deploy

I have put manually IP (by scheduled task) The server can ping an outside IP (8.8.8.8 by exemple) When I Try to catch traffic with wrireshark. I c...

5 years ago
Reply
RE: dedibox sc 2016 - windows 2016 - no access after deploy

🙁 wich information can I give you to resolve this issue ?

5 years ago
Reply
RE: dedibox sc 2016 - windows 2016 - no access after deploy

I had open a ticket at Online.net. They told mes that there are no problem on their infrastructure... Where is the problem. Why this deployment imag...

5 years ago
Reply
RE: dedibox sc 2016 - windows 2016 - no access after deploy

With rescue mode (Ubuntu 14) Qemu : wget -qO- /tmp | tar xvz -C /tmp launch serveur in emulated mode : /tmp/qemu-system-x86_64 -net nic -net user...

5 years ago
Reply
RE: dedibox sc 2016 - windows 2016 - no access after deploy

Template Name: Microsoft_Windows_Server_2016_Datacenter_Evaluation_64-bit_US_English.gz Vendor: Online.net Vendor Service Package: dedibox SC 2016...

5 years ago
Reply
RE: dedibox sc 2016 - windows 2016 - no access after deploy

I found information in the event viewer : Your computer was not assigned an adress from the network (by the DHCP Server) for the network Card with ...

5 years ago