I have created a samba server to share Solaris files with NT4 and Win2000 workstations. In early testing it has worked ok. Today a user created a file in a Unix directory while he was on an NT4 box. That file is now not visible to the Windows environment through explorer. It is visible on the Unix side and has similar permissions to other files which are visible both places. The file is visible using dos and mapping a drive and using the DIR command. What has happened?
Stan, Could it be that the file in question has an extension of .dll, .sys, .vxd, .386 , .drv or .pnf? By default explorer (at least in Windows NT 4.0) is configured to hide files with these extensions. You can configure explorer to show files with these extensions, maybe that is all you need to do. Marc Jacobsen Stan York wrote:> > I have created a samba server to share Solaris files with NT4 and > Win2000 workstations. In early testing it has worked ok. Today a user > created a file in a Unix directory while he was on an NT4 box. > That file is now not visible to the Windows environment through > explorer. It is visible on the Unix side and has similar permissions > to other files which are visible both places. The file is visible > using dos and mapping a drive and using the DIR command. > > What has happened?
These files are actually Unigraphics CADD files( .prt). Even when I copy a file (in Unix) which I cannot see in Windows to another filename, I can't see that file. It seems to be some attribute attached to that specific file and any file made from it. Does force create mode or force directory mode do something to the file itself?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello,> I have created a samba server to share Solaris files with NT4 and > Win2000 workstations. In early testing it has worked ok. Today a user > created a file in a Unix directory while he was on an NT4 box. > That file is now not visible to the Windows environment through > explorer. It is visible on the Unix side and has similar permissions > to other files which are visible both places. The file is visible > using dos and mapping a drive and using the DIR command.Some months ago I also had the strange behaviour, of Files getting _sometimes_ lost when connecting from NT4.0 SP5 to Samba 2.06 / 2.0.7, while the connection to an W95 worked fine. My NT box had a NE2000 10MBit clone, and my Samba Serve a 100MBit EEPro100. A few days later I got a second 100MBit EEPro100 for my NT box and everything went fine. The funny thing is that when I use a smbclient running Linux on the NT box everything worked fine. Maybe you have a similar problem, Best wishes Peter ________________________________________ Dr. Peter Schmitteckert / IT-Consulting s-mail: Fridolinstr. 19, 68753 Wagh?usel Web: http://www.schmitteckert.com e-mail: peter@schmitteckert.com Tel.: 07254/951896 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjp5ZcEACgkQHn79UhrElrG83QCgkAC98W16SO28lENOAtXXVsNA 0QoAn1S5JvQMej5ydLxTA8ZKnInD79uz =MS0Y -----END PGP SIGNATURE-----