|
Peter Martin wrote:
>
> 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.
can you export the files from the fileserver with samba?
> > 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.
hmm. I don't know enough about NT to help here I'm sorry.
> 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
OK. make the network standard tcpip and have the users connect that way and
chuck the netbios stuff
> 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!
remember that tcpip was not a part of MS's plan, since Bill didn't see any point
in the
internet. The tcpip layer (socks) was written by other people as an add-on. As
well
Bill doesn't want to be compatible with anyone else.
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
|
