NASLite Network Attached Storage

I have successfully instaleld and configured NASLite+, really easy, straight forward and fast.
I have also addes it to my workgroup and provided a different server name, now "Nas01".
Initially I was able to find and use it from my WinXP client, w/o any problems.
The next day, my new server couldn't be found, from none of my 3 WinXp clients in my network ?!
Telnet, FTP and HTTP worked, of course.

Only when I told my WinXP Explorer to go direkt to it vioa its IP address, "\\192.168.100.99" it would immediately recognize it again and make it available again. But strangely enogh, it shows up with a different Server name, I guess the default name
"Disk-1 auf "NASLite (IP: 192.168.100.99) (192.168.100.99)".
What's going on here, why can't I access it as "\\Nas01", as expected ?!

It sounds to me like you forgot to write the changed information out to either the floppy or USB flash drive. You need to save the configuration before it takes effect. Try to go in and do everything all over again but this time, save the configuration. You should be OK then.

Good Luck.

Sorry, forgot to mention this,
yes, of course, I did save it to the config file on my floppy disk.
I also repeated this several times.
The status screen shows all entires correct, and the server logs read ok to me, yet, its behavior is still different.

It almost feels like WinXP is successfully trying to prevent this Linux/Samba server to become a recognized memeber of its network family.
I also tried to shut everything down and boot NasLite+ first, to allow it to become the "master" in this p2p network scenario, no luck either.

I thought you saved the config but I had to ask

Now, when you mapped the network drive did you check the box that says to "reconnect at login"? You probably did, but again, I have to ask.

Yes, I did.

But even w/o that check box click, it should always find this machine on a network search, at least within this same workgroup ?!

are you running a personal firewall such as zonealarm?

I just had a similar problem with my system (tbh I can't figure out why it worked yesterday!) and the solution was to add the server to the trusted zone in zonealarm.

One more thing that you've probably already tried, but we all forget these things sometimes (at least, I did!)

I had the same problem when I first started using NASLite just over a year ago. Windows 95, 98 & ME computers at work would see the NASLite box but not the XP computers. I got most of the following info from elsewhere in these forums and it has worked for me.

1. Log into the nas box from a command prompt and type the following:

net use \\NASLite-SMB\Disk-1 /USER:NAS-User

same for the other shares, etc.

Then you should be able to hit it with explorer.

2. For earlier versions of Windows. Check bindings - TCP/IP needs to be bound to Client for Microsoft Networks in W9x

3. Turn off any firewall until you can talk to the NASLite server. If using Zonealarm, check Zonealarm has NASLite I/P address as trusted zone. I had quite a bit of trouble with later versions of Zonealarm forgetting the NASlite I/P address. I have since done away with Zonealarm and relying on the Windows SP2 firewall and the hardware firewall in our router.

Regards
Graham

Thanks for the help, butell, none of the above seems to fix my problem ?