About icecream_

icecream_ · ‎11-18-2009

Updating to 6.4 R4 fixed all issues with the way I initially had things setup. I went back to my config, updated, and everything worked fine. Still wouldn't mind knowing the purpose of the NC Server IP since support told me that it was for the DHCP relay.

icecream_ · ‎11-18-2009

I'm running IVE Version 6.4 R3 What is the purpose of the Network Connect Server IP Address? I had WAN: 4.2.2.2 LAN: 192.168.32.1 /20 NC IP: 192.168.32.100 DHCP Pool Scope is 192.168.32.1 /20 with exclusions only allowing 192.168.37.1-254 Trying to move from a local DHCP server to relaying to our Windows DHCP servers. I can take a trace from the inside interface and watch the Discover, offer, Request take place where the DHCP server offers 192.168.37.1. The relay agent set is 192.168.32.1. To get things resolved quickly assuming I had a small configuration error I opened a configuration ticket. Support had me change the NC IP to 10.200.200.200, change my LAN IP to 192.168.32.1 /24, and change my DHCP server to offer 192.168.37.1-254 /24 The relay agent is still 192.168.32.1 outgoing, although messages no longer reach the DHCP server, only discover's are sent out. Clients connected fine to local server, but never get their offers when using external DHCP servers. I've looked through the 6.4 docs for setting up DHCP but there is not much detail, I'll probably go back and get some older documentaion and hope for more detail.

icecream_ · ‎04-13-2009

Using two Juniper SA 6000s configured for a highly available cluster has yet to prevent an outage to my experience over the last year. I've heard other people sticking them behind F5s or other load balancers for this same reason. My main question is how are people implementing an HA setup that actually prevents them from having outages? Currently both round robin DNS and active/active balancing would have better results for us than using the built in active/passive clustering. (Currently running 6.0R5 Build 13073) Message Edited by icecream on 04-13-2009 06:55 AM

icecream_ · ‎12-08-2008

We have similar issues although our error rate is probably only around 5% The other annoyance we have is that there is no support for passing DHCP through to a microsoft dhcp server to allow easy updating of DNS for out Network Connect clients. The issue it causes us is that our help desk will try to access their computer by computer name. The fix for this is in our login script. Unfortunately, most network connect related calls are for drives not mapping, which is also in the login script...

Re: External DHCP issue/Purpose of Netconnect Serv...

External DHCP issue/Purpose of Netconnect Server I...

High Availability Cluster that actually works?

Re: Session Start Scripts in NC