Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Connecting to Jaguar through a firewall

8 posts in General Discussion (old) Last posting was on 2000-04-05 13:40:39.0Z
Eddie Lewis Posted on 2000-03-31 04:36:45.0Z
Newsgroups: sybase.public.easerver
From: "Eddie Lewis" <eddie.lewis@inte.com.au>
Subject: Connecting to Jaguar through a firewall
Date: Fri, 31 Mar 2000 14:36:45 +1000
Lines: 19
Organization: Intecom Systems
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
NNTP-Posting-Host: mail.intecom.com.au 210.9.112.10
Message-ID: <347_D0IQmqsm$GA.307@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25147
Article PK: 154246

Our client cannot create component instances within jag (error return of 50)
when we try connecting the application to through a firewall running on
linux (6.1).

The Jag manager network monitor shows the iiop sessions increase by 1 and
after about 10 seconds, the client shows the createinstance error.

The connection works fine when we connect internally.
The firewall passes on the request ok.

We are using Jag3.5 Enterprise.

Does anyone know of any seetings we require/ things we can try (ie. log
files to check and what to look for).

Thanks
Eddie Lewis


Dave Wolf [Sybase] Posted on 2000-03-31 12:04:21.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Connecting to Jaguar through a firewall
Date: Fri, 31 Mar 2000 07:04:21 -0500
Lines: 29
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: nomad6-3.sybase.com 157.133.176.3
Message-ID: <347_37TGonwm$GA.202@forums.sybase.com>
References: <347_D0IQmqsm$GA.307@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25127
Article PK: 154226

Is your firewall doing any Network Address Translation?

Dave Wolf
Internet Applications Division

"Eddie Lewis" <eddie.lewis@inte.com.au> wrote in message
news:D0IQmqsm$GA.307@forums.sybase.com...
> Our client cannot create component instances within jag (error return of
50)
> when we try connecting the application to through a firewall running on
> linux (6.1).
>
> The Jag manager network monitor shows the iiop sessions increase by 1 and
> after about 10 seconds, the client shows the createinstance error.
>
> The connection works fine when we connect internally.
> The firewall passes on the request ok.
>
> We are using Jag3.5 Enterprise.
>
> Does anyone know of any seetings we require/ things we can try (ie. log
> files to check and what to look for).
>
> Thanks
> Eddie Lewis
>
>


Eddie Lewis Posted on 2000-04-03 01:41:33.0Z
Newsgroups: sybase.public.easerver
From: "Eddie Lewis" <eddie.lewis@inte.com.au>
Subject: Re: Connecting to Jaguar through a firewall
Date: Mon, 3 Apr 2000 11:41:33 +1000
Lines: 121
Organization: Intecom Systems
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
NNTP-Posting-Host: mail.intecom.com.au 210.9.112.10
Message-ID: <347_FP0ZO3Qn$GA.202@forums.sybase.com>
References: <347_D0IQmqsm$GA.307@forums.sybase.com> <347_37TGonwm$GA.202@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24970
Article PK: 155321

Yes. The firewall isolates our internal LAN from the internet using
IPChains for port opening and ip masquerade for address translation. We are
redirecting packets from the internet address to an internal JAG server with
ipmasqadm.

Below is the output from tcpdump when attempting to connect from the
internet.

