|
Hi Joe,
----------
From: Joseph Mack
Sent: 09 May 2000 19:20
To: Peter Martin
Cc: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: NT behind LVS
let's see how I'm doing...
you've got a directory on one computer (fileserver) which is not part of the
LVS, mounted under the DOCUMENTROOT of another computer (a webserver).
These webservers is behind an LVS director and you can access all the stuff
under the webserver's DOCUMENTROOT except for the directory coming from the
fileserver. You can't mount the files from the fileserver to the webserver
because of a problem with netbios/RIP/VIP/WINS that I don't understand yet.
A part of the problem is that you can't export the files from the
fileserver to the VIP because the VIP is running on a linux
box which doesn't talk netbios.
> the RIP from the real server didn't match with the Static Mapping of the ip
> address I inserted for real server on the WINS server, the Netbios names
> being unique the real server shut down the network.
>
tell me more about this. Why can't you tell the WINS box the name/IP of the
realserver and the fileserver and let them sort it out?
The WINS system is similar to DNS, but, AFAIK is empty when first started as a
service, and then each PC which powers on register's itself with the database
entering both it's unique netbios name and IP address, you can enter static
mappings, but, if the PC then reboot's when it goes to WINS to register itself
and finds that the netbios name exists on a different IP address to the one its
trying register it shuts down the network. I could remove the WINS address
from the real server so it doesn't attempt to register with WINS, but as I said
earlier this means that the real server canot then do lookup's for netbios
names to find the other file/sql servers it requires to provide the web service.
It's catch22, the only solution I can think of at press it to setup a DNS
server and use this to resolve any IP's from the real web server to the
file/sql servers, and enter a static mapping on the WINS server so the traffic
from the internal network can then resolve the correct IP and map the drives
>
> >and stuff on the IIS web servers, and give the development team access to
> >the shared disc space, but it seems you can't do a read from and not write
> >to solution, it all or nothing!
I don't understand the relevence of this yet.
I didn't explain this very well did I :) I hope the above is more
understandable!
> What is the service(s) that you are LVS'ing?
>
> Basically I have two 'real' web servers and a 'real' mail server sat behind
> the LVS,
got it
Having multiple OS's in the shop is a real pain :-)
Windows is so inflexable in terms of networking, the TCP/WAN section is a real
afterthought!
Joe
--
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
|
