Also, what do you see in the Tracker logs?
Main Topics
Browse All TopicsHello everyone, we have just setup a cluster using NGX-R65, with (2) ip560's, everything works except our vendors that use Radius for authentication, when they connect it tries to go to "qcfw1" first and that fails saying "radius server not responding", but then if they continually try usually after (3-4) times it tries "qcfw2" and they get in. On our radius server; Microsoft, we have both ip address's assigned with their designated ip's, but it still fails till it finally rolls over to 2nd device. Securemote users that use securid have no issue?
Where do i begin to look?
Al
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Could you check that you can ping the radius server from qcfw1 - assuming that the radius server replies to pings. If not please try connecting to another tcp service on the box.
If the server does not reply then you would need to check a traceroute and devices (switches, routers) in between to find out where the connection is dropping.
If it does reply then we will need to do the packet captures.
thanks, now it says:
qcfw1[admin]# fw monitor -e "accept src=172.16.1.11 dst=172.16.2.10;" -o monitor.cap
monitor: getting filter (from command line)
monitor: compiling
monitorfilter:
"/opt/CPsuite-R65/fw1/tmp/
Compilation Failed.
monitor: filter compilation failed /opt/CPsuite-R65/fw1/tmp/m
You should see 4 entries for each packet but you'll need to set wireshark up to interpret the capture as a fw monitor file, see here for details: http://blog.empirion.co.uk
Check to see whether your packets destined for qcfw1 are actually leaving the firewall and if so what is happening to them. Is the radius server replying? Are the packets timing out?
This should help to identify where the problem is occurring i.e. at the firewall or radius server.
ok, that link helped a lot, I see where it is rejecting the request from the radius server, which would lead me to believe it was firewall, plus in another article it said that the keys might not match. So qcfw1 will not allow authentication through radius, saying server does not respond, BUT, qcfw2 does. I then went into radius server and re-entered key for qcfw1, went into object on firewall for radius server and retyped key... Guess what now qcfw1 works, but NOT qcfw2???????????????
Business Accounts
Answer for Membership
by: grimkinPosted on 2009-09-25 at 01:41:18ID: 25421047
Hi,
How is your cluster set up? HA or load-balancing?
Try taking a packet capture on both firewalls simultaneously and check what is being done with the incoming packets. If you are familiar with fw monitor then this would be the best way:
fw monitor -e "accept src=<IP1> or dst=<IP1> or src=<IP2> or dst=<IP2>;" -o monitor.cap
where <IP1> is the IP of your radius server and <IP2> is the IP of your incoming client
Compare the 2 and see how the traffic from the client is being handled.
HTH