tcpdump: listening on eth0
14:32:58.599425 > FIREWALL.inte.com.au > CLIENT IP Address: icmp: echo
request
14:32:58.599968 B arp who-has FIREWALL.inte.com.au tell CLIENT IP Address
14:32:58.599990 > arp reply FIREWALL.inte.com.au (0:50:8b:2e:c:6b) is-at
0:50:8b:2e:c:6b (0:10:5a:98:12:66)
14:32:58.600281 < CLIENT IP Address > FIREWALL.inte.com.au: icmp: echo reply
14:32:59.591772 > FIREWALL.inte.com.au > CLIENT IP Address: icmp: echo
request
14:32:59.592210 < CLIENT IP Address > FIREWALL.inte.com.au: icmp: echo reply
14:33:00.593065 > FIREWALL.inte.com.au > CLIENT IP Address: icmp: echo
request
14:33:00.593491 < CLIENT IP Address > FIREWALL.inte.com.au: icmp: echo reply
14:33:01.594370 > FIREWALL.inte.com.au > CLIENT IP Address: icmp: echo
request
14:33:01.594786 < CLIENT IP Address > FIREWALL.inte.com.au: icmp: echo reply
14:33:04.590979 > arp who-has CLIENT IP Address tell FIREWALL.inte.com.au
(0:50:8b:2e:c:6b)
14:33:04.591308 < arp reply CLIENT IP Address is-at 0:10:5a:98:12:66
(0:50:8b:2e:c:6b)
14:35:24.366325 B arp who-has FIREWALL.inte.com.au tell CLIENT IP Address
14:35:24.366350 > arp reply FIREWALL.inte.com.au (0:50:8b:2e:c:6b) is-at
0:50:8b:2e:c:6b (0:10:5a:98:12:66)
14:35:24.366653 < CLIENT IP Address.1079 > FIREWALL.inte.com.au.9000: R
73228:73228(0) win 0 (DF)
14:35:26.996243 B arp who-has ROUTER tell CLIENT IP Address
14:35:28.010024 < CLIENT IP Address.1081 > FIREWALL.inte.com.au.9000: S
73144:73144(0) win 8192 <mss 1460> (DF)
14:35:28.010317 > FIREWALL.inte.com.au.9000 > CLIENT IP Address.1081: S
970608532:970608532(0) ack 73145 win 8760 <mss 1460> (DF)
14:35:28.010781 < CLIENT IP Address.1081 > FIREWALL.inte.com.au.9000: .
73145:73145(0) ack 970608533 win 8760 (DF)
14:35:28.012146 < CLIENT IP Address.1081 > FIREWALL.inte.com.au.9000: P
73145:73167(22) ack 970608533 win 8760 (DF)
14:35:28.012583 > FIREWALL.inte.com.au.9000 > CLIENT IP Address.1081: P
970608533:970608553(20) ack 73167 win 8738 (DF)
14:35:28.013725 < CLIENT IP Address.1081 > FIREWALL.inte.com.au.9000: P
73167:73236(69) ack 970608553 win 8740 (DF)
14:35:28.014485 > FIREWALL.inte.com.au.9000 > CLIENT IP Address.1081: P
970608553:970608698(145) ack 73236 win 8669 (DF)
14:35:28.055516 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:28.139275 < CLIENT IP Address.1081 > FIREWALL.inte.com.au.9000: .
73236:73236(0) ack 970608698 win 8595 (DF)
14:35:28.800152 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:29.551116 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:32.312897 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:33.000984 > arp who-has CLIENT IP Address tell FIREWALL.inte.com.au
(0:50:8b:2e:c:6b)
14:35:33.001331 < arp reply CLIENT IP Address is-at 0:10:5a:98:12:66
(0:50:8b:2e:c:6b)
14:35:33.055652 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:33.806631 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:36.568410 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:37.311169 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:38.062150 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:40.824032 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:41.566689 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:42.317651 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:45.079849 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:45.822210 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:35:46.573176 B CLIENT IP Address.netbios-ns > BROADCAST
ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST

Regards
Eddie Lewis

Dave Wolf [Sybase] wrote in message <37TGonwm$GA.202@forums.sybase.com>...
>Is your firewall doing any Network Address Translation?
>
>Dave Wolf
>Internet Applications Division
>
>"Eddie Lewis" <eddie.lewis@inte.com.au> wrote in message
>news:D0IQmqsm$GA.307@forums.sybase.com...
>> Our client cannot create component instances within jag (error return of
>50)
>> when we try connecting the application to through a firewall running on
>> linux (6.1).
>>
>> The Jag manager network monitor shows the iiop sessions increase by 1 and
>> after about 10 seconds, the client shows the createinstance error.
>>
>> The connection works fine when we connect internally.
>> The firewall passes on the request ok.
>>
>> We are using Jag3.5 Enterprise.
>>
>> Does anyone know of any seetings we require/ things we can try (ie. log
>> files to check and what to look for).
>>
>> Thanks
>> Eddie Lewis
>>
>>
>
>


Dave Wolf [Sybase] Posted on 2000-04-03 12:57:30.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Connecting to Jaguar through a firewall
Date: Mon, 3 Apr 2000 08:57:30 -0400
Lines: 144
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: nomad6-18.sybase.com 157.133.176.18
Message-ID: <347_hI3fYzWn$GA.202@forums.sybase.com>
References: <347_D0IQmqsm$GA.307@forums.sybase.com> <347_37TGonwm$GA.202@forums.sybase.com> <347_FP0ZO3Qn$GA.202@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24958
Article PK: 154116

There is an ORB property you must set when your firewall is doing NTA. The
property is

