FreeNAS Virtual Machine

[Jamie.bark1]

Hi, im relatively new to FreeNAS and virtual machines. I've been running a virtual machine inside my FreeNAS for almost a year now, however today i received a new router from my ISP and once i installed it the virtual machine has stopped working. Well, its running however whenever i try to connect to it using a VNC i get: 

This site can’t be reached

*i have removed my IP for security*refused to connect.

Try:

• Checking the connection
• Checking the proxy and the firewall

ERR_CONNECTION_REFUSED

 

 

 

 

Has anyone got any ideas? Thanks in advance...

[PorkishPig]

The virtual machine likely has a new IP. What virtualization and VNC software are you using?

[Jamie.bark1]

Im just using the VNC tool through FreeNAS. Ive tried to connect to it using 'VNC Viewer' on windows but still no luck. The FreeNAS IP has changed but i am connecting to the VM through the new IP. I really dont know what to do.

[Windows7ge]

Did you reserve the IP assigned to the VM? Did you configure a Static IP on the VM? It sounds like the IP DHCP likely gave it changed.

[Windows7ge]

It's also possible the new router have put everything on a new network. This would also result in not being able to connect.

[Jamie.bark1]

11 minutes ago, Windows7ge said:

Did you reserve the IP assigned to the VM? Did you configure a Static IP on the VM? It sounds like the IP DHCP likely gave it changed.

 

4 minutes ago, Windows7ge said:

It's also possible the new router have put everything on a new network. This would also result in not being able to connect.

Hi so i know very little when it comes to this sort of thing. All ive  done is plug the new router in and try to connect to my VM. I am able to connect to the FreeNAS however its IP has changed: its now .11 whereas it was .29 before. 

 

What would you suggest i do to trouble shoot my problem and find out what is causing it ?

 

Thanks and i apologies in advance for my lack of knowledge.    

[Windows7ge]

What you need to do is assign a static IP address to the VM. I would also recommend doing the same to FreeNAS.

 

The easy way is reserving the IP using the MAC address but you can also setup IPs manually then shrink the DHCP pool so those IPs don't get handed out.

[Jamie.bark1]

27 minutes ago, Windows7ge said:

What you need to do is assign a static IP address to the VM. I would also recommend doing the same to FreeNAS.

 

The easy way is reserving the IP using the MAC address but you can also setup IPs manually then shrink the DHCP pool so those IPs don't get handed out.

The IP address for the VM is just the IP of the FreeNAS and then :5760. So would the VM not chaneg IP with the FreeNAS? Ive tried connecting to the VM using its old IP and the webpage just times out. 

 

How do i change the IP of my VM with FreeNAS i cant seem to find and tutorials and there doesnt seem to be an option in the interface. 

Thanks again.

[Windows7ge]

16 minutes ago, Jamie.bark1 said:

The IP address for the VM is just the IP of the FreeNAS and then :5760. So would the VM not chaneg IP with the FreeNAS? Ive tried connecting to the VM using its old IP and the webpage just times out. 

 

How do i change the IP of my VM with FreeNAS i cant seem to find and tutorials and there doesnt seem to be an option in the interface. 

Thanks again.

Is it a Windows VM?

 

What version of FreeNAS are you running?

[Jamie.bark1]

3 minutes ago, Windows7ge said:

Is it a Windows VM?

 

What version of FreeNAS are you running?

Yeah its a Windows VM and im on the latest FreeNAS version.

 

[Windows7ge]

1 hour ago, Jamie.bark1 said:

Yeah its a Windows VM and im on the latest FreeNAS version.

 

So you aren't connecting directly to the VM you're connecting to the FreeNAS VNC server. That would be why the IP is the same as FreeNAS's.

 

Looks like you want to go to Network -> Interfaces.

 

You probably only have one entry. Click the drop-down arrow on the far right.

 

Click edit. You'll see a little box highlighted next to DHCP. Un-tick it.

 

Now where it says IP Address use one within your networks range. It's important that your Router doesn't hand it out though so I'd use an IP in the high-end and then shrink the DHCP pool in your router.

 

Now click Add. Apply.

 

You will have to re-connect using the new IP but then you should be able to connect to your Windows VM from the same IP:Port.

[Jamie.bark1]

8 minutes ago, Windows7ge said:

So you aren't connecting directly to the VM you're connecting to the FreeNAS VNC server. That would be why the IP is the same as FreeNAS's.

 

Looks like you want to go to Network -> Interfaces.

 

You probably only have one entry. Click the drop-down arrow on the far right.

 

Click edit. You'll see a little box highlighted next to DHCP. Un-tick it.

 

Now where it says IP Address use one within your networks range. It's important that your Router doesn't hand it out though so I'd use an IP in the high-end and then shrink the DHCP pool in your router.

 

Now click Add. Apply.

 

You will have to re-connect using the new IP but then you should be able to connect to your Windows VM from the same IP:Port.

Thanks for your help so far. But ive had a look and i dont have any entry's under  Network -> Interfaces. Do you know why this is? 

Thanks.

 

[Windows7ge]

4 minutes ago, Jamie.bark1 said:

Thanks for your help so far. But ive had a look and i dont have any entry's under  Network -> Interfaces. Do you know why this is? 

Thanks.

 

Peculiar...does anything show up under Network Summary?

[Jamie.bark1]

3 minutes ago, Windows7ge said:

Peculiar...does anything show up under Network Summary?

This whats under network summary.

[Windows7ge]

2 minutes ago, Jamie.bark1 said:

This whats under network summary.

"re0" is suppose to be showing up under Network -> Interfaces. But nothing is there? Can you try restarting the server and see if that changes?

[Jamie.bark1]

7 minutes ago, Windows7ge said:

"re0" is suppose to be showing up under Network -> Interfaces. But nothing is there? Can you try restarting the server and see if that changes?

Yeah after a restart still nothing there!? 

[Windows7ge]

13 minutes ago, Jamie.bark1 said:

Yeah after a restart still nothing there!? 

If you go to ADD and click on Type does it give you an option called PHYSICAL?

[LogicalDrm]

*** Threads merged ***

 

Please don't post multiple times about same subject.

[Windows7ge]

If we can't set it up this way there is an alternative option I can walk you through.

[paddy-stone]

Unsure if this is related, but your nameservers might not be connecting maybe? try setting them to a public DNS like 8.8.8.8/8.8.4.4

Also you should definitely set your freenas default to a static address IMO, if not you may end up having to find out what the new address is after every reboot. And it might be beneficial to also set your VM to a static address too.

If everything worked fine before, then I would suggest setting your new router to the old subnet you used to have, that is the most likely cause of the breakage.

[Jamie.bark1]

6 minutes ago, paddy-stone said:

Unsure if this is related, but your nameservers might not be connecting maybe? try setting them to a public DNS like 8.8.8.8/8.8.4.4

Also you should definitely set your freenas default to a static address IMO, if not you may end up having to find out what the new address is after every reboot. And it might be beneficial to also set your VM to a static address too.

If everything worked fine before, then I would suggest setting your new router to the old subnet you used to have, that is the most likely cause of the breakage.

 

19 hours ago, Windows7ge said:

If we can't set it up this way there is an alternative option I can walk you through.

Hi guys sorry for not replying, i got abit fed up. So, basically im still no further forward: i tried going to go to 'ADD' in the interfaces section but there is no option for 'TYPE'. 

I think i can solve the problem by changing the VM's IP address but i dont know how to could anyone walk me through that? Thanks for all your help so far...

[paddy-stone]

5 minutes ago, Jamie.bark1 said:

 

Hi guys sorry for not replying, i got abit fed up. So, basically im still no further forward: i tried going to go to 'ADD' in the interfaces section but there is no option for 'TYPE'. 

I think i can solve the problem by changing the VM's IP address but i dont know how to could anyone walk me through that? Thanks for all your help so far...

OK, we can try.

 

First off though I need to know a few things:

 

Are you connected to your router via ethernet? and using DHCP?  this will definitely help if so. And you can alter your router's settings by connecting to it's IP address, eg 192.168.1.1?

And do you remember what your old router's subnet was? cos it sounds to me like that was what broke your ability to connect to your VM.

 

So IMO it'd be best to try that first. Go into your router's settings and look for the part that says LAN setup or similar.

There you should be able to specify what subnet you want to use and what DHCP  IP range you want to use (this enables you to have some IP addresses that aren't handed out by the DHCP server.

eg, 192.168.1.1 and DHCP range of 192.168.1.2 to 192.168.1.200

 

This would give you 54 addresses you could set manually on devices without the DHCP server also handing out those addresses and causing a conflict.

Also set the DNS/nameservers to something other than the ISP one IMO, so for example

google 8.8.8.8/8.8.4.4

openDNS 208.67.220.220/208.67.222.222

quad9 9.9.9.9

1.1.1.1

You can also just google "public DNS servers" and choose from one of those.

When the settings have been input, click OK, or apply, the router should then roboot on most routers IIRC.

[Windows7ge]

23 minutes ago, Jamie.bark1 said:

Hi guys sorry for not replying, i got abit fed up. So, basically im still no further forward: i tried going to go to 'ADD' in the interfaces section but there is no option for 'TYPE'. 

No?

 

 

23 minutes ago, Jamie.bark1 said:

I think i can solve the problem by changing the VM's IP address but i dont know how to could anyone walk me through that? Thanks for all your help so far...

If you connect to the VM using FreeNAS's IP but a different port number (because you're not connecting to the VM directly you're connecting to the VNC server FreeNAS is running to view the VM) then changing the IP of the VM won't improve the situation.

 

Since FreeNAS is being weird we can reserve the IP FreeNAS currently has in the router so it doesn't change unless you change out your router again.

[paddy-stone]

[Godlygamer23]

I use FreeNAS on a regular basis, and use the virtual machines feature. In the Virtual Machines section, select the three dot button next to one of the entries, if you have more than one. Click on Devices, and then click on the three dot button next to VNC and click Edit. You should see a section that says Bind, and an IP. It might be blank at this point due to the likely IP change. Click on it and see if there's a new IP there, and then save it. Personally, I've always had issues with configuring the network section of FreeNAS, so I would steer clear of it unless someone is with you who knows what they're doing. There are ways of fixing the mess up, but it might be a headache that's more than its worth. 

 

As far as ensuring the IP doesn't change in the future, you probably have some options within the router itself to make the IP permanent on that particular machine.