DCE on hyper-v network issue

[Gabi]

hello

i have a problem with  DCE configuration on hyper-v virtual machine

installed version 8.1.1/8.2/8.3 on Hyper -v 2019 and 2022 with the addition of the private network card when creating the virtual machine or after start it

the problem is that I can't change the setting of the private interface....basically I get messages that the ip address is changing but nothing happens and when I enter the network menu, all the settings are the initial ones

also in console menu of dce I do not receive the message for activation private network....when I adding the network card after first reboot, in the menu appear as absent but I can see it on client

thanks

[APC_Steve]

Hi @Gabi ,

I'd probably need more information on the settings. You state:
"the problem is that I can't change the setting of the private interface....
basically I get messages that the ip address is changing but nothing happens and when
I enter the network menu, all the settings are the initial ones"

Are you changing them from the desktop client or the console menu? You may want to speak with tech support directly as I don't want to ask for the specifics online but knowing the IP schemes of both public and private LANs may be helpful. We'd also want to look at the logs of the server which we don't want to share here.

Have you tried adding the secondary NIC to the VM prior to the initial boot of the system? That's always what I suggest. 

Thanks,

Steve

[Gabi]

Hello,

the issue was simple.....on deployment, someone set a .local hostname and invalid tld extension is not accepted 🙂 .....apcsetup script is configured to check domain extension, if is not valid, request again to enter a valid hostname, but if you enter second time the same non existent tld, wizard accept that name but you cannot change private network from client and apcsetup wizard skip configuration for private network 

Maybe is possible from developing team, to force and not continue wizard if user use non existent tld

thanks

[APC_Steve]

Hi @Gabi ,

Just speaking with engineering and it seems that was something they'd already been working on. I'm told that the next release (9.1) due out in an "estimated" few weeks addresses that exact issue. You seem to have resolved it for yourself though and I'm assuming you entered a fully qualified domain name and that worked. I'm also told that instead of <domain>.local, you should be able to use <domain>.localdomain in 9.0 and prior.

Glad you figured it out,

Steve