| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 523.1 | Some answers... | CSC32::R_BUCK | Authenticated and assimilated | Mon Feb 24 1997 15:40 | 47 |
| Not sure I can answer all of your questions but I will make a stab at
the areas I do know about.
File and Print shares are basic services offered with Windows for
Workgroups, Windows 95 and Windows NT. They were originally limited to
local network segments since NETBUEI, (NETBIOS), is not routable.
Current implementations for W95 and WNT use IP and encapsulation to
work over extended LANS and WANS. WFW has a free IP stack available
for the Microsoft site that also provides the same functionality.
Dial-Up networking and/or RAS are built into Windows 95 and Windows NT.
Third party solutions like Netrider are needed for Windows 3.x and
WFW. In all cases, running TCP/IP over the Dial-Up link, (typically a
PPP connection), allows the same services that would be available over
a local network.
>What they want to do is simple:
>1. WFW client be able to use file/print services on their network.
As far as I can tell, this would be available with standard Windows
software. Simply need to configure networking and specify that the
systems can share files and/or printers.
>2. Windows NT Workstation be able to use file/print services on the
>network.
Again, this capability exists with standard software. Need to run
TCP/IP if systems are on different segments of the network.
>3. Pathworks is not an option because of cost.
Pathworks for OpenVMS, or other non-PC platforms, would only be usefull
if you wanted to share files and/or printers that available on the
specific node.
Netrider client and other software packages that add dial-up
capabilities and TCP/IP, have been largely replaced by the built in
software on Windows NT and Windows 95. As I recall Netrider Client V1
was only 'supported' on Windows 3.x, not WFW and certainly not W95.
Actually, based on your questions and limited description of the
customer needs, I do not even see a purpose for Netrider client
software in this environment. Going to guess that I am missing some
information. Freely admit that I am not an expert on Netrider client
and Netrider remote office.
Randall Buck
MCS - Network Support
|
| 523.2 | NO callback !! | NETRIX::"[email protected]" | NSIS Austria | Mon Feb 24 1997 17:55 | 15 |
| Hi there,
Unfortunately the world is�nt that bright and the Win95 Sky not that blue.
The RAS clients WIN95 and NT use the MS "enhancements" for CBCP and therefor
a callback/dialback from a Netrider to WIN95/NT is NOT possible.
I hope someone will correct me and provides the dates of availability for a
new DNAS version which eliminates this annoying problem. Or maybe just a
third party client running on Win95/NT (Stampede ROGWIN95 ???)
not happy ;-(
Robert
NSIS Austria
[Posted by WWW Notes gateway]
|
| 523.3 | | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Tue Feb 25 1997 10:26 | 14 |
| RE: .2
> I hope someone will correct me and provides the dates of availability for a
> new DNAS version which eliminates this annoying problem. Or maybe just a
> third party client running on Win95/NT (Stampede ROGWIN95 ???)
You are correct. The Version 2.2 of DNAS will support Microsoft's Call Back
Control Protocol (CBCP). Contact the Product Manager for availability. If
you need a hint, the Product manager is listed in Note 4.*.
Regards,
Dave
|
| 523.4 | | LAVC::CAHILL | Jim Cahill | Tue Feb 25 1997 10:30 | 10 |
| As Dave said, DNAS V2.2 will contain CBCP. This version is about to go out
to field test. If you or your customer's site use Win95 clients and make
frequent use of callback, please consider becoming a field test site. Send
mail to the Product Manager and ask for a copy of the field test questionnaire.
> not happy ;-(
Hopefully you will be when you see what we've been up to lately!
Jim
|
| 523.5 | Will RAS work with V2.2 | KAOFS::HXMP01::p_savoie | mcs network support | Wed Feb 26 1997 09:40 | 9 |
| Hi,
I appreciate the discussion, but callback is not one of my customer's
requirement. They need to use a simple, reliable and functional client
software for WFW and NT workstation. Will V2.2 allow them to use Microsoft
RAS software from clients dialing in ?
Thanks,
Paul
MCS Network Support,Canada
|
| 523.6 | Microsoft has it... | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Wed Feb 26 1997 11:03 | 21 |
| > They need to use a simple, reliable and functional client software for WFW
> and NT workstation.
Windows NT workstation has it, and it works with DNAS that's out there today
(and has been for a long time). Same for Windows 95. For WFW, you want to
get the free IP stack from the Microsoft web site. WFW out of the box uses
NetBEUI over the dial-up link, a very passe' concept. We strongly recommend
using TCP/Ip over the dial-up link.
> Will V2.2 allow them to use Microsoft RAS software from clients dialing in ?
The improvements scheduled for V2.2 include: DHCP support, WINS auto discover
support, CBCP support, LPD printing support and enhanced AUTOLINK support.
This makes using RAS easire, but as I said above, it works today, as long as
you're using NetBIOS over TCP/IP (RFC 1001) and not NetBIOS Frames over PPP
(NetBEUI).
Regards,
Dave
|