Guide to Port Forwarding?

[brendonwp]

@toby - I can ping from FreeNAS shell to the router but not beyond the network. Restarting LMS doesn't change this. So it does look like it could be that the gateway address needs to be set.

@bfl: thanks, will follow this up. My router does DHCP and all the machines take their addresses from it, except the FreeNAS/LMS server which is on a static IP.

Cool handle btw

Edit: I changed the gateway setting to my router's IP address on FreeNAS, but no improvement. Anyway, my Proliant Microserver has arrived at last and I'm going to try installing on there rather than carry on wrestling with a VM.

Thanks all for the advice!

[toby10]

@toby - I can ping from FreeNAS shell to the router but not beyond the network. Restarting LMS doesn't change this....

Yeah, the NAS not seeing the internet would indeed be a problem.

Correct, re-booting LMS will not solve that, but it's a quick way to solve another common NAS networking issue that is much easier to resolve by a simple LMS re-boot. NAS boots can be very slow and often other programs like LMS auto-startup before the NAS has completely booted. In these cases LMS is not given the proper networking protocols by the NAS because the NAS has not fully resolved networking itself do to it's slow bootup. A simple LMS re-boot resolves it. If your NAS is not seeing the internet at all, that is a whole other can of worms.

[Mnyb]

@toby - I can ping from FreeNAS shell to the router but not beyond the network. Restarting LMS doesn't change this. So it does look like it could be that the gateway address needs to be set.

@bfl: thanks, will follow this up. My router does DHCP and all the machines take their addresses from it, except the FreeNAS/LMS server which is on a static IP.

Cool handle btw

Edit: I changed the gateway setting to my router's IP address on FreeNAS, but no improvement. Anyway, my Proliant Microserver has arrived at last and I'm going to try installing on there rather than carry on wrestling with a VM.

Thanks all for the advice!

Or a missing DNS setting in the NAS for example ?

[banned for life]

Or a missing DNS setting in the NAS for example ?

+1

Handy to remember: Google public DNS servers are 8.8.8.8 and 8.8.4.4

They tend to be speedy as well.

bfl

[banned for life]

@toby - I can ping from FreeNAS shell to the router but not beyond the network. Restarting LMS doesn't change this. So it does look like it could be that the gateway address needs to be set.

@bfl: thanks, will follow this up. My router does DHCP and all the machines take their addresses from it, except the FreeNAS/LMS server which is on a static IP.

Cool handle btw

Edit: I changed the gateway setting to my router's IP address on FreeNAS, but no improvement. Anyway, my Proliant Microserver has arrived at last and I'm going to try installing on there rather than carry on wrestling with a VM.

Thanks all for the advice!

I didn't know you were running in a VM. This is actually better, depending on what VM manager you are using. I use VMWare WS and it is a thing of beauty but I had issues with virtualbox. In VMWare, set the network adapter to bridged.

Of course, I am using Vortexbox in the VM. It just does not get any easier. Set the VM network adapter as above, reboot, and then use the web interface to vortexbox to static the address. A word of advice: vortexbox is a little stupid when your VM is not on eth0..

I had to set the memory to satisfy vortexbox for install but afterward I set it to 512MB and performance is stellar.

bfl