1. Go to www.tactical-sw.com and get the dialout/ip (this is for your win95/NT
machines.
1. keep your in.pmd
3. on the PM, create two modem pools (one for the unix boxes (in.pmd) and one
for the Win95/Nt machines.
4. on the PM do the following for the Win95/NT pool ports:
set sX login network twoway
set sX service_device netdata 7000
reset sX
reset sX
5. on the dialout/ip programe make sure the port it is using to create a
virtual link to the PM is 7000.
6. the ports that are assigned for the unix boxes should remain they way
they are, since they are already working well for you.
NOTE: YOU CAN NOT USE THE SAME MODEMS FOR BOTH in.pmd AND dialout/ip. THAT IS
WHY I WANTED YOU TO CREATE TWO MODEM POOLS.
P.S. Cisco can not do this! the only thing you can do on a cisco is to
reverse telnet to a port and dial out charactor mode (not packet
mode (i.e. ppp))
Good luck!
---------------------------------------------------------------
> From owner-portmaster-users Wed Jul 2 14:18:23 1997
> Organization: Mitra Imaging Inc. Waterloo, Ontario. +1.519.746.2900
> Date: Wed, 2 Jul 1997 17:07:39 -0400
> From: Larry Williamson <larry@mitra.com>
> MIME-Version: 1.0
> Content-Type> : > text/plain> ; > charset=us-ascii>
> Content-Transfer-Encoding: 7bit
> To: portmaster-users@livingston.com
> Subject: Windows and Unix access to modems on PM2
> X-Mailer: VM 6.30 under Emacs 19.34.1
> Sender: owner-portmaster-users
> Reply-To: Larry Williamson <larry@mitra.com>
> Content-Length: 2157
>
>
> I want to be able to give both our Windows NT users and our Unix users
> access to the modems on our terminal server.
>
> Our Livingston PM2 does this very nicely for our Unix users now
> through the in.pmd process. Unix users get ppp, cu and uucp access
> nicely managed through /dev/ttyxx entries.
>
> Something similiar for Windows is needed (access via comx: entries).
> There is something called comt that is supposed to do this for
> Windows, but it does not install or run on NT.
>
> We have a separate router for our ISDN traffic (Ascend 400). It would
> seem to me to make a great deal of sense to merge these two functions
> into one box. Have only ISDN lines coming in. Handle analog and ISDN
> traffic. Get better utilization over all.
>
> We are quite willing to buy another terminal server/router. I had
> looked at the Ascend 1800, and although it has the WindowsNT problem
> resolved. They do it by ignoring the Unix people (cannot access the
> modems as a /dev entry). It seems to merge the ISDN and analog modem
> traffic ISDN lines. No analog modem lines appear to be needed (Unless
> I misunderstand something)
>
> Is there any other terminal server (router) that allows both WindowsNT
> and Unix users access to a modem pool as local devices? (Cisco?
> Gandalf? Bay Networks? Others?) I have had a look, but either they
> do not support what I want, or their marketing people do not mention
> these types of features in their feature sheets. I cannot tell which.
>
> We need to support ppp (os independant, built into the terminal
> server/router), cu, uucp (for unix), pcanywhere and kermit (for
> Windows). Both dial *in* and dial *out* are essential. We would like
> ISDN (ppp only, no OS specific access) and analog modem access (very
> OS specific access) in the one box.
>
> The ISDN vs. analog modem issue is one that I can live with if it
> cannot be resolved. I can continue with the Ascend 400. But the
> windows users really need access to all the modems in our modem pool.
>
> What to do!
>
> Kind regards,
> Larry
>
>
> PS. I subscribe to both the portmaster-users and ascend-users mailing
> lists. I am wondering if there are other router/terminal server lists
> that I might subscribe to?
>