com.sybase.CORBA.ProxyHost

You must set its value equal to the IP name as it is knonw outside the
firewall. In otherwords the same IP name used to connect from the client.

Dave Wolf
Internet Applications Division

"Eddie Lewis" <eddie.lewis@inte.com.au> wrote in message
news:FP0ZO3Qn$GA.202@forums.sybase.com...
> Yes. The firewall isolates our internal LAN from the internet using
> IPChains for port opening and ip masquerade for address translation. We
are
> redirecting packets from the internet address to an internal JAG server
with
> ipmasqadm.
>
> Below is the output from tcpdump when attempting to connect from the
> internet.
>
> tcpdump: listening on eth0
> 14:32:58.599425 > FIREWALL.inte.com.au > CLIENT IP Address: icmp: echo
> request
> 14:32:58.599968 B arp who-has FIREWALL.inte.com.au tell CLIENT IP Address
> 14:32:58.599990 > arp reply FIREWALL.inte.com.au (0:50:8b:2e:c:6b) is-at
> 0:50:8b:2e:c:6b (0:10:5a:98:12:66)
> 14:32:58.600281 < CLIENT IP Address > FIREWALL.inte.com.au: icmp: echo
reply
> 14:32:59.591772 > FIREWALL.inte.com.au > CLIENT IP Address: icmp: echo
> request
> 14:32:59.592210 < CLIENT IP Address > FIREWALL.inte.com.au: icmp: echo
reply
> 14:33:00.593065 > FIREWALL.inte.com.au > CLIENT IP Address: icmp: echo
> request
> 14:33:00.593491 < CLIENT IP Address > FIREWALL.inte.com.au: icmp: echo
reply
> 14:33:01.594370 > FIREWALL.inte.com.au > CLIENT IP Address: icmp: echo
> request
> 14:33:01.594786 < CLIENT IP Address > FIREWALL.inte.com.au: icmp: echo
reply
> 14:33:04.590979 > arp who-has CLIENT IP Address tell FIREWALL.inte.com.au
> (0:50:8b:2e:c:6b)
> 14:33:04.591308 < arp reply CLIENT IP Address is-at 0:10:5a:98:12:66
> (0:50:8b:2e:c:6b)
> 14:35:24.366325 B arp who-has FIREWALL.inte.com.au tell CLIENT IP Address
> 14:35:24.366350 > arp reply FIREWALL.inte.com.au (0:50:8b:2e:c:6b) is-at
> 0:50:8b:2e:c:6b (0:10:5a:98:12:66)
> 14:35:24.366653 < CLIENT IP Address.1079 > FIREWALL.inte.com.au.9000: R
> 73228:73228(0) win 0 (DF)
> 14:35:26.996243 B arp who-has ROUTER tell CLIENT IP Address
> 14:35:28.010024 < CLIENT IP Address.1081 > FIREWALL.inte.com.au.9000: S
> 73144:73144(0) win 8192 <mss 1460> (DF)
> 14:35:28.010317 > FIREWALL.inte.com.au.9000 > CLIENT IP Address.1081: S
> 970608532:970608532(0) ack 73145 win 8760 <mss 1460> (DF)
> 14:35:28.010781 < CLIENT IP Address.1081 > FIREWALL.inte.com.au.9000: .
> 73145:73145(0) ack 970608533 win 8760 (DF)
> 14:35:28.012146 < CLIENT IP Address.1081 > FIREWALL.inte.com.au.9000: P
> 73145:73167(22) ack 970608533 win 8760 (DF)
> 14:35:28.012583 > FIREWALL.inte.com.au.9000 > CLIENT IP Address.1081: P
> 970608533:970608553(20) ack 73167 win 8738 (DF)
> 14:35:28.013725 < CLIENT IP Address.1081 > FIREWALL.inte.com.au.9000: P
> 73167:73236(69) ack 970608553 win 8740 (DF)
> 14:35:28.014485 > FIREWALL.inte.com.au.9000 > CLIENT IP Address.1081: P
> 970608553:970608698(145) ack 73236 win 8669 (DF)
> 14:35:28.055516 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:28.139275 < CLIENT IP Address.1081 > FIREWALL.inte.com.au.9000: .
> 73236:73236(0) ack 970608698 win 8595 (DF)
> 14:35:28.800152 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:29.551116 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:32.312897 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:33.000984 > arp who-has CLIENT IP Address tell FIREWALL.inte.com.au
> (0:50:8b:2e:c:6b)
> 14:35:33.001331 < arp reply CLIENT IP Address is-at 0:10:5a:98:12:66
> (0:50:8b:2e:c:6b)
> 14:35:33.055652 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:33.806631 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:36.568410 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:37.311169 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:38.062150 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:40.824032 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:41.566689 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:42.317651 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:45.079849 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:45.822210 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> 14:35:46.573176 B CLIENT IP Address.netbios-ns > BROADCAST
> ADDRESS.netbios-ns:NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
>
> Regards
> Eddie Lewis
>
>
> Dave Wolf [Sybase] wrote in message <37TGonwm$GA.202@forums.sybase.com>...
> >Is your firewall doing any Network Address Translation?
> >
> >Dave Wolf
> >Internet Applications Division
> >
> >"Eddie Lewis" <eddie.lewis@inte.com.au> wrote in message
> >news:D0IQmqsm$GA.307@forums.sybase.com...
> >> Our client cannot create component instances within jag (error return
of
> >50)
> >> when we try connecting the application to through a firewall running on
> >> linux (6.1).
> >>
> >> The Jag manager network monitor shows the iiop sessions increase by 1
and
> >> after about 10 seconds, the client shows the createinstance error.
> >>
> >> The connection works fine when we connect internally.
> >> The firewall passes on the request ok.
> >>
> >> We are using Jag3.5 Enterprise.
> >>
> >> Does anyone know of any seetings we require/ things we can try (ie. log
> >> files to check and what to look for).
> >>
> >> Thanks
> >> Eddie Lewis
> >>
> >>
> >
> >
>
>


