Unable to access FreeNAS from Windows

[balanga]

I've been happily accessing FreeNAS from Windows for the past couple of months getting familiar with how things work, but now all of a sudden the two machines don't speak to each other. Not sure that I intentionally did anything to cause this.... Another system using Arch Linux can communicate with both

FreeNAS is 192.168.0.4 and Windows is 192.168.0.2. and both a directly connected to my router.

I can access FreeNAS from my tablet without any problem and I can access the Internet from Windows but PING does not work from either system.

I guess Windows is blocking FreeNAS in some way.... Is there any way to tell where the problem lies?

 

[Ericloewe]

What do you mean? Can't you access the WebGUI, a share, ...?

 

[balanga]

Well if PING doesn't work then nothing else will...

 

[Darren Myers]

is the FreeNAS server on DHCP, if not did you put in the right subnet, default gateway, IP range? Can you post hardware specs, mobo, ram, cpu, hdds, psu, etc.

 

[DifferentStrokes]

Well if PING doesn't work then nothing else will...

Your OP is a bit hard to understand exactly what you are trying to say. I believe that @Ericloewe is more than willing to help you, but that tone of voice may change his mind.

 

[Ericloewe]

Well if PING doesn't work then nothing else will...

That's a rather simplistic view. It's not uncommon to not reply to random pings.

Start by disabling antivirus firewalls and similar stuff.

Kaspersky 2011 (or was it 2012?) always blocked WHS 2011's stuff and it was a pain, with no viable workaround other than turning it off. Magically fixed in 2012 (2013, respectively).
Sounds sleazy, but the updates are actually free. Licenses are good for whatever the latest version is.

 

[balanga]

Thanks for all the replies. I've been playing with networks for over 20 years and it is still a black art to me. I had a working setup - wireless/router/cable modem, FreeNAS, several Windows laptops and numerous phones/tablets. Yesterday my router hung, but after some time including several resets it came back up. I was unable to access FreeNAS from my main laptop which is cabled to the router. I tried several reboots on both systems both they would not communicate. Accessing FreeNAS from a tablet was no problem.

Several hours later after coming home from work I take a look at my systems and VOILA! everything works as it should....

I'm stumped!! I don't know if I did anything or if there exists some sort of self-healing property in a TCPIP network....

On thing I have noticed today is that I get the msg:-

You must configure a default route (Network->IPv4 Default Gateway)

if I click on Plugins or Jails within the GUI.

Not sure how that occured, but I've just configured it via the operators console.