Quote:
Originally Posted by gabsik
Definitly the two networks communicate now(from the linuxbox i'm configuring the windows box with vnc) i have properly set iptables postrouting snat and default routes.
|
I really dont buy the idea of NATting because SNATing broadcast packets wont help you out. Network browsing wont work this way (
WINS is what we opt for cross subnet browsing in real big LAN networks) So comment that rule out from your firewall script.
After you trash that iptables rule out, you have now got two (infact more than two) ways to make your samba+winHOME NETBIOS-name resolutions work(this is the only problem you have, as if in case you would have browsed your samba server via its ip, it would have worked a long way back).
Prior to moving these two ways.. you got to make sure that you can ping b/w these two boxes without natting.
1. Easiest way out --> Add another virtual ethernet interface at samba server with an ip belonging to xp-home-net-class i.e. 192.168.2.X .
Thats it!
The NETBIOS name resolutions would be done directly now as both samba server & XP-HOME box fall in a same subnet.
2. At samba & windows box; modify your lmhosts file to refer each other by its name.
At samba server, modify /etc/samba/lmhosts with
XP-IP XP-BOX-NETBIOS-NAME
& @ windows box, modify \%systemroot%\system32\drivers\etc\lmhosts.sam
SAMBA-IP SAMBA-BOX-NETBIOS-NAME
Enable lmhosts lookup under your network advance settings (& import it if you want to avoid a restart)
This is done as well.