Hello, I have a slight problem with browsing a samba server. I can see the server (www) in network neighborhood but when I click on it to see the shares I get that the network is busy or some such. I get this error with ever win32 system on the network. I don't have another linux box at the moment to test with linux. I would love to say that below you will find the samba config but I have no access to the net from the linux box at the moment and can't copy across the network. hehe. Any ideas? Thanks.
I have the same problem. You could (grimace (-< ) copy your smb.conf to a floppy and carry it to your email box. I'd be interested in comparing smb.conf files. Steve -----Original Message----- From: samba-admin@us5.samba.org [mailto:samba-admin@us5.samba.org]On Behalf Of Charles Williams ( CEO ACNS ) Sent: Thursday, November 16, 2000 7:16 AM To: samba@us5.samba.org Subject: samba headaches Hello, I have a slight problem with browsing a samba server. I can see the server (www) in network neighborhood but when I click on it to see the shares I get that the network is busy or some such. I get this error with ever win32 system on the network. I don't have another linux box at the moment to test with linux. I would love to say that below you will find the samba config but I have no access to the net from the linux box at the moment and can't copy across the network. hehe. Any ideas? Thanks.
and the networking and multiple subnet issues of using SAMBA continue. Steve and Charles, welcome to the wonderful world of SAMBA. What you need to do, to use SAMBA, is put your SAMBA on Unix box that is in walking distance of your win32 machines, on the same subnet, and never ever put the server on a different subnet or move it far from the users. SAMBA is NOT an enterprise solution for file access, when going from a win32 box to a Unix/Linux SAMBA server. It just doesn't Work! I became a serious Unix administrator over the past year, I am of course, still learning ALOT, what I did learn, from trying to get SAMBA working, from Win32 boxes to SAMBA-Unix box, is forget it, unless the network is "flat" and/or you are right next to the server. Unix is great, but for having users, already on a Windows network, using windows clients, just use a WINDOWS server, when part of the server's function is file sharing.... I am tired of fight SAMBA, I am sure I am not the only one. tpaul -----Original Message----- From: Steve Gonzales [mailto:gonzo@eng.lsu.edu] Sent: Thursday, November 16, 2000 9:29 AM To: samba@us5.samba.org Subject: RE: samba headaches I have the same problem. You could (grimace (-< ) copy your smb.conf to a floppy and carry it to your email box. I'd be interested in comparing smb.conf files. Steve -----Original Message----- From: samba-admin@us5.samba.org [mailto:samba-admin@us5.samba.org]On Behalf Of Charles Williams ( CEO ACNS ) Sent: Thursday, November 16, 2000 7:16 AM To: samba@us5.samba.org Subject: samba headaches Hello, I have a slight problem with browsing a samba server. I can see the server (www) in network neighborhood but when I click on it to see the shares I get that the network is busy or some such. I get this error with ever win32 system on the network. I don't have another linux box at the moment to test with linux. I would love to say that below you will find the samba config but I have no access to the net from the linux box at the moment and can't copy across the network. hehe. Any ideas? Thanks.
True, going out was never a problem, but I don't know anyone, with machines that are talking across long distances, and over multiple subnets, who could get their Win32 machines, to be able to create a mapped drive to a Samba 2.7 share, on a Solaris 2.7 If anyone knows how, I would be willing to pay $ to have you help me fix mine! thanks tpaul -----Original Message----- From: Charles Williams ( CEO ACNS ) [mailto:cwilliams@acns-online.com] Sent: Thursday, November 16, 2000 11:21 AM To: TPsmith@ixl.com; gonzo@eng.lsu.edu; samba@us5.samba.org Subject: Re: samba headaches Thanks for the feedback. However, have got it working that I can get out from the linux box to the win32 systems now. still same prob. going in though. no that I have access here is the config. [global] workgroup = acns.intern server string = Internal WWW Server hosts allow = 192.168.10. 127. name resolve order = lmhost bcast auto services = main log file = /var/log/samba/log.%m max log size = 50 security = server password server = 192.168.10.2 browse list = yes password level = 8 username level = 8 encrypt passwords = yes smb passwd file = /usr/local/samba/private/smbpasswd unix password sync = Yes passwd program = /usr/bin/passwd %u passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n*passwd:*all*authentication*tokens*updated*successfully* socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 remote browse sync = 192.168.10.2 remote announce = 192.168.10.255 local master = no os level = 25 domain master = no preferred master = no domain controller = 192.168.10.2 domain logons = no dns proxy = no Good luck. hehe #============================ Share Definitions ============================= [main] comment = Main access path = / browseable = yes public = yes writable = yes printable = no ----- Original Message ----- From: <TPsmith@ixl.com> To: <gonzo@eng.lsu.edu>; <samba@us5.samba.org> Sent: Thursday, November 16, 2000 4:32 PM Subject: RE: samba headaches and the networking and multiple subnet issues of using SAMBA continue. Steve and Charles, welcome to the wonderful world of SAMBA. What you need to do, to use SAMBA, is put your SAMBA on Unix box that is in walking distance of your win32 machines, on the same subnet, and never ever put the server on a different subnet or move it far from the users. SAMBA is NOT an enterprise solution for file access, when going from a win32 box to a Unix/Linux SAMBA server. It just doesn't Work! I became a serious Unix administrator over the past year, I am of course, still learning ALOT, what I did learn, from trying to get SAMBA working, from Win32 boxes to SAMBA-Unix box, is forget it, unless the network is "flat" and/or you are right next to the server. Unix is great, but for having users, already on a Windows network, using windows clients, just use a WINDOWS server, when part of the server's function is file sharing.... I am tired of fight SAMBA, I am sure I am not the only one. tpaul -----Original Message----- From: Steve Gonzales [mailto:gonzo@eng.lsu.edu] Sent: Thursday, November 16, 2000 9:29 AM To: samba@us5.samba.org Subject: RE: samba headaches I have the same problem. You could (grimace (-< ) copy your smb.conf to a floppy and carry it to your email box. I'd be interested in comparing smb.conf files. Steve -----Original Message----- From: samba-admin@us5.samba.org [mailto:samba-admin@us5.samba.org]On Behalf Of Charles Williams ( CEO ACNS ) Sent: Thursday, November 16, 2000 7:16 AM To: samba@us5.samba.org Subject: samba headaches Hello, I have a slight problem with browsing a samba server. I can see the server (www) in network neighborhood but when I click on it to see the shares I get that the network is busy or some such. I get this error with ever win32 system on the network. I don't have another linux box at the moment to test with linux. I would love to say that below you will find the samba config but I have no access to the net from the linux box at the moment and can't copy across the network. hehe. Any ideas? Thanks.
Hey Steve and everyone, My apologies for sounding sarcastic. I was just being honest with my frustration. If someone can show me a document in the samba archives, or samba site, which shows how to do the following, I will apologize and never write a sarcastic message to this forum again: ------Don't just have FAQs on the SAMBA site------- ---How about sample cases and the fix to the cases?--- -------Show Me How To Do the Following------- *How to create a samba share on Unix Solaris 2.7, running 2.7 of SAMBA, with the attached config file, and to ensure, that even if the client has one IP segment, and the server has a different IP segment, on different subnets, and the distance between the Win32 client machines and the server is across town but with a good T1. ----------------- I understand that this forum is for how to use SAMBA, not how to create windows shares. But when I can map a network drive to a server, sitting on the same network, in the same IP range, in the same subnet, which is Windows, and before we moved the server to different IP and subnet, and location, sometimes it worked and other times I got the semaphore timeout or network busy message, but now, there is nothing but semaphore timeout or network busy messages, which shows the multiple restrictions on an admin, when using SAMBA, I am just thinking, maybe someone, who can code 100x better than myself, which is probably most people, could take the time and make connecting from win32 clients to unix-samba clients more flexible. I apologize if my attitude annoyed anyone. I am frustrated with the inability to purchase feasable support for using SAMBA. thanks tpaul -----Original Message----- From: Steve Gonzales [mailto:gonzo@eng.lsu.edu] Sent: Thursday, November 16, 2000 1:59 PM To: samba@us5.samba.org Subject: RE: samba headaches I really apologize for the need of the original email posted below. I don't know what got into this person; but whatever it is, I sincerely apologize if it was something I said. I thought that this list was a serious discussion of Samba. Sometimes NT stuff does appear in this forum; however, consider the numbers of LANs that integrate either NT into Linux networks and visa versa. I realize that there is another forum, samba_ntdom, that is there to specifically address Linux/NT issues; however, on rush decision times, the more information one has, the better an educated guess he/she can make about what to do next to correct problems. With that said, I don't think that sarcasm is part of the equation. I want to visit the "Argument Room" not the "Abuse Room" (ala Monty Python). BTW, tpaul, my network _is_ flat and I inherited a network in which our original RedHat 6.2 Linux dialin server _did_ act right in an NT domain network. I am trying to replicate this on a new server using RedHat 7 and all that came with it. As many people are finding out, there are great differences btn 6.2 and 7.0, not the least of which is the Samba suite. Also, if Samba and NT do not work together, why have these forums? That is all. Steve -----Original Message----- From: TPsmith@ixl.com [mailto:TPsmith@ixl.com] Sent: Thursday, November 16, 2000 9:32 AM To: gonzo@eng.lsu.edu; samba@us5.samba.org Subject: RE: samba headaches and the networking and multiple subnet issues of using SAMBA continue. Steve and Charles, welcome to the wonderful world of SAMBA. What you need to do, to use SAMBA, is put your SAMBA on Unix box that is in walking distance of your win32 machines, on the same subnet, and never ever put the server on a different subnet or move it far from the users. SAMBA is NOT an enterprise solution for file access, when going from a win32 box to a Unix/Linux SAMBA server. It just doesn't Work! I became a serious Unix administrator over the past year, I am of course, still learning ALOT, what I did learn, from trying to get SAMBA working, from Win32 boxes to SAMBA-Unix box, is forget it, unless the network is "flat" and/or you are right next to the server. Unix is great, but for having users, already on a Windows network, using windows clients, just use a WINDOWS server, when part of the server's function is file sharing.... I am tired of fight SAMBA, I am sure I am not the only one. tpaul -----Original Message----- From: Steve Gonzales [mailto:gonzo@eng.lsu.edu] Sent: Thursday, November 16, 2000 9:29 AM To: samba@us5.samba.org Subject: RE: samba headaches I have the same problem. You could (grimace (-< ) copy your smb.conf to a floppy and carry it to your email box. I'd be interested in comparing smb.conf files. Steve -----Original Message----- From: samba-admin@us5.samba.org [mailto:samba-admin@us5.samba.org]On Behalf Of Charles Williams ( CEO ACNS ) Sent: Thursday, November 16, 2000 7:16 AM To: samba@us5.samba.org Subject: samba headaches Hello, I have a slight problem with browsing a samba server. I can see the server (www) in network neighborhood but when I click on it to see the shares I get that the network is busy or some such. I get this error with ever win32 system on the network. I don't have another linux box at the moment to test with linux. I would love to say that below you will find the samba config but I have no access to the net from the linux box at the moment and can't copy across the network. hehe. Any ideas? Thanks.
>and the networking and multiple subnet issues ofusing SAMBA continue.>Steve and Charles, welcome to the wonderful world ofSAMBA. What you>need to >do, to use SAMBA, is put your SAMBA on Unix box thatis in walking>distance >of your win32 machines, on the same subnet, and neverever put the>server on >a different subnet or move it far from the users.SAMBA is NOT an>enterprise solution for file access, when going froma win32 box to a>Unix/Linux SAMBA server. It just doesn't Work!It does work, and works extremely well, I have a WAN site setup with 3 subnets at and a Linux box located at each subnet acting as a gateway,Samba (including WINS),DNS,Webproxy server. All sites (subnets) can see and access all servers and shares on the network. Even people dialing up using Windows Dialup networking into our site can see all servers in the network neighbourhood. Each server acts as a domain login server so login scripts dont have to travel across the WAN, but all password authentication happens at the master server. We operate an NIS system plus use encrypted passwords to allow users to change their passwords and allow me to centrally manage users without having to update every server.> I became a serious Unix administrator over the pastyear, I am of course, still learning ALOT,>what >I did learn, from trying to get SAMBA working, fromWin32 boxes to>SAMBA-Unix box, is forget it, unless the network is"flat" and/or you>are >right next to the server.I suggest you do alot more research and reading like I did, before passing judgement and assuming to be a "serious" Unix administrator. There are plenty of books and pages on the internet describing how to setup subnet browsing through Samba. Make use of search engines on the internet to hunt the docs down. I will write up a short description of my setup and necessary options in each smb.conf for you and send to you (when I get time) if this helps.>Unix is great, but for having users, already on aWindows network,>using >windows clients, just use a WINDOWS server, when partof the server's>function is file sharing.... I am tired of fightSAMBA, I am sure I am>not >the only one.I get tired of reading to many postings here describing problems which relate more to people lacking skills in networking administration than to SAMBA. I believe if people took more time to become more skilled before using such powerful software then we wouldnt see so many posts. Even using their own initiative and read the documentation first. As the saying goes, A bad carpenter always blames his tools. ====. ,,, (o o) ==============oOO==(_)==OOo=============David Endres, mailto:bigmudcake@yahoo.com ===============( )==( )============= \ ( ) / \_) (_/ __________________________________________________ Do You Yahoo!? Yahoo! Calendar - Get organized for the holidays! http://calendar.yahoo.com/
thanks David. I thank you for your insight, and would be grateful to get the "write-up" of your setup, whenever you can. I found that the "real" reason I was so frustrated, had little to do with my skill level in networking (I have run multiple networks), and less to do with SAMBA, but more to do with the fact that I am an network/systems engineer, with no knowledge of when things change on the infrastructure, that my infrastructure sits on. Our corporate network/systems guys, without intent, don't give us information on what changes they do and/or when. I had tried to rule them out before I flamed this list, as the reason my SAMBA wasn't working, but just yesterday learned that they had modified route tables and wins servers and all kinds of fun stuff that could have been causing my issues. I moved the server to this building and put it on the same subnet as the client machines and everything is fine. I don't know why it couldn't work on the separate subnets, but if I had more time to figure it out, before moving on, I would do the proper research and not waste my and your time flaming this mailing list. thanks for your tolerance, tpaul -----Original Message----- From: David Endres [mailto:bigmudcake@yahoo.com] Sent: Friday, November 17, 2000 5:40 PM To: samba@lists.samba.org Cc: TPsmith@ixl.com Subject: RE: samba headaches>and the networking and multiple subnet issues ofusing SAMBA continue.>Steve and Charles, welcome to the wonderful world ofSAMBA. What you>need to >do, to use SAMBA, is put your SAMBA on Unix box thatis in walking>distance >of your win32 machines, on the same subnet, and neverever put the>server on >a different subnet or move it far from the users.SAMBA is NOT an>enterprise solution for file access, when going froma win32 box to a>Unix/Linux SAMBA server. It just doesn't Work!It does work, and works extremely well, I have a WAN site setup with 3 subnets at and a Linux box located at each subnet acting as a gateway,Samba (including WINS),DNS,Webproxy server. All sites (subnets) can see and access all servers and shares on the network. Even people dialing up using Windows Dialup networking into our site can see all servers in the network neighbourhood. Each server acts as a domain login server so login scripts dont have to travel across the WAN, but all password authentication happens at the master server. We operate an NIS system plus use encrypted passwords to allow users to change their passwords and allow me to centrally manage users without having to update every server.> I became a serious Unix administrator over the pastyear, I am of course, still learning ALOT,>what >I did learn, from trying to get SAMBA working, fromWin32 boxes to>SAMBA-Unix box, is forget it, unless the network is"flat" and/or you>are >right next to the server.I suggest you do alot more research and reading like I did, before passing judgement and assuming to be a "serious" Unix administrator. There are plenty of books and pages on the internet describing how to setup subnet browsing through Samba. Make use of search engines on the internet to hunt the docs down. I will write up a short description of my setup and necessary options in each smb.conf for you and send to you (when I get time) if this helps.>Unix is great, but for having users, already on aWindows network,>using >windows clients, just use a WINDOWS server, when partof the server's>function is file sharing.... I am tired of fightSAMBA, I am sure I am>not >the only one.I get tired of reading to many postings here describing problems which relate more to people lacking skills in networking administration than to SAMBA. I believe if people took more time to become more skilled before using such powerful software then we wouldnt see so many posts. Even using their own initiative and read the documentation first. As the saying goes, A bad carpenter always blames his tools. ====. ,,, (o o) ==============oOO==(_)==OOo=============David Endres, mailto:bigmudcake@yahoo.com ===============( )==( )============= \ ( ) / \_) (_/ __________________________________________________ Do You Yahoo!? Yahoo! Calendar - Get organized for the holidays! http://calendar.yahoo.com/