Troubles with lan connection

Today I spent 7 hours to setup my red hat 9 to connect to another PC
with Windows XP, but without results. Only one time I succeeded but
after some minutes, it didn't work any more. Can someone tell me if
there is a document which explain how to connect to another pc with
windows installed? For the moment I only want to see the files on the
machine with windows and nothing more. I've already tried the smb-howto,
but I did'nt find it useful since the samba installed with red hat was a
little bit different, in fact some files were missing here.
Any advice? Thanks and hi all.

Luca

Luca wrote:

> Today I spent 7 hours to setup my red hat 9 to connect to another PC
> with Windows XP, but without results. Only one time I succeeded but
> after some minutes, it didn't work any more. Can someone tell me if
> there is a document which explain how to connect to another pc with
> windows installed? For the moment I only want to see the files on the
> machine with windows and nothing more. I've already tried the smb-howto,
> but I did'nt find it useful since the samba installed with red hat was a
> little bit different, in fact some files were missing here.
> Any advice? Thanks and hi all.

did you try smbclient (-L) ?

--
pozdr
adeon

Adam Dyga ha scritto:

> did you try smbclient (-L) ?

I tried smbclient //croby/c where croby is the name of the windows
computer and c is one of the units shared. The response is:

added interface ip=192.168.0.1 bcast=192.168.255.255 nmask=255.255.0.0
Connection to croby failed

192.168.0.1 is the address of this computer, that with linux red hat
installed, while the address of the windows pc is 169.254.89.124.

I've even tried to ping the address of the windows pc but the response
is this:

[luca@localhost luca]$ ping 169.254.89.124
PING 169.254.89.124 (169.254.89.124) 56(84) bytes of data.

[2]+ Stopped ping 169.254.89.124

There was no response from the windows pc.
Someone has suggested me to check if the smb service was on, and it is.
I checked it in the services window of my red hat.
What should I do.
Thanks.

Luca

Luca wrote:
>
> Adam Dyga ha scritto:
>
> > did you try smbclient (-L) ?
>
> I tried smbclient //croby/c where croby is the name of the windows
> computer and c is one of the units shared. The response is:
>
> added interface ip=192.168.0.1 bcast=192.168.255.255 nmask=255.255.0.0
> Connection to croby failed
>
> 192.168.0.1 is the address of this computer, that with linux red hat
> installed, while the address of the windows pc is 169.254.89.124.

Those addresses aren't in the same network so they won't be able to
communicate.

Put both machines in the same network and try to ping again. Until you
can get ping to work nothing will.

Regards, Ian

Luca <(E-Mail Removed)> writes:

>Adam Dyga ha scritto:

>> did you try smbclient (-L) ?

>I tried smbclient //croby/c where croby is the name of the windows
>computer and c is one of the units shared. The response is:

>added interface ip=192.168.0.1 bcast=192.168.255.255 nmask=255.255.0.0
>Connection to croby failed

Tell your SAMBA daemon that the broadcast address of the interface is
192.168.0.255. For some strange reasons, it often gets it wrong (just
like it does in your case). That's not your main problem, though.

>192.168.0.1 is the address of this computer, that with linux red hat
>installed, while the address of the windows pc is 169.254.89.124.

[...]

There's the reason. A TCP/IP network uses IP addresses from the same
range to identify networks and network routes. Since your Linux box
uses 192.168.0.1, your Windows PC's NIC must get an address from out
of the same subnet . e.g., 192.168.0.2; otherwise, there's no way for
these systems to communicate via TCP/IP.

Michael
--
Michael Buchenrieder * (E-Mail Removed) * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.

Michael Buchenrieder wrote:
>
> Luca <(E-Mail Removed)> writes:
>
> >Adam Dyga ha scritto:
>
> >> did you try smbclient (-L) ?
>
> >I tried smbclient //croby/c where croby is the name of the windows
> >computer and c is one of the units shared. The response is:
>
> >added interface ip=192.168.0.1 bcast=192.168.255.255 nmask=255.255.0.0
> >Connection to croby failed
>
> Tell your SAMBA daemon that the broadcast address of the interface is
> 192.168.0.255. For some strange reasons, it often gets it wrong (just
> like it does in your case).

