Well, I was afraid that when I published that information it might not be
completely accurate since I was not the author and I don't work on the web
client.
It would appear that there is more to running one across a firewall than
the developer who wrote it was aware. The only way I know to get help with
this is to open a problem with Support and see if they can assist you. If
I had to guess, I would say that there are other ports which the background
processes for the web client are trying to use, and that your firewall
would have o be opened for them as well, but I don't know how to tell which
those are. It may be that in fact the original append was mistaken, and
that you cannot successfully run across a firewall with 6.0.1 and will need
to wait for a newer release, or negotiate with Support for some kind of
early relief if that is possible.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
Vynita <vynita@metroweb.co.za> on 10/12/2000 03:04:57 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: nv-l@tkg.com
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] NetviewNT WEB client 6.0.1 -Firewall problems
Hi all
I am trying to get the web client to work through a firewall but to no
avail.
As per James Shanks notes about pegging down the port number, I loaded the
6.0.1 software and made the changes so that the map would open on port 80.
On the client I call http://serverip:8080/NetviewApplet.html, I receive the
login prompt. After logging in I get the white screen with File .. etc. If
I click on event browser the event browser appears but if I go file->Open
the netview client just hangs. On the sniffer I see an HTTP error 404 and
nothing more happens
I have also tried using nvwc serverip 8080 and I still get no map
appearing.
With a network sniffer (whilst using nvwc) I can see ports 80 and 8080 but
I can also see that after the "Openmap" which is initiated by the client,
with the destination port 80 & s4351, I see HTML data being received but
then the server initiates another session dest port 4352(Random port which
increments by one from the previous session) & s 4666, which does not get
acknowledged because it is blocked. The client continues again on dest 80 &
s 4351 but the map is never received.
I am using the standard jettyserver settings which specify 8080 for
connectivity and mib browser 8892.
If I physically change segments so that the both server and client are on
the same segment it works and I get the default map.
Thanks in advance
Vynita
|