Very Computer

The problem in a nutshell: I'm using VisionFS on SCO 5.0.4.  Some PC's can
see the SCO host in their Network Neighborhood and others can't.

The "blind" PC's have the same workgroup as the others and VisionFS
(although I've found that VisionFS's workgroup doesn't matter.  It works the
same way.)  Their network properties are the same as the "seeing" PC's.
Running \\hostname does not find the SCO host.  I've read all the
troubleshooting guides I can find and done all the suggestions.

One interesting thing:  I downloaded and installed the "Master Browser
Finder" software.  On a seeing PC, it identifies the PC name, the workgroup,
and the master browser (which changes).  On a blind PC, it can't find the
master browser -- it can't even find the PC name or workgroup!

Another interesting thing: On the SCO host I type

    ./visionfs nameinfo

and the blind PC's do not appear on the printout.  Blind PC's do see each
other and the other PC's, just not the SCO host.

Any suggestions?  Thanks.

--- Knute Snortum

e-mail)

    "The three principle virtues of a programmer are: laziness, impatience,
and hubris."

I have VisionFS 1.2 running on my system at work.  Are you running IP?  
If you are, can you ping the VisionFS host from the 'blind' stations?
I had a problem with a couple of workstations that wouldn't see the host.  
I had to uninstall all the networking software and reinstall just the MS
client, the card driver and tcp/ip again and everything worked (win95
clients).  ARe you using DNS, or DHCP?  If not are you updating
/etc/hosts?
--
Bob Curci

try using start>find>computer enter computer name.

not seeing a VFS box in net neibourhood is a known problem that will be
fixed in the next release (apparently), everything else should work fine,
ie. drivemapping etc.

hope this helps

mick

Thanks for the reply!

I can ping the host from the PC, and the PC from the host.  We're using
/etc/hosts.

Well, it's fixed.

Thanks to a suggestion e-mailed to me, I deinstalled all network
protocols and reinstalled only the adapter, MS Client, Print and File
Sharing, and TCP/IP.  (IPX came along for free.)  This seemed to fix it.

Who knows?  It's Microsoft.  Where do you want to go today?

(answer censored.)

---Knute