NASLite Network Attached Storage

I threw a new NASLite+ machine on an existing network. That existing network already had a RedHat server, serving primarily as Samba Server of it's big data disks to WinXP users. Now , altho users can nicely see the new NASLite+ machine and its disks, they can no longer see their old familiar disks from the existing server.

Also, now, even when NASLite+ server is *disconnected* from network and everything rebooted.... users still cannot get to their old data disks. They can ping the old server by *IP address* but not my its Hostname.

Has my new NASLite server just declared itself 'grand poobah master'? and somehow disabled WINS service or what? Can the appearance of the second Samba Server have changed the config file for the original server? How can I somehow just let my new server slip quietly onto the scene?

Any guidance would be appreciated!

By any chance do both boxes have the same name? That would cause DNS/WINS entry to have the ip address of the last booted server. You would be able to ping either by IP but only one by name. This sounds like the case. Take a look in the DNS/WINS tables and see what IP the Hostname has.

My sincere thanks to everyone who stopped by to see if they could help.

I think I've solved my own problem and it had nothing to do with NASLite. As usual, I was doing three things at once and needed to change a user's samba password (which didn't seem to help her), so I went poking around in the smb.conf file, trying to clean things up. In doing so, I deleted a critical space character in the Allowed Hosts parameter, thereby allowing NO machines to see that samba server. Samba's 'testparm' utility didn't detect any errors. Anyway, I simply re-edited smb.conf to put back the 'space'.

Now both servers are happily co-existing on the same network and all Master Browser issues are resolved peacefully.

Again, Thanks for your help. --Mentor