I figured out the Internet Explorer problem. I had to use a DNS name
in
the proxy settings like Macs do. Once I put that in there the Citrix

terminal servers would actually display the correct web page after I pasted the session id. I then installed the browser client again and
it
automates the process correctly. If I close the browser I have to
enter
the SSL creditionals again like it is supposed to. Thanks to all for your help.

Gary

Gary Dosey wrote:
> Correction the last line is a typo it should say is the browser

client
> supposed to work with Netscape?
>
> Gary Dosey wrote:
>
>> Thanks for the tip Gonzalo. It was set to the default at yes. I

tried
>> changing that registry setting but it did not help. The behavior

of
>> Internet Explorer did not change I actually found that registry key

in
>> the registry three times under different sections. So I changed

each
>> one only and rebooted after each. I also reversed the setting and>> rebooted each time to see if it made a difference and no avail. So

after
>> that I switched all the settings to no rebooted and it didn't work

so I
>> switched all the settings back to yes and rebooted and it still

didn't
>> work.
>>
>> Scott thanks for getting the post SP2 patches out.
>>
>> I then tried the FP3 patch and after installing it I got Netscape

to
>> actually display the page correctly in only about 2 of 6 times but

I
>> had to manually copy the session id and paste it into the password


>> screen. If I kept closing Netscape and restarting and loging in it


>> wouldn't let me in it would just kind of hang on the screen trying

to
>> log me in with the session id. The url it would hang on is
>> https://10.25.5.1:443/BM-Login/auth-cup. For Internet Explorer I

didn't
>> get the SSL login it simply went to page can not be displayed. I

then
>> back reved the proxy NLM to the 1/10/2003 and got the same results.

I
>> then decided to reinstall service pack 6 for NetWare. I then

restarted
>> the BorderManager server at this point.
>>
>> After that I tried Netscape and it would only work about 2 of 6

times.
>> I started Internet Explorer it displayed the SSL screen after I

logged
>> in it went to a page not can not be displayed. So I went to a

server
>> that I didn't install that browser client and it did show the

session
>> id screen after I entered my SSL login but did not bring up the

screen
>> to enter a password it just went to a page can not be displayed

page.
>> So I think the browser plugin is working with Internet Explorer

just
>> whatever
>> is supposed to receive the session id is not. Netscape seems to

work
>> correctly if I don't install the broswer client on the machine. I >> don't know why on Netscape if i install the browser client I get

the
>> session id and it doesn't get passed to the browser. I was

thinking
>> that Browser plugin was supposed to work for Internet Explorer and


>> Netscape. For what it is worth I am using Netscape 7.02. I then
>> changed back to the proxy.nlm that was included with FP3 and I got

the
>> same results as with the old proxy.nlm.
>>
>> Does that give anyone any ideas on what I could try to fix the
>> receiving of the session id in Internet Explorer? Is the browser
>> client supposed to work with Internet Explorer?
>>
>>
>>
>>
>>
>>
>>
>> mysterious wrote:
>> > Gary,
>> >
>> > if you are seeing this behavior using cookie based

authentication, the
>> > problem is coming from windows setting to control the sharing of


>> cookies
>> > on the same machine. A registry key seems to control this

behavior.
>> > I could not find any reference to this on the Microsoft support>> > site, but I've toggled the setting back and forth several times

and
>> had
>> > repeatable results. The key is "BrowseNewProcess" located at:
>> >

>>

"HKEY_CURRENT_USER\Software\Microsoft\Windows\Curr entVersion\Explorer\BrowseNewProcess".

>>
>> >
>> > If set to yes (default) there is a new instance of IEXPLORE.EXE

for
>> > each new invocation of IE and there is no sharing of cookies.
>> >
>> > If set to no, then no instances of IEXPLORE.EXE are created and>> > EXPLORER.EXE is the only process that is used no matter how many

times
>> > you invoke IE. This results in apparent sharing of cookies and >> sometimes
>> >
>> > the session cookie is saved even when all IE windows are closed.


>> >
>> > hope it helps
>> >
>> > Gonzalo
>> >

>>
>>
>>

>