Still running a small network, now with a RH7.3p server (SAMBA) and one Win98 workstation. The server can see and copy files from the workstation just fine. However, the workstation doesnot ever see the server in Network Neighborhood. I've looked at all the entries in the forums, some are simular but don't seem to help me. Any suggestions would be helpful.
Pat

Hi,

Can U still explain in detail, what exactly you are looking for.


Mallikarjun

I am a newbie myself. However, I just went through some of this. There are lots of factors that could impact your issue. The answers to the following questions could help lead you to the solution or give us clues to a more specific direction.
Do you have the "Client for Microsoft Networks" installed on your Windows 98 PC?
Is your workgroup on the Windows 98 PC the same as the domain name defined for your Samba Server? ... If not you will have to look at the entire network to find the Samba Server.

I'm trying to connect the Win98 box to the SMB server to access the shares on it. I've copied a document from the Win box to the server, but the server does not even show up in the N.Neighbor Hood of the Win box???
Pat

Until I hear otherwise, my first guess is that your problem is on the Win98 networking setup.
Right-click on your Network Neighborhood icon and choose properties.
If you don't see Client for Microsoft Networks at or near the top, you need to click the add button and go into clients to add it.
If I am off base on that one, your Network Neighborhood only shows computers in the same group as your PC and servers. Your Samba server will not be seen as a server. If it is not in the same group you will have to open "entire network".

Rod,
I didn't see your first reply when I submitted my answer to mallikarjun. The setup on the Win 98 box is correct MC client, TCP/IP, and file and print sharing. You stated that the workgroup of the Win box needs to be the same as the servers domain name??? I thought that it had to be the same as the name in the smb.conf file??? That's the way I set it up each being left as workgroup. Need more help I guess.
Pat

My reference to domain server name was probably confusing. I am not always clear of the distinctions myself.
If you set domain master to True in smb.conf it uses the workgroup name for the domain name so they are the same.
I am looking at my settings.
I belive these are the significant settings in smb.conf.
workgroup = (same name for Samba and Win98)
announce as = win95 (Works for Win95 & up.)
name resolve order = hosts wins (This is my setting. Just make sure hosts is first.)
setup your linux server IP address in the hosts file (probably /etc/hosts)

I think getting the hosts settings correct is what resolved the problem for me now that I think about it some more. As I understand it, Linux does not constantly announce its presence the way Windows does.

Ok, I finally got the server to show up in Explorer/N.N. However, when I double click it to access folders I get an error about no connection to computer or shared folders, check to make sure the spelling is right. Everything double checks. The workstation has an account on the server. I have set it up so that the workstation should access it's home directory???
Don't know what I'm doing wrong now.
Pat

I think I had that error. Don't remember how I solved it unless it had to do with conflicting firewalls or domain services.

is it working with windows NT?

My domain services is being supplied by the Samba Server instead of an NT Server. It looks the same to my Windows workstations. I have Win95, Win98, NT and XP attaching to the server. I have not yet logged in to the domain server with NT or XP though. I just attach to them and give them a userid and password. Not completely happy with that but not a priority since the production workstations are Win9x.
Since I have domain services setup, my Win9x PCs are setup to login to the windows network. I had it working without domain services at first. Then you just attach to the server just like any peer-to-peer connection.
If you already have an NT server and you setup your Samba for domain services, you can create conflicts.
If you already have a firewall and setup a firewall on Samba or on a local PC, you will create conflicts.
Our firewall is built into our DSL router. When one of our users turned on Norton Firewall on the local Win98 PC, she received a message similar to the one you described.

Oops!
I did not notice that the last question was from you PatC. I replied to someone elses question. Hope there was something helpful anyway.