Reply With QuoteChange your IP addresses so they are all on the same subnet. Either use 10.0.0.x or 10.0.1.x for all your boxes.
Something like:
win1 = 10.0.1.3
linux eth0 = 10.0.1.1
linux eth1 = 10.0.1.2
win2 = 10.0.1.4
Jim H
ok where to start. I ve got a box running redhat linux. It has two network cards. Each card has its own ip adderss. they are eth0 - 10.0.0.1 and eth1 - 10.0.1.1.
I have put ipv4_forward to 1. Each card has 1 windows machine connected at the other end of their network, their IP's are 10.0.0.2 for the eth0 card and 10.0.1.2 for the eth1 card.
I have samba running and can access the samba server from both machines but i cannot get files off one windows machine to the other windows machine. They all have the same workgroup name.
I can see the other windows machine when looking in the workgroup directory on the windows machine but cannot acces the computer or ping it.
Can anyone help? the objective is to be able to transfer files from 1 windows machine to another windows machine through the linux box which has 2 network cards. Thanks
Its better to regret something you have done than to regret something you havent done :P
Change your IP addresses so they are all on the same subnet. Either use 10.0.0.x or 10.0.1.x for all your boxes.
Something like:
win1 = 10.0.1.3
linux eth0 = 10.0.1.1
linux eth1 = 10.0.1.2
win2 = 10.0.1.4
Jim H
Ok thanks Jim but i have tried making them the same subnet but then only 1 network card can be used ( i dont know why?). eth1 if thats any help? Any other ideas , or is this another problem? Maybe its windows or do i have to use a samba client to read the windows files? Im using Red Hat 7.2 if thats any help and also 1 windows machine runs Win XP and 1 runs Win ME. Thanks again , i'll keep messing around and post the answer if i find one., until then any help is good help
Its better to regret something you have done than to regret something you havent done :P
Hmmm, I figured that was it for sure. :'( It is kind of a strange setup the way you have it. With the ip addresses the way you had them originally what does this show on the linux box.
/sbin/route -n
Jim H
ok i tried to dig up as much info as possible for you to look at?
hope you understand it. Also 1 of the windows computers was not on at the time so the route info is missing the ip address 10.0.0.10
Also why do u say its a strange set up? Im just learning about this stuff so if you think somethings odd it probably is lol. Just tell me what you recommend.
ok heres some info
[root@Satan root]# ip address show
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:40:05:4c:77:e0 brd ff:ff:ff:ff:ff:ff
inet 10.0.1.1/24 brd 10.0.1.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:c0:6c:00:06:7f brd ff:ff:ff:ff:ff:ff
inet 10.0.0.1/24 brd 10.0.0.255 scope global eth1
[root@Satan root]# route -FC
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 * 255.255.255.0 U 0 0 0 eth1
10.0.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
Kernel IP routing cache
Source Destination Gateway Flags Metric Ref Use Iface
10.0.1.10 10.0.1.1 10.0.1.1 il 0 0 5375 lo
localhost.local localhost.local localhost.local l 0 0 23 lo
10.0.0.1 10.0.0.255 10.0.0.255 bl 0 0 1 eth1
10.0.1.1 10.0.1.10 10.0.1.10 0 0 1 eth0
10.0.1.10 10.0.1.255 10.0.1.255 ibl 0 0 0 lo
10.0.1.1 10.0.1.10 10.0.1.10 0 3 2 eth0
localhost.local localhost.local localhost.local l 0 0 11 lo
[root@Satan root]# less /proc/sys/net/ipv4/ip_forward
1
/proc/sys/net/ipv4/ip_forward (END)
<<<<<<<<<<In the smb.conf>>>>>>
Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
#my interfaces that i have configured
interfaces = 10.0.1.1 10.0.0.1
ok if that isn't making you go cross eyed prehaps you can think of something else. Is the route table ok? how do i change it if it is?
Thanks again
Its better to regret something you have done than to regret something you havent done :P
Strange in that a small network would usually be setup:Originally Posted by friskydrifter
win1 -- hub/switch -- win2
|
|
eth0
linux box
You know when you use NIC to NIC connections you need to use cross-over cables not standard cables.
This is incorrect. Look at the manpage for smb.conf at the interfaces option if you specifiy ip address it must be ip/mask. You can alternately use just the interface name, i.e. "eth0" etc... You can also use both.#my interfaces that i have configured
interfaces = 10.0.1.1 10.0.0.1
One last thing you are using class A reserved network address 10.x.x.x but you are using a class C netmask. Check an make sure the netmask is the same on all three boxes.
You might want to checkout the Linux networking Howto
http://www.tldp.org/HOWTO/Net-HOWTO/index.html
Jim H
ok i made the network cards
eth0=192.168.0.1
eth1=192.168.1.2
win 1 = 192.168.0.3 - connected to eth0
win 2 = 192.168.1.4 - connected to eth1
The subnet mask is 255.255.255.0 for both cards and the win machines.
I've set ip_forward to 1
I edited the smb.conf to hold "eth0 eth1" also the ip's with subnet mask e.g. 192.168.x.x/24 (but i dont think samba is the root of the problem yet?)
I tried making the eth1/win 2 network the same network as the eth0/win 2 network. e.g. changed all the ip's to 192.168.0.x
Im going to attempt this explanation of the topology.
WIN1----------eth0----eth1-----------WIN2
I still can't ping WIN2 from WIN1 with all the things ive described above.
I updated the initscripts still nothing? im starting to think linux cant route between two eth(x) cards.?? ???
Also this is a network made completely out of spare pieces thats why I am using two cards, because they were there. I just wanted to see if it was possible.
Thanks for your replys anyway Jim i learnt a lot from the places you recommended to visit
Its better to regret something you have done than to regret something you havent done :P
oops i forgot to put this in the previous post - I am using the right cables. And win 1 or 2 communicate with the linux box very well, just cant seem to join the networks. Frustrating i tell u!!! >lol
Its better to regret something you have done than to regret something you havent done :P
The "interfaces" option is really not needed for what you are trying to do. Samba will automatically use any broadcast capable ip addresses it finds. The "interfaces" option is used more when you have multiple NIC's installed, but don't want Samba to listen on them all.
That is definitely not the problem.im starting to think linux cant route between two eth(x) cards.?? ???
Great reason. ;DAlso this is a network made completely out of spare pieces thats why I am using two cards, because they were there. I just wanted to see if it was possible.
Have you configured the shares on your windows boxes in your smb.conf?
What does the routing table show now with both win boxes running? Use -n with any other options you use so it doesn't resolve the ip addresses.
I have never tried anything like the setup you are trying. Makes your problem interesting.
Jim H
Ok an update and a small success for me ;D
I finally got the windows machines to ping each other. Did this by making the default gateway on each windows machine the ip address of the network card they were connected to. Probably elementary but i just worked it out :
Still cant share files though.
dont know how to put a quote in here Jim but you wrote
Have you configured the shares on your windows boxes in your smb.conf?
Um i confused there , where in smb.conf? can u help me a bit more here. What do i type? is there a section that explains it, i couldnt find one? Although im a newbie and look like a llama lol
Anyway a bit more blurb for u to look at, i think this is what you meant by adding -n
[root@Satan root]# route -FCn
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
Kernel IP routing cache
Source Destination Gateway Flags Metric Ref Use Iface
192.168.0.1 192.168.1.4 192.168.1.4 il 0 0 32 lo
192.168.0.3 192.168.0.1 192.168.0.1 0 0 24 eth0
192.168.0.3 192.168.0.1 192.168.0.1 0 1 0 eth0
192.168.1.4 192.168.0.1 192.168.0.1 0 0 0 eth0
192.168.0.1 192.168.1.2 192.168.1.2 i 0 0 3 eth1
192.168.0.1 192.168.0.3 192.168.0.3 il 0 0 505 lo
192.168.1.2 192.168.0.1 192.168.0.1 i 0 0 3 eth0
127.0.0.1 127.0.0.1 127.0.0.1 l 0 0 23 lo
192.168.1.2 192.168.1.255 192.168.1.255 ibl 0 0 0 lo
192.168.0.1 192.168.0.255 192.168.0.255 ibl 0 0 3 lo
192.168.0.3 192.168.0.255 192.168.0.255 bl 0 0 23 eth0
192.168.1.4 192.168.1.255 192.168.1.255 bl 0 0 23 eth1
127.0.0.1 127.0.0.1 127.0.0.1 l 0 0 11 lo
Well we are getting there i guess. Anymore ideas?
Cheers - Friskydrifter
Its better to regret something you have done than to regret something you havent done :P
Posting Permissions
Bookmarks