Eddie Lewis Posted on 2000-04-04 06:12:28.0Z
Newsgroups: sybase.public.easerver
From: "Eddie Lewis" <eddie.lewis@inte.com.au>
Subject: Re: Connecting to Jaguar through a firewall
Date: Tue, 4 Apr 2000 16:12:28 +1000
Lines: 28
Organization: Intecom Systems
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
NNTP-Posting-Host: mail.intecom.com.au 210.9.112.10
Message-ID: <347_LpU8xyfn$GA.316@forums.sybase.com>
References: <347_D0IQmqsm$GA.307@forums.sybase.com> <347_37TGonwm$GA.202@forums.sybase.com> <347_FP0ZO3Qn$GA.202@forums.sybase.com> <347_hI3fYzWn$GA.202@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24853
Article PK: 155293

Dave
We have written the application using PB only (client and server objects) so
where should we set this property ? ie. which .props file or is this within
the connection object on the client ?
I have searched the html documentation and the only references to the
proxyhost property occur with java.

P.S
thanks for your help so far.

Regards Eddie Lewis

Dave Wolf [Sybase] wrote in message ...
>There is an ORB property you must set when your firewall is doing NTA. The
>property is
>
>com.sybase.CORBA.ProxyHost
>
>You must set its value equal to the IP name as it is knonw outside the
>firewall. In otherwords the same IP name used to connect from the client.
>
>Dave Wolf
>Internet Applications Division
>


Jim O'Neil [Sybase] Posted on 2000-04-04 19:11:43.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 04 Apr 2000 15:11:43 -0400
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Connecting to Jaguar through a firewall
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 24
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38EA3E6E.B02743DE@sybase.com>
References: <347_D0IQmqsm$GA.307@forums.sybase.com> <347_37TGonwm$GA.202@forums.sybase.com> <347_FP0ZO3Qn$GA.202@forums.sybase.com> <347_hI3fYzWn$GA.202@forums.sybase.com> <347_LpU8xyfn$GA.316@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24795
Article PK: 154008

set <connection>.options = "ORBProxyHost='11.23.45.67'"


--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc

Eddie Lewis wrote:

> Dave
> We have written the application using PB only (client and server objects) so
> where should we set this property ? ie. which .props file or is this within
> the connection object on the client ?
> I have searched the html documentation and the only references to the
> proxyhost property occur with java.
>
> P.S
> thanks for your help so far.
>
> Regards Eddie Lewis
>
> Dave Wolf [Sybase] wrote in message ...
> >There is an ORB property you must set when your firewall is doing NTA. The
> >property is
> >
> >com.sybase.CORBA.ProxyHost
> >
> >You must set its value equal to the IP name as it is knonw outside the
> >firewall. In otherwords the same IP name used to connect from the client.
> >
> >Dave Wolf
> >Internet Applications Division
> >


