Samba glitch
I recently re-arranged my networking setup. I installed a wireless router for my laptop. In order for the laptop to receive information from my LAN under Windoze, I had to basically install the wireless router as a firewall between the DSL modem, and the rest of the LAN. The DSL feeds the "untrusted" port on the router, and the rest of the LAN is attached through one of the "trusted" ports. Effectively, it changed my IP addresses on all the machines on my LAN. Instead of being in the neighborhood of 172.10.xxx.xxx, they are now in the range of 198.162.xxx.xxx.
What this has effectively done is rendered Samba completely blind. While Samba still sees the name of my work group, it cannot see one single computer when I am going through Konqueror. If I use Xfsamba, it still shows the old IP addresses (in the 172.10.xxx.xxx range). It does not show the new IP addresses, nor does it connect to the computers on my LAN. If I use Konqueror, and I type in my Samba addresses in the form, smb://198.162.xxx.xxx, I can actually connect to the computer in question. This tells me that there is a file that has the old IP addresses locked in it, and for some reason, it won't release those IP addresses and use the new addresses. This is happening on all the Slackware machines on the LAN.
What I need to know is the specific file(s) that contain these old IP addresses. The Samba documentation is less than forthcoming on this issue. According to that documentation, this file is called "lmhosts" and is supposed to be stored in the /etc/samba directory. However, this is not how things are done in Slackware. Obviously, there is a file somewhere that contains this information, and I need to change it so I can work with Samba again. Returning the wireless router and the LAN back to the way it was is right out. While Samba won't operate properly, under Windoze, I can share files and printers by way of the wireless router. Since I do a lot of file (and printer) sharing, it's a must that the wireless setup can do this.
While all my machines that run Slackware are also dual boot, and therefore can connect to one another through Windoze and NetBEUI, I want my Samba back. There's something infinitely cool about file sharing between Windoze and Slackware.
I am asking only those who have experienced this problem to reply. I know there is much that is theoretical when it comes to problem solving with Linux. I am not interested in theory. I am interested in getting my Samba back. Please, if you know the file that is causing my misery, please let me know. I don't care what it takes to get things back in operation. I want my Samba back!
Blessed be!
Pappy
|