At 01/07/06 11:54, Ken Schneider wrote:
On Sat, 2006-01-07 at 11:20 -0600, Eric Hines wrote:
D*n. Sorry for the direct email. Screwed up on the REPLY TO button.
<snip>
I think you've about got it, now. And my LAN is up today--two days in a row. I've done nothing, that I know of, to achieve this. And some clarifying data that, as my meager knowledge grows, may in fact be relevant. I say that the Linksys sits on the edge of my LAN and everything happens behind it, and that's the intent. However, all three NICs are on the SUSE Samba server, and because of the way YaST works, all three NICs have as their default gateway the Linksys. My understanding is that default GWs are addresses of last resort, so my claim that everything is happening behind the Linksys here stands (e.g., IP Forwarding is on, the stack knows where the interfaces are, etc), but I could be wrong. The smb.conf file (I've included only the global part, as the shares wouldn't seem relevant to this problem) and log excerpts are below.
I have wins support = yes; and I have 2 instances of winbindd running.
I have win2k Pro and XP Pro installed on the two devices. No "Home" versions for me.
Thanks
Eric Hines
<hugh snip>
Eric,
Since you are using your PC as a router with it (the PC) between two internal subnets and the internet the PC only needs to have a single default GW and IP forwarding turned on. The proper setup would have a separate hub/switch connected to each secondary NIC (or a crossover cable if only one PC is used) for network access.
diagram:
ISP modem | Linksys router | 192.168.1.1 (I may have the subnets mixed up but the theory is the | same) Also this is the default GW for the samba PC. | 192.168.1.2 | PC external NIC | samba PC |___________ | | | PC NIC #2 - internal network #1 192.168.100.x | PC NIC #3 - internal network #2 192.168.200.x
Any PC's on internal #1 would set their default GW to the IP address if the NIC #2 on the samba PC. The same goes for PC's on internal #2 as they would have their default GW set to the IP of NIC #3 on the samba PC. I think most of your problems are one of routing not working as it should because the default GW's are not being properly setup or understood. If you want to talk via land line let me know in a private email. Not sure were you live, I'm in SW Florida.
If I understand you correctly, I think that is my set up, including with IP forwarding turned on. Below is my version of ASCII art, with more detail. I think it shows what you're talking about. .3.9 ---Laptop----Hub---------.3.1-----Samba (PDC/dns/dhcp)-----.2.2-------------Hub-----PC-----.2.9 (WinXP NIC (NIC on Samba | (NIC on Samba NIC (Win2k laptop) server) .1.2 server) PC) (NIC on Samba server) | Linksys router/switch .1.1 | ISP's Cable Modem | Internet The laptop NIC has .3.1 as its default gateway, the PC NIC has .2.2 as its default gateway, and the three NICs on the Samba server (.1.2, .2.2, and .3.1) all have, because of the way YaST does this, the Linksys as their default gateway. I think I'd like to have .2.2 and .3.1 each have .1.2 as their default gateway, but I don't know how to do that. The Hubs exist because of the physical layout of my office, not, unfortunately, through any special acumen on my part. However, each hub has only its computer and default gateway NIC plugged into it. I'm in a suburb of Dallas. I don't mind the telecon, but I think we may be at an accurate description of the LAN, now. Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell