|
Hi Joe,
Ive tried the solution, done all as stated, and the second email, but, the real
server still goes to the WINS server and shuts down the 'windows networking'
element because of the static mapping.
The solution I'm currently running is to do as John says with lmhosts, but also
include an entry for each of the file/sql servers I need to access, switch off
the WINS client (on the real server) and do LMhosts lookups instead. This is
letting me map/access the servers I need for the webserver to run.
Then I entered the static route into the WINS server (of the VIP+netbios name)
for all client lookups from the internal network, now all clients can map the
drives.
It's a little bit more housekeeping than I wanted (WINS is dynamic), but, it
works! and thats all that matters!
Thanks for all the help both you and John have given, if you want any further
assistance for info for the HOWTO see below or drop me a note.
Thanks
Peter
What I Did!
Original Setup
IP Router from internet / internal network info DMZ, where ONE server serviced
WWW, FTP, PROXY, EMAIL.
New Setup
Installed IPVS with RH Linux 6.2, gave the linux box the original IP from the
WWW box, on one lan card, and a 172.1.1.1 address on the other lan card.
Re IP addressed the WWW server to 172.1.1.2, Build a new PC with Mail server
software put on IP 172.1.1.4, built a new PC with duplicate of WWW server on IP
172.1.1.3
IPVS rules setup
VIP rr (persistence needed for ASP code session obects on IIS) to both WWW
servers
VIP:SMTP to new Mail Server
VIP:POP3 to new Mail Server
VIP to old WWW for FTP
I got both redundancy and to get the eMail server onto its own server with out
any client changes, this is brilliant as I have 600+ clients at 50+ locations,
the logistics of changing every mail client's server address is.... well we
won't think about that :-)
The one thing to remember, on top of the NT info re WINS above is that you must
redirect the three ports for netbios networking to work!! I worked this out
very early and haven't even mentioned it to you yet! You must redirect VIP to
RIP for ports 137,138 and 139. That is worth putting in the HOWTO.
----------
From: Joseph Mack
Sent: 10 May 2000 20:21
To: p.martin@xxxxxxxxxxxxxxxxxxxxx
Cc: JBailey@xxxxxxxxxx; lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: NT behind LVS
Hi Peter,
I thought I should get an NT expert onto this. If this
works ftp John a beer :-)
Whatever happens let me know so I can put it in the HOWTO
Joe
"Bailey, John" wrote:
>
> Hi Joe,
>
> I've looked in a few places for an answer to this problem.
>
> Just so I know the problem, let me restate.
>
> 1) A machine is trying to register its IP with a WINS server that sits on
> the other side of a redirector.
>
> 2) The machine tries to register it's Real IP instead of its Virtual IP.
>
> 3) A static entry on the WINS server solves the RIP registration problem
> until the machine reboots and tries to reregister with WINS. The
> registration fails because WINS has a static enty, and the network will not
> function.
>
> The trick is to tell the machine to determine its hostname/IP before
> checking/registering with the WINS.
>
> If the name resolution search order is the same at boot time versus any
> other regular name resolution request, then this should work.
>
> Keep the static WINS entry. Edit the LMHOSTS file (located in
> %WINNT%\system32\drivers\etc\lmhosts, copy the sample file - lmhosts.sam -
> if it isn't there). At the end of the file, add an entry of the form RIP
> hostname #PRE. Here is an example:
>
> 192.18.97.195 myNTNetBIOSname #PRE
>
> Load this entry into the NB cache with the command:
>
> nbtstat -R
>
> Or you can use the standard Microsoft operating procedures ( reboot ;-)
>
> The idea here is that the machine looks in a series of places for name
> resolution (Ref:
> http://support.microsoft.com/support/kb/articles/Q119/4/93.asp?LN=EN-US&SD=g
> n&FR=0 ). The NB Cache is checked before the WINS server. The LMHOSTS file
> is checked after the WINS server (this search order may be configurable in
> the Registry. Node type specification also controls order. Default for a
> WINS client is H-node, B-node for non WINS). The LMHOST entry preloads the
> NB cache with a persistent entry. You want this entry at the end of LMHOSTS
> because it only needs to be read once and normal entries will be parsed
> before when looking up IPs.
>
> This method (assuming it works) should allow you to still use WINS and keep
> the correct IP/local NetBIOS name resolution.
>
> Let me know if it does work. Thanks.
>
> John C. Bailey
> Technical Support
> Engage, Inc.
> jbailey@xxxxxxxxxx
> (919) 872 7755 x3308 Direct
> (888) 693 2237 Toll Free
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
