Does Windows Mosaic (0.6) or Cello (alpha R3) work with PC-NFS 5.0?
Joerg MESSER
Has anyone managed to get Wmosiac (0.6) or Cello (alpha R3) working
with PC-NFS 5.0? The new PC-NFS version supports the WINSOCK interface
so I'm at a loss as to where the problem may be. Windows Trumpet
(1.0rA) appears to work fine and it also relies on WINSOCK. Mosaic
simply complains that it can't make a connection. Cello, on the
other, complains it can't make a DNS lookup of the host name although
there seems to be no way to point it at a DNS server. I assume both
problems have a similar root cause. Any tips would be welcome.
...Joerg
--
Joerg Messer |
International Institute | Email: jo...@iiasa.ac.at
for Applied System Analysis | Phone: +43 2236 71521 314
A-2361 Laxenburg, Austria | Fax: +43 2236 71313
Jon E. Mittelhauser
>
> Has anyone managed to get Wmosiac (0.6) or Cello (alpha R3) working
>with PC-NFS 5.0? The new PC-NFS version supports the WINSOCK interface
>so I'm at a loss as to where the problem may be. Windows Trumpet
>(1.0rA) appears to work fine and it also relies on WINSOCK. Mosaic
>simply complains that it can't make a connection. Cello, on the
>other, complains it can't make a DNS lookup of the host name although
>there seems to be no way to point it at a DNS server. I assume both
>problems have a similar root cause. Any tips would be welcome.
>
Cello is giving you the better hint at what is going wrong. I was informed
by one of our Alpha users that the early PC-NFS winsock didn't support
Domain Name Servers (DNS) correctly. He said that he got a patch from
PC-NFS and Mosaic now works fine. I would suggest contacting your PC-NFS
vendor. WinTrumpet probably works fine because it is only going to a
local NNTP server that you have configured. A web client (Mosaic or Cello)
needs the DNS to find arbitrary hosts...
-Jon
Thomas R.Bruce
>with PC-NFS 5.0? The new PC-NFS version supports the WINSOCK interface
>so I'm at a loss as to where the problem may be. Windows Trumpet
>(1.0rA) appears to work fine and it also relies on WINSOCK. Mosaic
>simply complains that it can't make a connection. Cello, on the
>other, complains it can't make a DNS lookup of the host name although
>there seems to be no way to point it at a DNS server. I assume both
>problems have a similar root cause. Any tips would be welcome.
You bet there's a similar root cause, and it's Sun's refusal to put DNS code
into PC-NFS. Apparently if you're running an NIS server there's a package
called wshelper which will emulate DNS with Sun's Winsock....
it's on ftp.sunet.se /pub/pc/pc-nfs/5.0/101128-01.tar.Z
I'm probably wearing out my welcome on this subject, but I completely fail
to understand how Sun can market a so-called Winsock-compliant product which
does not resolve domain names in the most commonly accepted way, and do it
with a straight face.
Regards,
Tb.
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| Thomas R. Bruce 607-255-1221 |
| Research Associate FAX: 607-255-7193 |
| Cornell Law School |
| 481 Myron Taylor Hall t...@law.mail.cornell.edu |
| Ithaca, NY 14853 |
| |
| "Language -- it's a shipwreck, it's a job." |
| --Laurie Anderson |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Geoff Arnold @ Sun BOS - R.H. coast near the top
#You bet there's a similar root cause, and it's Sun's refusal to put DNS code
#into PC-NFS. Apparently if you're running an NIS server there's a package
#called wshelper which will emulate DNS with Sun's Winsock....
#it's on ftp.sunet.se /pub/pc/pc-nfs/5.0/101128-01.tar.Z
PC-NFS, via WinSock as well as its native toolkit, supports the name
and address resolution functionality of the BSD API in the same way as
most other Sun systems: via NIS (YP) as well as hosts files. Sites
running NIS can relay requests to DNS using the "ypserv -d" mechanism.
We have already announced that the next version of PC-NFS will also
support "native" DNS, albeit with reduced functionality. (For example,
you will not longer be able to mount file systems via the "auto.vol"
map.)
PC-NFS 5.0 has always used the "wshelper.exe" component as part of its
WinSock support. In 5.0, there was a subtle bug in wshelper which caused
GetXByY lookups to fail at certain sites. We corrected the bug and
posted the fix to the net, as noted above.
#I'm probably wearing out my welcome on this subject, but I completely fail
#to understand how Sun can market a so-called Winsock-compliant product which
#does not resolve domain names in the most commonly accepted way, and do it
#with a straight face.
DNS support is not a requirement for WinSock compliance, as you will
have found in reading the spec. It is a common myth that the GetXByY()
routines are simply front-ends to DNS. While I am looking forward to
providing DNS support in PC-NFS, I regard as much more important our
(eventual) support for full-blown NIS+. [However, people who are unhappy
with our memory footprint will not welcome the arrival of an RNM for
this (necessarily) complex system.]
Geoff
--
Geoff Arnold, PC-NFS architect, Sun Select. (geoff....@East.Sun.COM)
#### "Here the ways of men part: if you wish to strive for peace ####
#### of soul and pleasure, then believe; if you wish to be a ####
#### devotee of truth, then inquire..." - Heinrich Heine ####
Joerg MESSER
>You bet there's a similar root cause, and it's Sun's refusal to put DNS code
>into PC-NFS. Apparently if you're running an NIS server there's a package
>called wshelper which will emulate DNS with Sun's Winsock....
>it's on ftp.sunet.se /pub/pc/pc-nfs/5.0/101128-01.tar.Z
>I'm probably wearing out my welcome on this subject, but I completely fail
>to understand how Sun can market a so-called Winsock-compliant product which
>does not resolve domain names in the most commonly accepted way, and do it
>with a straight face.
>Regards,
>Tb.
I got another pointer to the PCNFS 5.0 WINSOCK patch mentioned above
and it appears to do the trick. Since this is a Sun which they
claim will be included in PCNFS 5.1, I'm assuming Sun has changed
its mind concerning the DNS support. Or am I mistaken?
Julian Field
>In article <joerg.749406399@iiasa> jo...@iiasa.ac.at (Joerg MESSER) writes:
>> Has anyone managed to get Wmosiac (0.6) or Cello (alpha R3) working
>>with PC-NFS 5.0? The new PC-NFS version supports the WINSOCK interface
Yes. I run NCSA Mosaic 0.6 on PC-NFS 5.0 with no real problems (apart
from bugs in Mosaic as it is a beta version). I've got all the patches
for PC-NFS 5.0 that I've ever found, i.e.
wshelper.exe - 40592 bytes (There are 2 different versions
the same length)
winsock.dll - 24064 bytes
net.exe - 118220 bytes
pcnfs.sys - 63152 bytes (Version 5.0a)
telnetw.exe - 348128 bytes
My NIS server (which does the DNS stuff for me) is running SunOS.
Jules.
--
Julian Field, MEng. j...@soton.ac.uk
Department of Electronics ___ __o Fax: +44 (703) 592082
University of Southampton ___ -\<, Tel: 0703 593021/592774
Southampton SO9 5NH, UK .....O/ O Disclaimers? Who needs 'em!
Rolf Petter Halle
[....]
|> PC-NFS, via WinSock as well as its native toolkit, supports the name
|> and address resolution functionality of the BSD API in the same way as
|> most other Sun systems: via NIS (YP) as well as hosts files. Sites
|> running NIS can relay requests to DNS using the "ypserv -d" mechanism.
|> We have already announced that the next version of PC-NFS will also
|> support "native" DNS, albeit with reduced functionality. (For example,
|> you will not longer be able to mount file systems via the "auto.vol"
|> map.)
|>
Unfortunately, it looks like the d options is missing under HP-UX. This is
a real problem for those of us who can't use Suns for NIS-servers.
If anyone knows a way around this problem, I would really like to hear
about it...
Anyway, DNS support in the next version sounds is very good news, but will
it be released only as a new release (with an upgrade fee), or will it
also be available as a patch on the net (the DNS stuff).
|> Geoff
Rolf
Will Sadler
>PC-NFS, via WinSock as well as its native toolkit, supports the name
>and address resolution functionality of the BSD API in the same way as
>most other Sun systems: via NIS (YP) as well as hosts files.
If you think that most Sun systems run NIS (aka Yellow Pages - gee I
wonder why no one thought there would be a copyright issue with
that one?) then I have this bridge in Florida for sale that you might be
interested in....
Maybe NIS is the default elsewhere, but around here DNS is pretty standard.
Will
--
***************************************************************************
* _______________\|/_ Will Sadler wi...@cica.indiana.edu *
* Laser 151008 /|\ sad...@indiana.edu *
***************************************************************************
"Just Machines to Make Big Decisions /
Programmed by Fellas with Compassion and Vision"
Jon E. Mittelhauser
>In <28g455$l...@dr-pepper.East.Sun.COM> ge...@poori.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
>
>>PC-NFS, via WinSock as well as its native toolkit, supports the name
>>and address resolution functionality of the BSD API in the same way as
>>most other Sun systems: via NIS (YP) as well as hosts files.
>
>If you think that most Sun systems run NIS (aka Yellow Pages - gee I
>wonder why no one thought there would be a copyright issue with
>that one?) then I have this bridge in Florida for sale that you might be
>interested in....
>
>Maybe NIS is the default elsewhere, but around here DNS is pretty standard.
>
Ditto here. I must side with Tom B. here, I think that it is a joke for Sun
to release a Winsock without DNS support. Whether or not it is officialy
part of the API, everyone else seems to be able to support it without any
trouble. I think the root of Tom and my frustration is that 75% of the
mail from people who "can't get Mosaic/Cello to run at all" are running
PC-NFS. If I was Sun, I would be embarrassed that Peter Tattam can write
a shareware winsock which appears to blow the pants of what I am selling.
The fact is that I am simply calling something like
gethostbyname("www.ncsa.uiuc.edu") and the PC-NFS winsock is returning
"Ahh, gee Bob I don't know...". If gethostbyname can't do what the name
implies, I consider it a failure of the Winsock. Geoff is correct that
the API doesn't explicity say that this name should be resolved through
DNS but the rest of the world seems to have assumed it.
I am glad that the next version of PC-NFSs winsock will support DNS,
but I sure hope they hurry it up. I get enough "real" bug reports without
having to answer what I consider to be Sun's as well...
-Jon
---
Jon E. Mittelhauser (jo...@ncsa.uiuc.edu)
Research Programmer, NCSA (NCSA Mosaic for MS Windows)
More info <a href="http://www.ncsa.uiuc.edu/SDG/People/jonm/jonm.html">here</a>
Jeff Guerdat
|>DNS support is not a requirement for WinSock compliance, as you will
|>have found in reading the spec. It is a common myth that the GetXByY()
|>routines are simply front-ends to DNS. While I am looking forward to
|>providing DNS support in PC-NFS, I regard as much more important our
|>(eventual) support for full-blown NIS+. [However, people who are unhappy
|>with our memory footprint will not welcome the arrival of an RNM for
|>this (necessarily) complex system.]
Are there any plans for a Windows DLL for those sites who can get along without DOS
support under Windows? I'd prefer to see the footprint minimized via this mechanism...
Jeff Guerdat
Eastman Kodak