LrngTheHardWay
09-23-2002, 02:26 PM
...and a bone-headed idea.
To appease my wife, I allowed myself to be convinced that our network would benefit from a Samba installation. Not being *too* unfamiliar with Linux (been using it for around 3 years now), I figured that this was within my abilities to manage.
Well.....something went wrong and I'm slamming my head against the edge of the desk, feeling like I should just buy a new hard drive and re-install RH-7.3 and sort things out later. (With a slew of birthdays this month, that's just not going to happen!)
Our Home Network:
2 RH-7.3 Linux desktops (#1 & #2)
1 Win98SE desktop (#3)
1 WinME desktop (#4)
7 other Win98SE Desktops, disconnected for the time being
2 Workgroup Switches, 1 disconnected for the time being
1 Broadband Router/Switch
1 DSL modem
The arrangement is reasonably logical:
* "The IP Cloud" connects to the DSL modem.
* DSL modem connects to the "WAN" port of the BB Router.
* Each WG Switch connects to the BB Router LAN ports.
* One Linux desktop, #1, is connected directly to the Router/Switch.
* All Desktops, with the exception of (#1) are connected to WG Switches.
* The Router is firewalled (also using SPI instead of NAT).
* Each Desktop is firewalled as well.
* Router uses RIP1 dynamic routing.
* Except for the DSL link, everything runs at 100Mb/s.
* #1's IP is static, with all others DHCP/BOOTP assigned by router. DHCP addy pool (scope) excludes #1's IP addy.
It has been up--in this general configuration--for a few months, with no connectivity problems, and all systems are current (as of 19 September, 2002) on all patches/updates.
Saturday night, I sat down to install Samba on #1, and had mild success. Just before going to bed for the night, I gave SWAT a try, and decided to resume working on things in the morning.
Shut Down....go to bed.
Sunday morning: I fire things up to finish configuring and no Internet connectivity on #1; however, #s 2, 3 and 4 have no problems connecting to the Internet. Uh-oh, oops, !&(^%!, and so forth.
I spent a few hours going through configuration files (ifcfg-eth0, resolv.conf, network, hosts, smb.conf and so on) with nothing looking strange--even when comparing file contents with those on #2.
Situation:
* #1 can ping loopback
* #1 can ping all LAN nodes (including router near-side)
* All nodes can ping #1
* #1 CANNOT ping router far-side, nor any ISP DNS server (of course)
I'm fairly sure that I'm missing something simple--maybe even painfully obvious--due to tunnel-visioning developed over Sunday and carrying over to this morning...nevertheless, I'm ready to pull my hair out over this.
Does this kind of situation sound familiar to anyone?
How about opinions, ideas or WAGs?
To appease my wife, I allowed myself to be convinced that our network would benefit from a Samba installation. Not being *too* unfamiliar with Linux (been using it for around 3 years now), I figured that this was within my abilities to manage.
Well.....something went wrong and I'm slamming my head against the edge of the desk, feeling like I should just buy a new hard drive and re-install RH-7.3 and sort things out later. (With a slew of birthdays this month, that's just not going to happen!)
Our Home Network:
2 RH-7.3 Linux desktops (#1 & #2)
1 Win98SE desktop (#3)
1 WinME desktop (#4)
7 other Win98SE Desktops, disconnected for the time being
2 Workgroup Switches, 1 disconnected for the time being
1 Broadband Router/Switch
1 DSL modem
The arrangement is reasonably logical:
* "The IP Cloud" connects to the DSL modem.
* DSL modem connects to the "WAN" port of the BB Router.
* Each WG Switch connects to the BB Router LAN ports.
* One Linux desktop, #1, is connected directly to the Router/Switch.
* All Desktops, with the exception of (#1) are connected to WG Switches.
* The Router is firewalled (also using SPI instead of NAT).
* Each Desktop is firewalled as well.
* Router uses RIP1 dynamic routing.
* Except for the DSL link, everything runs at 100Mb/s.
* #1's IP is static, with all others DHCP/BOOTP assigned by router. DHCP addy pool (scope) excludes #1's IP addy.
It has been up--in this general configuration--for a few months, with no connectivity problems, and all systems are current (as of 19 September, 2002) on all patches/updates.
Saturday night, I sat down to install Samba on #1, and had mild success. Just before going to bed for the night, I gave SWAT a try, and decided to resume working on things in the morning.
Shut Down....go to bed.
Sunday morning: I fire things up to finish configuring and no Internet connectivity on #1; however, #s 2, 3 and 4 have no problems connecting to the Internet. Uh-oh, oops, !&(^%!, and so forth.
I spent a few hours going through configuration files (ifcfg-eth0, resolv.conf, network, hosts, smb.conf and so on) with nothing looking strange--even when comparing file contents with those on #2.
Situation:
* #1 can ping loopback
* #1 can ping all LAN nodes (including router near-side)
* All nodes can ping #1
* #1 CANNOT ping router far-side, nor any ISP DNS server (of course)
I'm fairly sure that I'm missing something simple--maybe even painfully obvious--due to tunnel-visioning developed over Sunday and carrying over to this morning...nevertheless, I'm ready to pull my hair out over this.
Does this kind of situation sound familiar to anyone?
How about opinions, ideas or WAGs?