Hi, We just installed an Openfire XMPP Instant Messenging Server (http://www.igniterealtime.org/projects/openfire/index.jsp) at our company. I'm trying to use a web-based flash chat client called SparkWeb (http://www.igniterealtime.org/projects/sparkweb/index.jsp) to connect to the Openfire server. I have a web link set up in our SA 2000 for http://server/sparkweb/SparkWeb.html. The website loads up OK. But I can only authenticate if I am connected to Network Connect. When I am not tunneled, I get an error saying "not authorized." I am using LDAP authentication with Active Directory 2003. It tries to make a socket connection to port 5222 on the Openfire server. This works fine within our LAN and when using the Juniper web link while tunneled. But I would like to get this working without being tunneled. We have opened ports 5222 and 5229 in our firewall with no luck. Is there some type of policy I need to set in Juniper? I do not see any errors in the logs in Juniper or Openfire. Thank you. ... View more

Where do I start!? Upgraded SA2000 OS to 6.2R1 and the Network Connect is very unstable. 1. Several users are getting this error when trying to connect to Network Connect. "nc.windows.app.23791 - The secure gateway denied the connection request from this client." I can log on as a different user on the same PC and it works. 2. Many users are complaining that their sessions keep getting frozen up or disconnected. 3. GINA plug-in was made useless! The NC login screen now comes up AFTER the Windows login screen instead of BEFORE it. The whole reason we implemented the GINA plug-in was to fix password problems for remote users. Sometimes #1 and #2 are resolvable by uninstalled NC 6.0.0 and NC 6.2.0 clients and then letting NC 6.2.0 reinstall. But sometimes they are not. Any suggestions? Anyone else have this problem? Should I rollback? Help! Thanks! ... View more

Good Morning, We recently upgraded our SA2000 to OS 6.2R1 (build 13255) from OS 6.0R5 (build 13073). I am now seeing entries on almost every line of the event log saying "Cannot determine realm for AD server 4." This error did not start until just after the upgrade. Users are still able to log on without a problem. But this error must mean something. I opened a case with JTAC, but they said they never saw this error before and suggested to check settings on our domain controllers. They also had me create a new realm and new auth. server, and it got the same error. I have verified that the AD server settings are correct. I tried specifying the Kerberos realm name on the auth. servers page instead of having it use LDAP to get Kerberos realm name. The Test Configuration was fine. But I then received this error in the Event Log: " realm ######## failed: Wrong realm." Has anyone seen this error before? Any suggestions? Is this a bug with the new OS version? Thanks! ... View more