|
Stanley, I don't have hands experience with the RAS server but know am familiar with the product. Probably easiest and cheapest solution would be to stick with TCP/IP and go with the RAS server on the host side and on the client side use Client Access configured for TCP/IP and the Win95/NT PPP dialer for your connection method. You can configure the Win95/NT PPP dialer to support NetBEUI, IPX/SPX and TCP/IP. Just turn off what you don't need. If you are at v4.xx on your Novell servers then they support TCP/IP. This is the route I'm going with on our dial-in network, minus the RAS server. I'm even going to implement this for our Internet connections and run Client Access over the Internet. Naturally we are going to put in a firewall first (Raptor Eagle) and use encryption software at the client side. Danny Mc? Danny Mc? Stanley Tang wrote: > > We have 5 token ring LANs connected via 2 IBM6611 routers. There is an > AS/400 running V3R2 on the first ring and a NT Server running 4.0 on the > third ring. We are using IPX, TCP/IP and DLC on the LANs. > > Now we want to provide remote access for users so that they can dial in from > home to access all the network resources such as AS/400, Novell servers and > NT servers. We want the NT server to act as the only point of entry. > Therefore, we do not want users to dial in the AS/400 directly. > > My questions are: > > 1. If we set up RAS on the NT server, can users dial in from > home and then access the AS/400 using Client Access for Windows 95? > > 2. If it is possible, what kind of protocol do I need at the PC > and the AS/400? Do I have to use TCP/IP? Can I use MSDLC? > > 3. If Client Access for Windows 95 cannot do the job, are there > any other products that can do the job? -- --- Danny Mc? E-mail: dcmcques@vantek.net or Click: mailto:dcmcques@vantek.net Web Page: http://www.vantek.net/pages/dcmcques/index.html -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzF0vwQAAAEEANHAlvrDaRFM5J3H/OZCdfIMWDDmJnfutn7nhd6RUJiGCey2 sCH0PBAFhonINuI/bm0ACk4gRuwoQfERuLUMeESvMjNbcnt1qrpjsPVB9GyUs8x5 kB4gTzjD5UXQOF+EnD5I9wgSsPlXeTfwLXTs4RXUdTKoYHkxhsDJ9mZy58+NAAUR tCZEYW5ueSBNY1F1ZXN0aW9uIDxkY21jcXVlc0B2YW50ZWsubmV0PokAlQMFEDF1 3jq89vGA2+K4WQEBa6gEAIxGmjwzJ0ezTPJdDKro+C55y9XVjoRWNcGSXDZHtDun /aGx16AQ98RjCOoJH48ze4keG+KsUrSa7xXaPQpbOnoAP6I6Yanq3lxSEZzkUj/V EL+C8LWDJli5dPyXXVnvyiZ4uoVpydQeL1lEzXm4xoCOMWe5pUkjc1+B3dtWb2Mw iQCVAwUQMXXYK8DJ9mZy58+NAQFWEQP/TRU0eIpW2LaHygMNeiISOcPr3YX7Gbga pdVi1oqi6ujSS5bWAE2qQG8OGpYjz25JpYBUMQgxfsaqhZ/P820CrcChqgu99ujM J0goQPr2SY5mezg9Z8rd7EVgTg0BMIVjGSTf3IAPGdH9gStzSeFDKtGEzYgn+9tx S7ZNYDwImUg= =cnWd -----END PGP PUBLIC KEY BLOCK----- * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the Midrange System Mailing List! To submit a new message, * * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * * this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. Questions * * should be directed to the list owner / operator: david@midrange.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.