No Comps showing up in Network Neighborhood

[ps2cho]

Ok for some reason my server will not show up in the network neighborhood.
Some days it does, and others it just disappears. I dont know why and i cant transfer files

Its on the correct workgroup, firewall is off. Still nothing...

Is there any other way to connect to it through CMD ?

I forgot the way... :rolleyes:

[harlam357]

Can you ping the IP?

Can you force a connection by using "\\<machine name>"?

Yes, you can map drives through a command prompt... can't give you any syntax for the appropriate commands, but it should be easy to find- search is friend. :D

Could also be a Master Browser issue... I'm not uber familiar with Windows Server OSes, which is what I assume you mean by server... so I'm not sure what kind of havok it could potentially reek on clients if not configured properly. Can you not access the server from any machine on the network or is it limited to one machine?

[ps2cho]

Sorry, its just a XP Home comp, but its my home storage server, web server etc.

Ok ill take a look and try it. Thanks.

[don256us]

map root g:=servernamefolder

Where 'g' = the drive letter that you wish to assign.
Where 'servername' = the name or IP of the server you wish to map to
Where 'folder' = the full path to the item you want to map.

'map root' allows access to the share and all directories up to the root.
'map' only allows access to the share itself.

I don't think that it works in 2000/XP. If anyone finds that any part of what I have posted is incorrect, please correct me. DOS is not my favorite interface.

On a more basic point, none of this will work if you can not see the machine on the network. I have found that if my server is not running when my client machines boot up, the clients refuse to acknowledge the server at all. It makes no sense to me either. Check the IP of the server and see if you can ping that IP from other machines. If you get an IP that seems way off, that would be a good place to start the trouble shooting further.

[harlam357]

I think you need to write the servernamefolder part as such: "\\servername\folder" or further subfolders if necessary.

Yes, I used the wrong slashes in my previous post. It is backslashes('\')... duh, it's Windows for crying out loud. :cry:

[jajmon]

Just because you can't 'see' a computer in the Network Neighborhood doesn't neccesarly mean you can't get to it. If the permissions for the share are setup properly, you should be able to 'map' a drive via windows explorer/tools/map networkdrive, then provide the sharename ie \\myservernamehere\sharename here. 'Seeing' a computer in the network neighborhood has to do with the master browser <google that for more info

[don256us]

I think you need to write the servernamefolder part as such: "\\servername\folder" or further subfolders if necessary.

Yes, I used the wrong slashes in my previous post. It is backslashes('\')... duh, it's Windows for crying out loud. :cry:
You're right. I had them in there but then the spell check took them out. My fault for not double checking.

map root g:=\\servername\folder.

For Novell we use
map root g:=//servername/folder so you are correct there too.

Thanks.

[harlam357]

'Seeing' a computer in the network neighborhood has to do with the master browser <google that for more info

As I said in my first post... what I've done to alleviate this type of issue on my network is to have my Samba server take over Windows network Master Browser piviledges. It's really easy to force such a config in the samba.conf file. This way Windows machines don't fight over who is going to cache the NetBIOS names on the network. Works really well...

Imagine that... Linux controlling Windows. :D