home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.ms-windows.apps:5232 comp.protocols.tcp-ip.ibmpc:6493
- Newsgroups: comp.os.ms-windows.apps,comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!microsoft!hexnut!jallard
- From: jallard@microsoft.com (James 'J' Allard)
- Subject: Re: TCP/IP and Windows for Workgroups
- Message-ID: <1992Nov23.193419.7780@microsoft.com>
- Date: 23 Nov 92 19:34:19 GMT
- Organization: Microsoft Corporation
- References: <1992Nov17.162001.14830@devildog.att.com> <BxxJ1G.4vv@law7.DaytonOH.NCR.COM> <7nnq0_k@lynx.unm.edu>
- Lines: 30
-
- In article <7nnq0_k@lynx.unm.edu> tkeitt@algodones.unm.edu writes:
- >
- >I think I started this thread (thanks to those who have
- >responded). Let me restate the question. I use windows on my
- >PC. I have an ethernet link to our Suns. I can telnet, ftp, etc
- >using QVT/NET. The question is WHAT GOOD IS WfWG OUT OF THE BOX
- >WITHOUT BUYING ANY OTHER SOFTWARE FOR TCP/IP CONNECTIONS? Does
- >it include TCP/IP utilities a la QVT/NET? Can I mount remote
- >drives? Transparently print to remote printers? Or am I better
- >off pocketing the upgrade cost and sticking with W3.1 and
- >QVT/NET?
-
- The answer to this question depends entirely on your needs. It appears
- that what you're after is a package which will allow your Windows
- workstation to communicate with your Suns, and other UNIX-hosts. Windows
- for Workgroups was not designed to facilitate this. Windows for Workgroups
- was designed to allow Windows workstations to easily share data between
- members of workgroups (hence the name). Windows for Workgroups offers
- peer file and print sharing, DDE (dynamic data exchange) over the net,
- e-mail and scheduling facilities, etc.. Although it does not prevent
- you from making connections to foreign hosts, it does not offer TCP/IP
- "in the box", nor does it offer TCP/IP utilities like FTP, r*, TELNET,
- etc... Microsoft will be making TCP/IP available for Windows for
- Workgroups customers, but I'm not sure that this is what you're
- after. It sounds like you'd be better off looking at other vendors
- PC-based TCP/IP solutions.
-
- J. Allard
- Microsoft Corp.
- (jallard@microsoft.com)
-