|
On Sun, 6 Sep 2009, Nick Couchman wrote:
> Thanks for the suggestions, Joe! On the first count, yes,
> the network where the virtual IP sits has several windows
> machines (a couple dozen). On the second count, I
> actually gave this a shot, set up Samba and turned on WINS
> Proxy, then pointed the real servers at the IP of the LVS
> machine for WINS. Unfortunately I got errors in the Samba
> logs saying that the clients need to contact the WINS
> Server.
Samba is not the easiest thing to debug I'll admit.
You have two networks of windows machines joined by a
machine that happens to be an linux LVS director, but which
isn't doing anything to packets to ports 137,138.
Getting the two networks of windows machines to be on the
same NT domain (or whatever its called) has got to be a
solved problem (although I don't know the solution).
Do the two lots of windows machines have to be on the same
IP network? In this case you'll have to NAT out 137,138 on
the realservers (I think both udp and tcp are involved). If
not, then you'll need to setup the director to do the
routing (turn off lvs first to simplify things).
I expect Samba has got to be able to do it as well.
For the ip2route method of getting realservers to talk to
the outside world have a look at
http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.non-lvs_clients_on_realservers.html#3-tier_routes
Joe
--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
