Just first up, I'm having a lot of trouble following your quoting. Can
you get your mail client to wrap at seventy-something characters and
just use the '> ' convention for quoting? thanks.
On Sat, 2003-02-22 at 18:00, LS wrote:
> >
> > Louis> Thanks for a detailed explanation. Ok Now as I understand I
> > Louis> install
> > XFREE86 on my Master PC running windows 2000. I am downloading cgywin
> > at the quoted url. I am letting it download all the stuff. I see that
> > Xfree86 is there as well from the install package.
>
> >ok, good.
>
> Louis> After a week I finally installed XFREE86 on my master PC Windows
> 2000.
> It just took forever to download on a dialup account.
I find that going from a local mirror makes a big difference.
>
> > Louis> I am confused here. Once Linux is installed on the slave PC.
> > Louis> What's the
> > tool I use to configure the Linux box to export displays.
>
> >good question. Google around a bit for stuff on "xdm" or "gdm" (they
> are both incarnations of the same technology). There >is also the
> possibility that you're running a third program called "kdm". Alas they
> all have different configuration
> >>mechanisms. If it's xdm (which it probably won't be), you need to edit
> a configuration file with a text editor. I think
> >there's something at www.tldp.org about it, but otherwise, googling for
> "xdmcp" or "xdm" or something will tell you what
> >you need to know.
>
> >gdm uses a program called "gdmsetup" to configure it. You need to be
> 'root' to run it (although if you're not, my system >
> >prompts for root password, yours may also). You need to go to the xdmcp
> tab and enable xdmcp, enable "honour indirect
> >requests", and if you like, fiddle with all the numbers except the port
> number (they're fairly self explanatory)
>
> Louis>
> 1. I logged in on the slave PC on the Linux OS as root;
> 2. Open an xterm, and typed gdm. [ Linux said gdm is already running.
> Aborting]
yes, that's correct. gdm is *not* gdmsetup. Log in as root and then type
'gdmsetup', not 'gdm'.
gdm is the program which actually does all the work. gdmsetup is its
configuration tool.
run "ps -ef | grep dm". It will list the details of some of the programs
running on your computer. In all probability the right most column will
tell you what display manager you're using. If it's not working after
all this stuff, tell us which dm it is and perhaps we'll know what's
wrong.
> 3. I went to the graphical windows that came up when Linux opened [this
> windows has things like "Favourites", "Preferences", "Server
> Configuration", "System Settings" etc.... ] Is this the right window you
> are talking about?
[snip]
ok, that is almost certainly the wrong program.
> I have searched from Google, and cannot see something specific that
> tells me how to run this XDCMP stuff.
really? hmm. google must be broken.
>
>
> >What distribution are you using? you might have mentioned but I've
> forgotten. Hopefully someone here can tell you what the default display
> manager (that's what the dm part is for) is and if there's an easy way
> to get to the configuration tool for it.
>
> Louis> Red hat Linux 7.2
Is it gdm, anyone?
>
> >Now, after configuring your chosen dm, you will need to restart it. You
> can do this without rebooting, but if you're new to all this, a reboot
> is probably the easiest way to do it.
>
> Louis> Can't do that as I am stuck above.
ok, well use gdmsetup and see how far you get.
> Louis> tried "Xwin -query 127.0.0.1". An X window opened like in Exceed
> but I see no Linux login as yet for the above reasons.
ok. Again, try this post-gdmsetup. 127.0.0.1 is the wrong address -
that's an address reserved for the local machine. The address you're
looking for will be 192.168.soemthing.something. probably 0.something.
> >
> > Any I have connected all PCs to the hub, and turned them all on. I am
> > in windows in both of them, what do I do to even see if I can access
> > the drives from the other PC, or test that the networking is ok ?
>
> >ping is the canonical test of network connectivity. Ping each machine
> from the other. The command you use (it's the same >
> >on windows and linux)
>
> >is:
>
> ping <IP of other computer>
>
>
> >oh, and in case you don't know what the IP is on either box, you use
> the "ipconfig" command to find out on windows, and "/sbin/ifconfig eth0"
> on Linux.
>
> Louis> I got the IP addresses. However typing the "sbin/ifconfig eth0"
> for Linux on slave PC returned something that made no sense to me.
Ok, you should read up on this stuff, but, here's the crash course. On
my machine, when I type /sbin/ifconfig eth0, this is what I get:
$ /sbin/ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:02:A5:9C:F4:FE
inet addr:192.168.9.20 Bcast:192.168.9.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3521 errors:0 dropped:0 overruns:0 frame:0
TX packets:4241 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
RX bytes:3206950 (3.0 Mb) TX bytes:332057 (324.2 Kb)
(slightly compressed to prevent line wrapping)
The line you're interested in is this one:
inet addr:192.168.9.20 Bcast:192.168.9.255 Mask:255.255.255.0
The "inet addr" is your IP address. IP == Internet Protocol. The other
bits (in case you were wondering) are an address which all computers on
the network listen to, and a specification of how large the network is
(or rather, how big it can be).
>
> From the master PC running Windows 2000, I can ping the
> "Autoconfiguration IP Address" returned from an "ipconfig" for the
> "Ethernet Adapter Local Area Connection" of the slave PC running Windows
> 2000. However I still cannot map the network drives of the slave PC
> running windows 2000 onto the master PC. Any hints on what step I am
> missing ??
umm, ok, this is something entirely different. You told me you wanted to
map network drives as a connectivity test. Ping is the right tool for
the job for connectivity tests. If you want to "map network drives" you
need to use the right tool for that job.
anyway, if you can ping in one direction I'd be amazed if you couldn't
ping in the other direction (in this configuration anyway).
In short you need to use a thing called "samba". I suspect Redhat has a
tool to configure this for you - I don't know what it is though. Just
before I go any further, if you read any document which tells you to
build samba, look it squarely in the face and say "NO I WILL NOT BUILD
SAMBA!" - install it from RPMs, you will save yourself much pain. I'm
also not sure if redhat 7.x had the version of samba that could talk to
windows 2000. It might save you some time and misery to upgrade to
redhat 8.0 before you get started with file sharing. Runing "rpm -qa |
grep -i samba" will tell you what samba stuff you have installed. Again,
there's a gui tool for this, but I don't know it. I get this output:
$ rpm -qa | grep -i samba
samba-doc-2.2.6-1.0.pre2.2mdk
samba-common-2.2.6-1.0.pre2.2mdk
samba-winbind-2.2.6-1.0.pre2.2mdk
samba-client-2.2.6-1.0.pre2.2mdk
samba-server-2.2.6-1.0.pre2.2mdk
The last one there sounds like the important one. This means you don't
need to download it from a web page. At all.
Anyway, peruse these documents for some background on samba. I'd leave
samba until you've got your X problems sorted out (for the simple reason
that you'll have any network problems solved that way), but if you're
really keen they give you some background on how it all works, which
will help once you locate your preferred configuration tool and start
setting everything up:
good overall guide:
http://www.tldp.org/HOWTO/SMB-HOWTO.html
some playstation 2 specific stuff, but has some eg config files.
http://playstation2-linux.com/download/cfyc/HOWTO_setup_samba.html
the samba home page. Documentation is here:
http://au1.samba.org/samba/samba.html
>
> From Linux machine a ping test on the "Autoconfiguration IP Address"
> returned from an "ipconfig" for the "Ethernet Adapter Local Area
> Connection" of the Master PC running Windows 2000 returned "Network is
> unreacheable".
>
> Am I using the right IP addresses here ?
umm, ok. Can you copy and paste exactly what you're doing here (in
linux, just selecting the text will copy it. Middle clicking, or
clicking both mouse buttons if you don't have a middle mouse button,
will paste). Also paste the output of /sbin/ifconfig. Did you tell your
linux box to use an "automatic IP" or something? That may not work, it
depends on how your windows computer is configured. Anyone know if
windows acts as a dhcp server if there aren't any other dhcp servers
around?
Of course all this copying and pasting is reliant on you getting the
network going, but hopefully this will get you a little closer.
I would suggest configuring your linux computer with a manual IP. If
you're on a "standard" windows network, 192.168.0.69 is a good one. Your
netmask should be 255.255.255.0, and broadcast address should be
192.168.0.255. Then you *know* what IP address to ping from windows.
Redhat will have a tool to configure this.
>
> Any comments or help on this is welcome.
>
> In the meantime I am continuing to Googling around the web, and see what
> I can find.
good luck.
James.
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
