|
midrange.com
You lost me on that one... not familiar with what you're suggesting here...
"DeLong, Eric"
<EDeLong@Sallybea
uty.com> To
Sent by: "'Midrange Systems Technical
midrange-l-bounce Discussion'"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
10/12/2005 04:26 Subject
PM RE: Netserver browsing across
firewall zones
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Chad, perhaps you could try this as a workaround....
Create the entry in QNTC by IP address if you know it.
MKDIR '/QNTC/10.11.111.111'
Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of
ChadB@xxxxxxxxxxxxxxxxxxxx
Sent: Wednesday, October 12, 2005 1:10 PM
To: Midrange Systems Technical Discussion
Subject: Netserver browsing across firewall zones
We have 3 iSeries boxes that do a limited amount of Netserver file serving
to a few users. The users are all on the 'inside' firewall zone as well as
2 of the 3 iSeries boxes. The users can pull up the domain when browsing
down through the network and see those 2 boxes just fine. The 3rd box is
in our 'DMZ' firewall zone and doesn't show up when browsing the domain (It
is also a member of the same domain).
The netserver is set to announce it's name every 5 minutes (via Netbios
broadcasts I believe). I suspect this is just a matter of the broadcasts
not getting across the firewall into the inside zone because the correct
ports aren't open. I've tried opening up the inside zone to ports 137,
138, 139 from that particular iSeries in the DMZ with no luck so far. Any
ideas? Any example of the PIX commands follows:
access-list inside permit udp any host 172.#.#.# eq netbios-dgm
access-list inside permit udp any host 172.#.#.# eq netbios-ns
access-list inside permit udp any host 172.#.#.# eq 139
____________________________________________________________________________
_
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
____________________________________________________________________________
_
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT0002F12A
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs. For
more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
