Thomas Charron wrote:
>
> Quoting Matt Herbert <[EMAIL PROTECTED]>:
>
> "Programs going out eth0 to get to the internal network"..
>
> I think you'll find that if you do manage to switch them around, the same
> problem will occur. How do you have your routes setup? Eth interfaces are
> bound to an IP, and things such as netmasks determine where to send what, with
> the default route recieving packets it can't route itself. Example:
>
> eth0: IP 172.1.2.3 Netmask 255.255.255.0 default route
> eth1: IP 10.0.0.1 Netmask 255.255.255.0
>
> Anything addressed to 10.0.0.X in this will go out eth1. Anything addressed
> *ANYWHERE ELSE* will goto eth0. This is a *VERY* simplified example, and not
> all of these terms are correct, but just to give you an idea..
>
> Basically, IP info really has nothing to do with the physical device.
>
Hmmm, it's samba that's giving me a problem. He's trying to list the shares
on his windows machine and it keeps choking up this error:
Added interface ip=24.218.207.*** bcast=24.218.207.255 nmask=255.255.252.0
session request to 192.168.1.38 failed
session request to *SMBSERVER failed
Now the 24.218.* ip is the external interface, which is eth0, and 192.168.1
is his internal network (on eth1). So seeing this error I assumed (possibly
incorrectly) that smbclient was shooting out eth0, and not being able to find
192.168.1.* .... although that doesn't really make sense now that I think
about it :-/
After talking with him some more, now he's not so sure that he even has any
share's on his windows machine. I wouldn't be suprised if he doesn't even
have sharing enabled on the box, and hence that is why it's getting this
error. I have to remember to try look for the simple solutions first!
At any rate, I did switch eth0 with eth1 in his conf.modules, switched over
his ipchains stuff and the network-scripts stuff, then rebooted (with my
fingers crossed) and everything came back up with nary a problem. A nice
side effect of this is that the system now has a decent hostname instead
of his MAC address as a hostname (yuk). But, as you suggested, I still
get the error, (only with the 192.168.1.* network address in the first line)
so it is probably a mis-configuration on his windows machine.
Thanks for the help
-Matt
--
Matthew W. Herbert x75764
Spectrum Advanced Applications
http://www.aprisma.com/
mailto:[EMAIL PROTECTED]
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
