samba - Jul 2005 - Samba stops working after moving machines

A client changed offices.
Upon connecting the machines at the new location samba is not working.
In particular I am getting an error:

Workgroup is not accessible. You may not have permissions
to use this network resource.

Network path is not found.

The only difference between the previous location and the current is that 
they have not gotten internet connection in the new location yet. Other 
than that all the equipment is the same.

Any suggestions would be greatly appreciated.

On Sun, 10 Jul 2005, Francisco Reyes wrote:

I fogot to mention. The machines all have assigned IPs.. they all can see 
each other (I can ping each other and I can ssh to the FreeBSD server).

Does Samba needs DNS to work? That's the only thing I can possibly think 
off.
> A client changed offices.
> Upon connecting the machines at the new location samba is not working.
> In particular I am getting an error:
>
> Workgroup is not accessible. You may not have permissions
> to use this network resource.
>
> Network path is not found.
>
> The only difference between the previous location and the current is that 
> they have not gotten internet connection in the new location yet. Other
than
> that all the equipment is the same.
>
> Any suggestions would be greatly appreciated.
>
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba
>

> A client changed offices.
> Upon connecting the machines at the new location samba is not working.
> In particular I am getting an error:
>
> Workgroup is not accessible. You may not have permissions
> to use this network resource.
>
> Network path is not found.
>
> The only difference between the previous location and the current is that
> they have not gotten internet connection in the new location yet. Other
> than that all the equipment is the same.
>
> Any suggestions would be greatly appreciated.
>
It sounds like your client's new office location is now on a different
subnet then your Samba server.  Are you using WINS?

If not, try using "wins support = Yes" in the global section of your
smb.conf file.  Restart your Samba server, then point all your clients to
the IP address of your Samba server for their WINS configuration (under the
TCP/IP properties --> advanced --> WINS tab).  You should only need 1
entry
for the WINS server, make sure that "Enable NETBIOS over TCP/IP" is
checked
on.


Regards,

Arnold Andrews
Sr. Systems Administrator
Seagate Technology

Does Samba needs DNS in order to work?
I moved some machines to a new office and for 2 days there was no 
internet. I could not get Samba to work. Tried a number of settings 
including setting it as WINS server.

I also tried "name resolve order = host" and entered all the machines 
into the list (/etc/hosts).

It seems that once the Samba server could see the DNS servers it worked.. 
even when I had not changed the windows clients yet to see DNS.

Running Samba 3.0.14 in FreeBSD 5.4 stable.
Is it possible the problem has to do with the way samba was compiled 
by the port?