Eddie Lewis Posted on 2000-04-05 02:00:55.0Z
Newsgroups: sybase.public.easerver
From: "Eddie Lewis" <eddie.lewis@inte.com.au>
Subject: Re: Connecting to Jaguar through a firewall
Date: Wed, 5 Apr 2000 12:00:55 +1000
Lines: 95
Organization: Intecom Systems
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
NNTP-Posting-Host: mail.intecom.com.au 210.9.112.10
Message-ID: <347_MT5lSLqn$GA.34@forums.sybase.com>
References: <347_D0IQmqsm$GA.307@forums.sybase.com> <347_37TGonwm$GA.202@forums.sybase.com> <347_FP0ZO3Qn$GA.202@forums.sybase.com> <347_hI3fYzWn$GA.202@forums.sybase.com> <347_LpU8xyfn$GA.316@forums.sybase.com> <347_38EA3E6E.B02743DE@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24756
Article PK: 153970

Thanks for the reply Jim.
This worked but we now have trouble resolving the machine address from the
client
I have set up my connectionObj.Option as per the ini file settings shown
below

[Jaguar]
UserID=jagadmin
PassWord=
Server=iiop://FIREWALL:9000
;Port = 9000
Application = capsServer
Option=ORBLogFile='c:\temp\orb.log',ORBLogIIOP=true,ORBProxyHost='FIREWALL:9
000'


The orb.log file generated gives
ORB_init option = 'LogIIOP' value = 'true'
ORB_init option = 'ProxyHost' value = 'FIREWALL:9000'
Warning: protocol "iiops" not supported.
----------------------------------------------------------------------------
---
IIOP putMessage Hexadecimal [padding] (interpretation) ISO 8859-1
encoding
--------------- - ---------------------------------------- -----------------
---
putOctet < 47 (71) G
putOctet < 49 (73) I
putOctet < 4F (79) O
putOctet < 50 (80) P
putOctet < 01 (1) .
putOctet < 01 (1) .
putBoolean < 01 (TRUE) .
putOctet < 00 (0) .
putULong < 00000000 (0) ....
putMessage | GIOP version = 1.1

| flags = 1 ('<' little endian)

| message type = 0 (Request)
putRequest | service context length:
putULong < 00000000 (0) ....
putRequest | request id:
putULong < 00000000 (0) ....
putRequest | response expected:
putBoolean < 01 (TRUE) .
putRequest | object key:
putULong < 00000002000000 [3] (2) .......
putOctets < 4D00 M.
putRequest | operation:
putULong < 00000E000000 [2] (14) ......
putString < 63726561746553657373696F6E00 createSession.
putRequest | requesting principal:
putULong < 000000000000 [2] (0) ......
putRequest | request body:
putULong < 01000000 (1) ....
putString < 00 .
putULong < 00000001000000 [3] (1) .......
putString < 00 .
endMessage | message size = 57 (after 12 byte header)
NLWNSCK-Library Error 4: new_JagIIOPSocket: ipd_connect failed
new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed
NLWNSCK-Library Error 4: new_JagIIOPSocket: ipd_connect failed
new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed
NLWNSCK-Library Error 4: new_JagIIOPSocket: ipd_connect failed
new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed
NLWNSCK-Library Error 4: new_JagIIOPSocket: ipd_connect failed
new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed
NLWNSCK-Library Error 4: new_JagIIOPSocket: ipd_connect failed
new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed
FIREWALL:9000 (proxy FIREWALL:9000) - Connection refused

The server gives an error after approx 10 seconds which coincides with the 5
attempts made above (which i believe is the standard).
The FIREWALL address maps correctly to the jag server listening on port 9000
In the ini file, if we remove the 9000 from the server setting, the
application returns immediately and the orb.log shows

ORB_init option = 'LogIIOP' value = 'true'
ORB_init option = 'ProxyHost' value = FIREWALL:9000'
Warning: protocol "iiops" not supported.
new_JagObjectRef: Bad URL - iiop://FIREWALL

Any help would be excellent...


Jim O'Neil [Sybase] wrote in message <38EA3E6E.B02743DE@sybase.com>...
>set <connection>.options = "ORBProxyHost='11.23.45.67'"
>
>
>--
>Jim O'Neil
>Senior Technical Support Engineer
>Sybase, Inc


