Text 50, 101 rader
Skriven 2005-02-12 10:24:18 av Mike Luther (1:117/3001.0)
Ärende: More on Sprint DSL?
===========================
Well, I got totally told wrong on the Sprint ADSL site setup once I got down
there.  Sigh.

They neglected to tell me that they already *HAD* a connection to Sprint up and
running as ADSL via a LinkSys router that was also cascaded into a Cisco switch
of some kind!  A total of six win boxes for totally other institutions caked
onto one ADSL modem is now in use.

What they THOUGHT they were going to do was put their new broadband ZyXel 324
router behind all this and isolate the OS/2 operation totally from everything
else against the same ADSL line!  No I don't visualize any way to ever do that.
 But maybe it could be done?  The ZyXel sure doesn't think so however I know to
set that up.

Help?

OK, if they really wanna be on that same line (?), in theory as I see this, all
they really need to do is to use the OS/2 box with a LAN cord connection just
with DHCP and let it get just another 192.168.1.??? address given to the OS/2
box.  Then whatever misery they get into for NAT and firewall and so on, is
their business with whomever has cabled up their setup.  As in some places, the
whole building is simply cabled up with wires and, other than the telco panel
.. there are *NO* id tags on hundreds of cable wired .. no log books .. no
nothing!  And the building guru isn't available for huddle when I'm there.

Before I found this out, the new ZyXel 324 works as intended.  I can COMM port
it, look at WAN and see traffic .. WAN lite winking and all that.  But the OS/2
box never got a connect to Sprint.  Of course not! So I know that at least the
line given me through this multi-story building goes somewhere and is live!

   ************

So I tried to get a bare box single line DHCP connection with LAN0 set up for
Netbios for OS/2 and TCP/IP protocols on it to simply connect to the provided
cable that goes (?) to the closet.  No connect,  So my guess is that they are
trying to stick this OS/2 box on the tail end of the Cisco switch and it isn't
passing th OS/2 DHCP request properly to the Linksys in regard to some part of
the protocol it needs.  Even though as connected to the ZyXel router it gets a
nice 192.168.1.33 private DHCP assignment just fine from it.  Yes, I've read
the Usegroup posting on having to enable additional options in the PROTOCOL.INI
for the box in some cases for some devices.  But I'm not comfortable with doing
that in the field yet from memory and wasn't prepared with even printed notes
for this when I went to do a brand new single connect to a brand new Sprint
ADSL modem!
                                         
Since Peter here is Cisco oriented, maybe he can tell me what is missing from
the OS/2 DHCP request protocol to get to the DNS service on the Linksys .. or
even maybe it goes to Sprint?  I dunno as nobody was there that could tell me
where any of the cables go and what is intended!

  *************

Next problem, this on in OS/2.  Isolating the local network from the WAN
connection for this one box.

As I understand this, a proper way to isolate the entire OS/2 Peer operation
for all the rest of the perfectly functional boxes in the OS/2 network is done
through the use of two LAN NIC cards in the box.  One NIC should be connected
to the WAN .. upstream to the router.  The other one of the NIC cards should be
connected to the local PEER network. I've not had to do this before.  But this
means one NIC is LAN0 and the other NIC is LAN1.  OK .. I've got two in the box
in PCI slots and they test and are for sure on different IRQ's.

I can use MTPN setup and get the second NIC identified and assigned to
protocols.  And .. as I understood this, only one of the NIC's may be set up
with DHCP and not fixed addressing.  So my assumption is that whatever of the
two NIC's I use for the DCHP connection to the whatever router Linksys or
ZyXel, it is the other NIC which will have to connect back to the already
present hub.

I can, with both cards, still get the DHCP address returned to the OS/2 box
from the ZyXel.  Obviously not yet from whatever is in the building.

But .. with Netbios for OS/2 and TCP/IP as protocols enabled on both the DHCP
NIC and the new one (which has a fixed address that shows as 192.168.1.9
somehow, I cannot see the existing LAN!  Neither on the NIC which has the DCHP
setting, nor the new one.

When I go to log on to the LAN .. I get a message 'DOMAIN already in use' and
as far as I can see .. that user is not even and has never logged in to
anywhere.  It, of course as PEER .. is IBMPEERS as far as I know.

What am I doing wrong?   How do I enable this box so that the DCHP service can
exist on the one NIC and IBMPEERS with the correct connections can be made to
the local PEER LAN on the other NIC?

Or .. is there some way to use a HUB card so that the core box here could be
used with a crossover connection to the HUB in reverse to let the local PEER
LAN be on one port and the building's whatever Cisco/Linksys or whoknowze be on
another HUB port to get isolation?  I don't think so.  But my nose is sniffing
water at this point.

Help?


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)