Timeout problems

[GISD]

We are using Bordermanager with surf control. When users first open up IE they cannot do anything for the first 30-45 seconds (I assume its synching with the cltrust key thing) and goes to the 403 error page. We get a lot of work order requests telling us they cant browse at all because once they encounter the original timeout they stop trying to use it. Is there anyway to reduce or eliminate the timeout when first opening IE?

 

[Lou0686]

Hi,

First off the 403 error is accompanied by another error. For instance Forbidden "Access Has been denied because you are not logged in."

Which error are you getting?

The following items may help:

1. Updating to the latest Client Trust may help.
2. Running the client trust from the login server or from the PC.
3. Upgrading to the latest Novell Client.

Lou

 

[GISD]

Yeah, Im getting this:

HTTP Error
Status : 403 Forbidden
Description : Access has been denied because you are not logged in!
Note : If necessary, please contact your Systems Administrator for resolution.

I think we are running the newest Novell Client. Are you saying update the CLtrust file? Where do I get that exactly?
And I dont understand what you mean by running the client trust from the login server. We are running that file at each PC though. Thanks for all your help!

 

[Lou0686]

Hi,

Check out TID 10072020 for the latest Proxy and Client Trust.

Client Trust can be run locally on the PC or from the Public directory of the login server. Try copying it to that directory and have a few PCs point to that file to see if it makes a difference. I read somewhere that Client Trust first look at the local PC (if running locally) for the info it needs, then to the login server and then to Border. That's 2 steps and may time out at times. You can eliminate one step by copying it to the Login server this way one step is omitted and therefore eliminate the timeout.

Lou

 

[XFire]

Well, it may not be related at all but this is a situation i recently discovered in the network i have inherited.

An isolated group of users were having sporadic timeout problems when accessing the internet via the BorderManager firewall. Bypass the firewall and there was no problem. I found that the two NICs used in the firewall server were patched to different network hubs. I suspected that this must have caused unaccetptable delays when there was a lot of network traffic and hence resulted in a time out. Repatching the NICs to the same hub fixed the problem.

Good luck

 

[Lou0686]

Hi Xfire,

Are you saying that you have both the Public and Private NICS connecting to the same hub?

Lou

 

[GISD]

We figured out that their is a place on the server to set a time to allow connection. It was set to like 5 seconds and people couldnt get authenticated fast enough. We increased this to 45 secs to allow more time. Problem solved. Thanks guys.