Jim O'Neil [Sybase] Posted on 2000-04-05 13:40:39.0Z
Newsgroups: sybase.public.easerver
Date: Wed, 05 Apr 2000 09:40:39 -0400
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Connecting to Jaguar through a firewall
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 115
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38EB4257.2A5452E9@sybase.com>
References: <347_D0IQmqsm$GA.307@forums.sybase.com> <347_37TGonwm$GA.202@forums.sybase.com> <347_FP0ZO3Qn$GA.202@forums.sybase.com> <347_hI3fYzWn$GA.202@forums.sybase.com> <347_LpU8xyfn$GA.316@forums.sybase.com> <347_38EA3E6E.B02743DE@sybase.com> <347_MT5lSLqn$GA.34@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:24722
Article PK: 153935

Don't put the port number in ORBProxyHost - note the error, with the port number
specified twice, in the log:

new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed

If you need to change ports too, use the ORBProxyPort tag within the options
string.

--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc

Eddie Lewis wrote:

> Thanks for the reply Jim.
> This worked but we now have trouble resolving the machine address from the
> client
> I have set up my connectionObj.Option as per the ini file settings shown
> below
>
> [Jaguar]
> UserID=jagadmin
> PassWord=
> Server=iiop://FIREWALL:9000
> ;Port = 9000
> Application = capsServer
> Option=ORBLogFile='c:\temp\orb.log',ORBLogIIOP=true,ORBProxyHost='FIREWALL:9
> 000'
>
> The orb.log file generated gives
> ORB_init option = 'LogIIOP' value = 'true'
> ORB_init option = 'ProxyHost' value = 'FIREWALL:9000'
> Warning: protocol "iiops" not supported.
> ----------------------------------------------------------------------------
> ---
> IIOP putMessage Hexadecimal [padding] (interpretation) ISO 8859-1
> encoding
> --------------- - ---------------------------------------- -----------------
> ---
> putOctet < 47 (71) G
> putOctet < 49 (73) I
> putOctet < 4F (79) O
> putOctet < 50 (80) P
> putOctet < 01 (1) .
> putOctet < 01 (1) .
> putBoolean < 01 (TRUE) .
> putOctet < 00 (0) .
> putULong < 00000000 (0) ....
> putMessage | GIOP version = 1.1
> | flags = 1 ('<' little endian)
> | message type = 0 (Request)
> putRequest | service context length:
> putULong < 00000000 (0) ....
> putRequest | request id:
> putULong < 00000000 (0) ....
> putRequest | response expected:
> putBoolean < 01 (TRUE) .
> putRequest | object key:
> putULong < 00000002000000 [3] (2) .......
> putOctets < 4D00 M.
> putRequest | operation:
> putULong < 00000E000000 [2] (14) ......
> putString < 63726561746553657373696F6E00 createSession.
> putRequest | requesting principal:
> putULong < 000000000000 [2] (0) ......
> putRequest | request body:
> putULong < 01000000 (1) ....
> putString < 00 .
> putULong < 00000001000000 [3] (1) .......
> putString < 00 .
> endMessage | message size = 57 (after 12 byte header)
> NLWNSCK-Library Error 4: new_JagIIOPSocket: ipd_connect failed
> new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed
> NLWNSCK-Library Error 4: new_JagIIOPSocket: ipd_connect failed
> new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed
> NLWNSCK-Library Error 4: new_JagIIOPSocket: ipd_connect failed
> new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed
> NLWNSCK-Library Error 4: new_JagIIOPSocket: ipd_connect failed
> new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed
> NLWNSCK-Library Error 4: new_JagIIOPSocket: ipd_connect failed
> new_JagIIOPSocket: ipd_connect(FIREWALL:9000:9000) failed
> FIREWALL:9000 (proxy FIREWALL:9000) - Connection refused
>
> The server gives an error after approx 10 seconds which coincides with the 5
> attempts made above (which i believe is the standard).
> The FIREWALL address maps correctly to the jag server listening on port 9000
> In the ini file, if we remove the 9000 from the server setting, the
> application returns immediately and the orb.log shows
>
> ORB_init option = 'LogIIOP' value = 'true'
> ORB_init option = 'ProxyHost' value = FIREWALL:9000'
> Warning: protocol "iiops" not supported.
> new_JagObjectRef: Bad URL - iiop://FIREWALL
>
> Any help would be excellent...
>
> Jim O'Neil [Sybase] wrote in message <38EA3E6E.B02743DE@sybase.com>...
> >set <connection>.options = "ORBProxyHost='11.23.45.67'"
> >
> >
> >--
> >Jim O'Neil
> >Senior Technical Support Engineer
> >Sybase, Inc