I would like to thank everyone who assisted me with this problem. It turns out that the problem was caused by the fact that we were running selinux on the server. Once it was disabled the share was accessible.
Thanks Ayo -----Original Message----- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of Ayo Adeyeri Sent: Thursday, November 11, 2010 9:37 AM To: John Drescher; samba Subject: Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME Thanks John, I just removed the "." , changed the workgroup name to covecapcom but I am still getting the same errors in the log file when I attempt to connect to either of the shares from a windows client. Thanks, Ayo Adeyeri -----Original Message----- From: John Drescher [mailto:dresche...@gmail.com] Sent: Thursday, November 11, 2010 9:30 AM To: Ayo Adeyeri; samba Subject: Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME Network names with a . in them are not supported. Well unless you are talking about an ads realm. John This e-mail message, and any enclosures, is intended only for the persons to whom it is addressed, and may contain confidential information. Any use, distribution, modification, copying or disclosure by any other person is strictly prohibited. If you receive this message in error, please notify the sender by return e-mail and delete this message from your computer. InfoHedge disclaims all responsibility from and accepts no liability whatsoever for any incorrect, misleading or altered information contained herein, or for the consequences of any unauthorized person acting, or refraining from acting, on any information contained in this message. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba