I am using Samba version 2.0.5 on a unix box running Sun Solaris 2.6. My users can't log onto the network to print and I can't figure out the reason. I have used the testparm and smbstatus commands, and the Samba configuration file looks fine. Could anyone tell me where the Samba log file is located or what the name of the log file is? I would appreciate any other suggestions.
I've read through the BROWSING*.txt files in docs/textdocs and I think I set everything up right but I can't get this to work. I am using IPSEC to connect two lans that are seperated by the internet and use dsl lines for internet connection. That is setup and working. I can ping from a client on one subnet to a client on another subnet with no problems. One subnet is 192.168.3.0 and the other is 192.168.4.0 The 192.168.3.0 subnet has the workgroup of irish and the 192.168.4.0 has the workgroup of msp. I want both of these subnets to see both workgroups. All clients are win98 and there is a samba server on each network that is also doing the ipsec and acting as the firewall(currently setup to accept everything). Each subnet has the samba server setup as the WINS server for that subnet. in the smb.conf file on 192.168.3.1 I added: remote browse sync = 192.168.4.1 remote announce = 192.168.4.1 and on 192.168.4.1 I added: remote browse sync = 192.168.3.1 remote announce = 192.168.3.1 Any ideas how to solve this so that each subnet can see and use both workgroups. Another question about the WINS servers, I read that it is best if only one is used for both subnets. If I do this and the link drops, the subnet without samba setup for wins will of course no longer have a wins server. Will this Win98, ME clients automatically start using broadcast based name resolution when the WINS server becomes inaccessable? TIA Andy Worthington
Ok, I now have the machines visible on each subnet in network neighborhood.
Here is the setup of the network:
Workgroup:MSP - 192.168.4.0
2 Windows ME clients
|
| 192.168.4.1
Linux samba, firewall, ipsec machine
| 64.218.*.*
|
Internet
|
| 64.217.*.*
Linux samba, firewall, ipsec machine
| 192.168.3.1
|
6 Windows 98, ME clients
Workgroup: Irish 192.168.3.0
Both subnets can see all clients but when Irish workgroup clients try to
connect to either of the clients on the other subnet they get an error
message about the client not being found. Same with clients on the MSP
subnet. If they try to communicate with the Linux server on the other
subnet that works fine. Here is what I get if I try to connect from the
Irish linux server to one of the MSP clients:
[root@fw samba]# smbclient -L "Mindy"
doing parameter domain logons = yes
doing parameter logon script = netlogon.bat
doing parameter printcap name = /etc/printcap
doing parameter load printers = yes
doing parameter printing = lprng
doing parameter print command = /usr/bin/lpr -b -h -r -P%p %s
pm_process() returned Yes
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
added interface ip=192.168.3.1 bcast=192.168.3.255 nmask=255.255.255.0
added interface ip=64.217.29.97 bcast=64.217.29.103 nmask=255.255.255.248
Client started (version 2.0.7).
resolve_wins: Attempting wins lookup for name Mindy<0x20>
bind succeeded on port 0
Got a positive name query response from 127.0.0.1 ( 192.168.4.66 )
Connecting to 192.168.4.66 at port 139
timeout connecting to 192.168.4.66:139
Connection to Mindy failed
By that I am assuming it is either a routing or firewall problem keeping the
connection from working. Pinging the client works fine though. How can I
find where the problem is to solve it? The connection between 192.168.3.0
and 192.168.4.0 is via a freeswan ipsec tunnel.
Thanks
Andy
Andy, On Fri, 27 Oct 2000 13:55:52 -0500, Andy Worthington wrote:>Ok, I now have the machines visible on each subnet in network >neighborhood. >Here is the setup of the network: > >Workgroup:MSP - 192.168.4.0 >2 Windows ME clients > | > | 192.168.4.1 > Linux samba, firewall, ipsec machine > | 64.218.*.* > | >Internet > | > | 64.217.*.* >Linux samba, firewall, ipsec machine > | 192.168.3.1 > | >6 Windows 98, ME clients >Workgroup: Irish 192.168.3.0 >>[root@fw samba]# smbclient -L "Mindy"[...]>timeout connecting to 192.168.4.66:139 >Connection to Mindy failed > >By that I am assuming it is either a routing or firewall problem >keeping the connection from working. Pinging the client works fine >though. How can I find where the problem is to solve it? The >connection between 192.168.3.0 and 192.168.4.0 is via a freeswan >ipsec tunnel.Make sure ports 137, 138, 139, both tcp and udp get through. Regards, Robert -- --------------------------------------------------------------- Robert.Dahlem@gmx.net Fax +49-69-432647 --------------------------------------------------------------- Sent using PMMail (http://www.pmmail2000.com) - fast, decent, email software; far better than Outlook. Try it sometime.