That isn't necessarily wrong. It is unusual I agree to subnet 192.168 at
/16 but there's nothing invalid about it. It's horribly wasteful to take
up the whole of that particular private space with a single network, and
most things will default incorrectly, that's all.

It appears that the actual interface has a /16 netmask (255.255.0.0) and
Samba is just following that. What the OP should probably do, unless
there is a reason for this, is to change the interface itself to be /24,
which is what is normally used with the 192.168.x networks: address
192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0. The important
thing is that the netmask and broadcast should agree on all machines on
the network.

Regards, Ian

Ian Northeast <(E-Mail Removed)> writes:

>Michael Buchenrieder wrote:
>>

[...]

>> Tell your SAMBA daemon that the broadcast address of the interface is
>> 192.168.0.255. For some strange reasons, it often gets it wrong (just
>> like it does in your case).

>That isn't necessarily wrong.

Nor did I claim that. In general, though, on a typical private or
small office LAN, you won't do much subnetting of that kind.

[...]

>It appears that the actual interface has a /16 netmask (255.255.0.0) and
>Samba is just following that.

No. The SAMBA daemon simply disregards the eth0 settings and defines
a broadcast address of its own. I had to do the same on some machines,
that is, telling the daemon the correct netmask, for no obvious reasons
(no subnetting in place, and eth* interfaces correctly configured).

Michael
--
Michael Buchenrieder * (E-Mail Removed) * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.

"Luca" <(E-Mail Removed)> wrote in message
news:SXVfb.169922$(E-Mail Removed)...
> Adam Dyga ha scritto:
>
> > did you try smbclient (-L) ?
>
> I tried smbclient //croby/c where croby is the name of the windows
> computer and c is one of the units shared. The response is:
>
> added interface ip=192.168.0.1 bcast=192.168.255.255 nmask=255.255.0.0
> Connection to croby failed
>
> 192.168.0.1 is the address of this computer, that with linux red hat
> installed, while the address of the windows pc is 169.254.89.124.
>
> I've even tried to ping the address of the windows pc but the response
> is this:
>
> [luca@localhost luca]$ ping 169.254.89.124
> PING 169.254.89.124 (169.254.89.124) 56(84) bytes of data.
>
> [2]+ Stopped ping 169.254.89.124
>
> There was no response from the windows pc.
> Someone has suggested me to check if the smb service was on, and it is.
> I checked it in the services window of my red hat.
> What should I do.
> Thanks.
>
> Luca
>

As others have sia, you will need to get ping working first, either by
changing your subnet settings or to change one of the machines IP addresses.
I would recommend the latter, have both machines on the same subnet, i.e.
both start 192.168.0.
Your windows machine will need to be setup to do this - go to network
connections(control panel), and open up your Local Area Connection.
Now go to properties.
Find Internet Protocol (TCP/IP) and go to its properties. Now specify an
address there, e.g 192.168.0.2 and a subnet of 255.255.255.0 and leave the
rest (for now).
XP should take a few seconds to cahnge the settings. Once done, you should
be able to ping fine )

Ok, then you need to get the samba mount working to view the windows machine
from linux.
First, get the name of your shared drive on windows (right click on the
drive then goto sharing). You need this to get it all working. You will
need a dir on the linux machine to mount to so type (assuming mounting the
windows c drive)
mkdir /mnt/croby-c
Then in Linux, type
smbmount //croby/"windows(c)" /mnt/croby-c /-o username=XXX,password=XXX
Where XXX are replaced by your actual username and pass. Now you should be
able to go to /mnt/croby-c and view your windows files.

To make this automatic when you start the linux machine then add the
'smbmount...' line to your /etc/rc.local

HTH
Allan