Can't connect to the server

[wuw]

Version

When I try to connect to any of the shares I keep getting " Windows cannot access \\FREENAS\pathname"
When I try to open the web interface I keep getting "web page not available" (I tried in firefox ie and chrome)
At the console it keeps displaying Nov 10 07:20:26 freenas ntpd_initres[1898] : host name not found 0.freebsd.pool.ntp.org
The only thing that is different inbetween eack time it comes up is the time and the number in the address 0.freebsd.pool.ntp.org

 

[SweetAndLow]

Hardware specifications and version of FreeNAS? And did it ever work?

 

[wuw]

It worked up until today. I had to turn it off to add in some new servers and had to move the Free NAS. When I turned it on that is what came up. It is using 9.1.1 x64. I don't recall the specs.

 

[gpsguy]

It can't find an external server.

My guess, is that it's either not connected to the network, connected to the wrong NIC, or you've got a bad cable.

What IP address is it on? Can you ping the server from a workstation? Did you have a static IP address on it? If DHCP, did it change? Check your DNS settings - normally this would be my first suggestion. But, since you moved the server, it could be something simple, like I suggested earlier.

host name not found 0.freebsd.pool.ntp.org

btw, if you don't know the spec's, take time to document it. The forum rules ask you to provide it. And, it'll probably help you down the road.

 

[Ericloewe]

Don't recall the specs? That's never a good sign.

 

[wuw]

I tested and checked the cables and double check everything. Its not layer 1. I can't ping the server. It is a static address 192.168.2.4. It is only a class C (going to move everything to a class A with in the next year) I tested and there is nothing on my network using the same address. It is outside of the DHCP range that I have.

Specs here
Intel Xeon E5645 Westmere-EP 2.4GHz 12MB L3 Cache LGA 1366 80W Server Processor
Dual LGA1366 Intel Xeon 5600/5500 Series
Wintec 24GB (3 x 8GB) 240-Pin DDR3 SDRAM ECC Registered DDR3 1333 (PC3 10666) Server Memory Model 3SH13339R5-24GT
Patriot Supersonic Pulse 16GB USB 3.0 Flash Drive Model PSF16GSPUSB
5 x 2 TB WD RED ZF2 raid
1 x 1 TB seagate

 

[Mlovelace]

At the server console run

Code:

ifconfig -a

and see if the interface is active. Is the new switch port the FN is plugged into configured correctly (right VLAN, dhcp forwarder...)?

 

[wuw]

Yes the interface is active. It is plugged into the same port as it was before everything is configured correctly.

I should also note I am a CIO of a local company. And that built the network from the ground up. I will double check everything suggested. This problem I am having is not at my business but my personal NAS.

 

[Mlovelace]

Can you ping out from the NAS's console? You could try resetting the network interface, gateway and DNS.

 

[anodos]

Yes the interface is active. It is plugged into the same port as it was before everything is configured correctly.

I should also note I am a CIO of a local company. And that built the network from the ground up. I will double check everything suggested. This problem I am having is not at my business but my personal NAS.

I don't hold a single certification in anything. Well... I think I was CPR certified once.

Anyway, USB flash drives are pretty much uniformally crap. After you complete the basic boring network diagnostics (and assuming you don't get anywhere) try a fresh install of freenas on a different USB flash drive. If it works, try uploading your old config.

 

[wuw]

I reset the interface I check the gateway I check the DNS. No I can't ping it. I tried pinging it from the router and the switch and cant get to it. I recheck all on the networking settings. Note it everything was working earlier today. I only shut down the server so I could move it 2RUs everything else is the same.

I read on the FreeBSD fourm that "ntpd_initres[1898] : host name not found 0.freebsd.pool.ntp.org" can be caused by the NIC not responding in time. They also show a rc script that they claim to fix it. It looks fairly straight forward. I will ask my Linux guys tomorrow about it. I would like to know the FreeNAS pros think about this?

Code:
#!/bin/sh
#
# PROVIDE: wait_for_network
# REQUIRE: NETWORKING
#

. /etc/rc.subr

name="wait_for_network"
start_cmd="${name}_start"
stop_cmd=":"

wait_for_network_start()
{
echo "waiting 30 seconds for network!"
sleep 30
}

load_rc_config $name
run_rc_command "$1"

 

[depasseg]

The ntpd issue is likely just a symptom of the main problem which appears to be no IP connectivity. I would ignore ntpd and just focus on fixing IP.

Start at layer 1 and work your way up.

Have you tried arping?

 

[Mlovelace]

Do you have your configuration backed up? @anodos suggested dd'ing a new USB and uploading your config.

 

[Mlovelace]

... I think I was CPR certified once.

I've got that one! I was a lifeguard in high school (a 100yrs ago);)

 

[wuw]

I tried ARP it is in the table but it is marked inactive. I will clear the ARP tables once I get home. If that doesn't work I will give the script a try and after that I will go with a new install and then update it. All the script does is give the NIC time to settle down before coming online.

 

[wuw]

I've got that one! I was a lifeguard in high school (a 100yrs ago);)

I too was a Lifeguard in high school but not 100 years ago.

 

[no_connection]

If the problem is not found in Layer 1-7 then it must be a Layer 8 problem.

I doubt the script would do much good.

Do you have Layer 2 connectivity to the router or switch?
Layer 3 in both/one or zero directions?

 

[depasseg]

The script is running the ntpd service which is trying to sync your clock via IP. IP isn't working, hence the errors. Specifically, the error is that a hostname can't be resolved. I'm guessing because your host can't reach it's DNS server. Fix the IP problem.

 

[Mlovelace]

The script is running the ntpd service which is trying to sync your clock via IP. IP isn't working, hence the errors. Specifically, the error is that a hostname can't be resolved. I'm guessing because your host can't reach it's DNS server. Fix the IP problem.

Could be an ID-10T error.

Did you try testing if the FN server interface can get out, like I had said before, try pinging from the FN console (option 9 as I renember)?

 

[depasseg]

1. ping 127.0.0.1
2. run ifconfig -a
3. ping your local address(s)
4. run netstat -r
5. ping the gateway ip address
6. cat /etc/resolv.conf
7. ping each ip address next to "nameserver"

Compare the settings from above to those listed in your network summary tab, and compare those to what you believe they should be.