I type the switchdns ip
(primary dns 10.0.2.XX)
I save and don't work
--------------------- MERGED ---------------------------
(normaly the switch language is french but for the screenshots I put it in english)
View attachment 106302
View attachment 106303
View attachment 106304
I type the new dns in primary dns but it says that incorrectYou are using VirtualBox, I presume. While the VM is closed, click so that your Ubuntu VM is highlighted, click Settings, click Network, use a new network tab to choose Attached to: Bridged Adapter, expand Advanced, and for Adapter Type choose PCnet FAST III
And uncheck Enable Network Adapter for any other network adapters, you just want this one enabled. You can re-enable them later. This ensures Pegaswitch will choose the right one.
what does PegaSwitch say the new dns is? don't worry about posting, its internalI type the new dns in primary dns but it says that incorrect
switch DNS IP : 127.0.0.1what does it say the new dns is? don't worry about posting, its internal
can you confirm all your network devices are disabled in VirtualBox except for one, and it looks like this:switch DNS IP : 127.0.0.1
Primary DNS : 127.0.0.1
And when I click on ok ("+")
incorrect address
can you confirm all your network devices are disabled in VirtualBox except for one, and it looks like this:
https://drive.google.com/file/d/1IOYOIBy97UIYDF8YPah8m9tVI1AdflW9/view?usp=sharing
Important is that
- Enable Network Adapter is checked on only this tab
- Bridged
- PCnet II
- Cable Connected is checked
don't worry about MAC
Ok, Bridged Adapter was better it seems. That is um... truly strange... I'm trying to think of what could be wrong. You should typically see an internal IP beginning with 192.168.xxx.xxx or 10.xxx.xxx.xxx occassionally, but never 127.0.0.1, it means the VM is not connected to your network.Ubuntu isn't connected now ?
View attachment 106306
It's possible but why and how to resolve it ?Ok chang
Ok, Bridged Adapter was better it seems. That is um... truly strange... I'm trying to think of what could be wrong. You should typically see an internal IP beginning with 192.168.xxx.xxx or 10.xxx.xxx.xxx occassionally, but never 127.0.0.1, it means the VM is not connected to your network.
Yes you could try replacing PCnet III with Intel Pro/1000 MT Desktop, but that one is less reliable for me sometimes. Worth a try though.
It's possible but why and how to resolve it ?
--------------------- MERGED ---------------------------
before use the bridged adaptater, I was connected
I get another dns ip but nothing changeI have another idea if you are down. Leave the Host-Only Adapter enabled, but in tab 3 enable an NAT adapter, like the one you originally had. If a new NAT is recognized perhaps PegaSwitch won't recognize it as the default this time, but even if it does there is a simple parameter to make PegaSwitch choose a specific IP, but let me know if that works.
Thats ok, as long as its not 127.0.0.1. Now open a terminal and type inI get another dns ip but nothing change
yes, only the 2 and then only the 3Are you tryed to use only one adapter like me?
yes, only the 2 and then only the 3
I test your now