No route to host errors

[sid]

Hello,

Does anyone know where I can find the documentation on how to setup the route to host. I'm tryin to set up a windows box and a RedHat box and for both I keep getting "No route to host" errors. I know it is something really small, but I don't know what I'm missing.

I checked the v1.1 documentation page for the installation guidelines and i've followed them all. I still am not able to fix this issue. Is there any page specific to setting up routes to hosts???

I appreciate any help. Thanks.

[raminix]

Sounds like a basic networking issue from point A to B. I'm assuming the Windows and RH boxes are the ones with the issue. Are you able to ping the Windows box from RH or vice versa? If not, are both on the same network/subnet? If not, have you checked your routing table? With that type of error, you're going to want to start from the ground up and make sure you have basic connectivity from one machine to the other.

[befortin]

Could you please post your agent's configuration file?

[sid]

I figured it out...thanks for the help.

[mary nancy]

Dear Sid,



Even i am getting the same error "No Route to the Host" for most of my windows and solaris clients. Pleae can you share the solution


Thanks
Nancy

[kahala]

not a network problem

I am seeing this error in zabbix_agentd.log but most systems are working fine. Furthermore, the network works fine. on the machines where I see this I can can ssh to the zabbix server by name and by ip. This message makes no sense. Why is it showing up?

The only thing I can figure is that zabbix is being stupid when given an IP address for the server and tries to do a dns lookup on the IP address--which isn't going to work of course. in my case the server name isn't in dns either. I have entries in /etc/hosts.

This is in the sample config and it is what makes me suspect the above
# List of comma delimited IP addresses (or hostnames) of ZABBIX servers.
# No spaces allowed. First entry is used for sending active checks.
# Note that hostnames must resolve hostname->IP address and
# IP address->hostname.

BUT resolve how? dns? is /etc hosts not enough?

[cptnzod]

I can think of this scenario: You have multiple IP or NICs on the Agent. When you start the agent it is listening on one IP and your server is trying to get to it via another IP?

[extremoburo]

firewall issue....