networking 2 computers with sx adapters, fiberoptics cables

[hilophilo]

here is a base summary of my network so far:
6 systems networked connecting to a switch then to a dhcp server. all systems are fine working on the internet sharring whatever. I just got myself 2 1000Base-SX Adapters. I just want to network 2 systems on the network together taking advantage of the 1000bae-se adapter speed. Do I cross over the fiber optics cables like the rj-45's when connection 2 system directly? and how would I set the network up. right now my dhcp server is taking care of the ips on my network. when installing the 1000base adapter on my linux system, it ask me to put in ip and and all that stuff. what do i fill in? for windows too.. what ip do i fill in? thanks.

[neondog]

first look at the DHCP server to check the range of ip addresses it assigns because you don't want to duplicate those on the new nics. Next you will want to assign static ip addresses to the new NIC's via the neat program in Linux if you want to use a GUI.

As far as whether you'll need a cross-over cable its probably a good idea but I would bet those nics are auto-sensing so it might not matter. Check the specs on the cards.

[hilophilo]

all im tryin to do now is connecting 2 computers using fiber optics cables. i have 2 network 1000base cards. can i do this ? do i have to cross over the cables? very frustrated!!! please help!

[neondog]

plug them in and try it. See my post above.

[hilophilo]

if i pull the 2 computers out of my network and connect the 2 directly together it works fine.. but when using two network cards, how would i set up doing that. for example i want eth0 to connect to internet and my network. but i want eth1 to connect to my server directly using the 1000base because those 2 systems have 1000base cards. i heard somewhere i have to using route. any tips? thanks again

[jumpedintothefire]

Discribe the numbering of the ip addresses that you are using for the machines that have the 2 cards...
the output of route -n and ifconfig from both would be very helpful for me.

[hilophilo]

Linux Machine

eth0 Link encap:Ethernet HWaddr 00:04:5A:64:96:D8
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3452 (3.3 Kb) TX bytes:3325 (3.2 Kb)
Interrupt:11 Base address:0x3000

eth1 Link encap:Ethernet HWaddr 00:60:CF:20:1D:DD
inet addr:192.168.1.109 Bcast:192.168.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:572657 errors:0 dropped:0 overruns:0 frame:0
TX packets:1078160 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:34261404 (32.6 Mb) TX bytes:1581495065 (1508.2 Mb)
Interrupt:10

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:316 errors:0 dropped:0 overruns:0 frame:0
TX packets:316 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:28242 (27.5 Kb) TX bytes:28242 (27.5 Kb)

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 eth0
192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.109 0.0.0.0 UG 0 0 0 eth1


WindowsXP Machine

Windows machine is kinda similar with

eth0 - ip:192.168.1.101 mask:255.255.255.0 gateway:192.168.1.1 dhcp server
192.168.1.1

eth1 - ip:192.168.1.108 mask:255.255.0.0

both machines are already hooked up to a dhcp server throught eth0. i just wanted to use the eth1 to transfer data on both machines because of the 1000base card. any more info you need. please ask. thanks

[jumpedintothefire]

The main problem is that 192.168.0.0 overlaps with 192.168.1.0 and the route with the narrower subnet gets used...

Reset the default gateway to 192.168.1.1

It would be just easier to just use a 255.255.255.0 subnetmask for the second nic on both machines...

OR

On the linux box:
route add -host 192.168.1.108 dev eth1

On the Windows box:
route add 192.168.1.109 mask 255.255.255.255 192.168.0.108

Either way, edit the host file on both machines so that the names of each other are on the 192.168.1.x ip. When the name lookup occurs it will resolve to ip with the fast nic....

Hope it helps...

[hilophilo]

i tried those things but it doesnt seem to work correctly. maybe im odin something wrong. whatever nic cards loads up first or the primary one.. it uses that one and ignores the secondary one. can you explain a little more detail about the host on the two machines? thanks

[jumpedintothefire]

Sorry this was a mistype:

route add 192.168.1.109 mask 255.255.255.255 192.168.0.108

S/B

route add 192.168.1.109 mask 255.255.255.255 192.168.1.108

What doesn't work correctly??
Can you ping the second interface's ip??

Post the output of route -n from both machines, both need to be correct, or no traffic will flow...

------
EDIT:
.:eek: ~~~brainwave

Two interfaces, same network:
Been down this before....

http://linuxnewbie.org/forum/showthread.php?s=&threadid=82190
------

You could change the ips on the second cards to something like 192.168.2.1 and 192.168.2.2 using a 255.255.255.0 subnetmask...... Then use 192.168.2.x in the hosts file...

When you ping, traceroute, or otherwise access a machine by name, the first thing that is done is a dns lookup of the name to get the ip to connect to. The dns lookup can use a dns server and/or the hosts file. Placing the ip/name combo in the hosts *should* result in the resolver giving the ip that is in the hosts file for that name... That would depend on the setting in the nsswitch.conf file for "hosts:", the order should be: files dns, to use the hosts file first. Windows should check the hosts file first by default..

[hilophilo]

so far. i have this situation. i can now access eachother with the eth1 card. but now.. the eth0 card does not seem to connect. i cant connect to internet anymore and cant browse the other systems on my network.

LInux system:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.1.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
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

eth0 Link encap:Ethernet HWaddr 00:04:5A:64:96:D8
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:92 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:12874 (12.5 Kb) TX bytes:5853 (5.7 Kb)
Interrupt:11 Base address:0x6000

eth1 Link encap:Ethernet HWaddr 00:60:CF:20:1D:DD
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:8356 (8.1 Kb)
Interrupt:10

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:700 (700.0 b) TX bytes:700 (700.0 b)

Windows:

================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 20 78 08 63 8d ...... Linksys NC100 Fast Ethernet Adapter - Packet Sch
eduler Miniport
0x10004 ...00 60 cf 20 48 34 ...... 3Com Gigabit Ethernet Server NIC (SX/TX) - P
acket Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.2.2 50
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.102 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.102 192.168.1.102 20
192.168.1.102 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.102 192.168.1.102 20
192.168.2.0 255.255.255.0 192.168.2.2 192.168.2.2 50
192.168.2.2 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.2.255 255.255.255.255 192.168.2.2 192.168.2.2 50
224.0.0.0 240.0.0.0 192.168.1.102 192.168.1.102 20
224.0.0.0 240.0.0.0 192.168.2.2 192.168.2.2 50
255.255.255.255 255.255.255.255 192.168.1.102 192.168.1.102 1
255.255.255.255 255.255.255.255 192.168.2.2 192.168.2.2 1
Default Gateway: 192.168.1.1
================================================== =========================
Persistent Routes:
None

can you explain more on how to edit the host files? both windows and linux. kinda confused. do i use the same netmask for both network cards eth0 and eth1 on both machines and both gateways 192.168.1.1?

[jumpedintothefire]

The subnetmasks and default gateway should be fine...

Just to check....
What are the names of the machines??
Then we'll deal with the hosts files...

From linux you can ping 192.168.1.102, 192.168.1.1, 192.168.2.2 ?? how about a internet ip?? internet name??

Can you ping by name?? which ip does the pinging? ie: PING 192.168..2.2 (192.168..2.2) from <ipused>
it the from that I need to know.....


From windows you can ping 192.168.1.1, 192.168.1.101, 192.168.2.1? how about a internet ip?? internet name.??

Just to keep my head clear....

[hilophilo]

if you mean by computer name.. windows computer name is : windowz
linux hostname is: linux.linuz.com .... is that what you mean?

i did the pinging from linux. i can ping all those numbers 192.168.1.102, 192.168.1.1, 192.168.2.2, internet name and ip is fine. when i ping 192.168.2.2 from my linux, it uses the ip of 192.168.1.100

from windows pinging seems to work fine for 192.168.1.101, 192.168.1.1, 192.168.2.1. BUT, now i cant ping the internet name.

[jumpedintothefire]

OK small steps...
what does cat /etc/resolv.conf give you??
Where is the windows machine looking for DNS??

edit /etc/hosts adding:
192.168.2.2 windowz

edit c:\windows\system32\drivers\etc\hosts adding
192.168.2.1 linux

now ping by just those names, which ip are they using??

Which and whos internet name??

[hilophilo]

cat /etc/resolv.conf gives me this.. my dhcp server

; generated by /sbin/dhclient-script
search SBC
nameserver 213.xxx.xxx.xxx
nameserver 243.xxx.xxx.xxx

i think windows is looking for dns from dhcp server too.

on my windows machine when i ping : windowz it says
Pinging windowz 192.168.2.2 and it seems fine
when i ping linux it says replay from 192.168.2.1 and it seems fine as well.

i try the same thing on my linux machine but i cant ping linux, but i can ping windowz.

[jumpedintothefire]

Your using a dns server that know nothing about your private network....

add to /etc/hosts
192.168.2.1 linux

now open a connetion from windows to linux (webpage samba, whatever) and do a netstat -na on both machines.... should be using ports that are on the 192.168.2.x ip addresses..

Internet still work from both machines??
Is every OK now??

[hilophilo]

everything seems to work fine expect one thing. windows machine cannot access the net, but can access the systems on the network and the linux machine.

the linux machine can access everything.

[jumpedintothefire]

do a tracert from windows to www.yahoo.com and post the output.

[hilophilo]

it seems when tryin to reach the internet it uses eth1. but, when accessing the network, it uses eth0.

i did the trace on windows and it says "unable to resolve target system name www.yahoo.com"

when i try to disable my eth1 card on windows, the internet seems to work fine again using the eth0 card and can also access my network using the eth0 card.

[jumpedintothefire]

go into the advanced properties for the fiber card and remove the gateway...

[hilophilo]

removing the gatewate made my eth0 card access the net now, which is good. i can now access my network but it seems to be a conflict between the two nics (eth0 and eth1). it uses both cards to access my linux machine, and it freezes in the middle when i try to drag a file across from the linux to the windows and vise versa.

[jumpedintothefire]

what does netstat -na show??

[hilophilo]

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1037 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1242 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1243 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1244 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1245 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1246 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1248 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5000 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1030 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1030 127.0.0.1:1178 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1180 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1184 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1186 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1187 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1191 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1192 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1195 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1198 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1203 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1204 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1209 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1211 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1213 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1215 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1217 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1218 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1220 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1223 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1225 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1233 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1237 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1240 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:1242 ESTABLISHED
TCP 127.0.0.1:1030 127.0.0.1:1244 ESTABLISHED
TCP 127.0.0.1:1030 127.0.0.1:1246 FIN_WAIT_2
TCP 127.0.0.1:1030 127.0.0.1:1248 FIN_WAIT_2
TCP 127.0.0.1:1030 127.0.0.1:1250 TIME_WAIT
TCP 127.0.0.1:1031 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1179 127.0.0.1:1030 TIME_WAIT
TCP 127.0.0.1:1232 127.0.0.1:1231 TIME_WAIT
TCP 127.0.0.1:1242 127.0.0.1:1030 ESTABLISHED
TCP 127.0.0.1:1244 127.0.0.1:1030 ESTABLISHED
TCP 127.0.0.1:1246 127.0.0.1:1030 CLOSE_WAIT
TCP 127.0.0.1:1248 127.0.0.1:1030 CLOSE_WAIT
TCP 192.168.1.102:139 0.0.0.0:0 LISTENING
TCP 192.168.1.102:1029 0.0.0.0:0 LISTENING
TCP 192.168.1.102:1029 192.168.1.100:139 ESTABLISHED
TCP 192.168.1.102:1169 195.90.87.201:80 TIME_WAIT
TCP 192.168.1.102:1171 63.240.15.154:80 TIME_WAIT
TCP 192.168.1.102:1228 203.127.132.36:80 TIME_WAIT
TCP 192.168.1.102:1230 203.127.132.36:80 TIME_WAIT
TCP 192.168.1.102:1243 63.240.15.145:80 ESTABLISHED
TCP 192.168.1.102:1245 63.240.15.138:80 ESTABLISHED
TCP 192.168.2.2:139 0.0.0.0:0 LISTENING
UDP 0.0.0.0:135 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1032 *:*
UDP 0.0.0.0:1041 *:*
UDP 0.0.0.0:1085 *:*
UDP 0.0.0.0:1107 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1038 *:*
UDP 127.0.0.1:1059 *:*
UDP 127.0.0.1:1140 *:*
UDP 127.0.0.1:1165 *:*
UDP 127.0.0.1:1239 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.102:123 *:*
UDP 192.168.1.102:137 *:*
UDP 192.168.1.102:138 *:*
UDP 192.168.1.102:1900 *:*
UDP 192.168.2.2:123 *:*
UDP 192.168.2.2:137 *:*
UDP 192.168.2.2:138 *:*
UDP 192.168.2.2:1900 *:*

[jumpedintothefire]

need to force samba and windows to use the 192.168.2.0 network...

on windows edit the c:\windows\system32\drivers\etc\lmhosts file ( you may have to create it )
use the same ipaddress from the hosts file..

Make sure the allow lmhost lookup is checked under the wins tab.

on linux edit /etc/samba/lmhosts, use the same ipaddresses from the hosts file..

edit /etc/samba/smb.conf

name resolve order = lmhosts host bcast wins

make sure the hosts allow has the 192.168.2.x address in it.

restart samba

retest...

[hilophilo]

ok. it seems to be working kind of now. thanks :] some littles things though. sometimes when i transfer data accross the two gigabit nics, it stops sometimes like its not responding, and sometimes freezes saying network connection was not found. But also, sometimes it works fine when i transer data accross the network. when i use both nic the same times trasfering data, it laggs also. seems like its not stable when i was using my network with 1 card before? is this normal?

How fast is it normally to transfer say.. around 700mb of data accross a 10mbps network, 100mbps network, 1000mbps network?

just checked it couples times again, and it stop resonding when i transfer data accross, but it does use the eth1 card though.

[jumpedintothefire]

Are either of your 2 nic sharing an interrupt??
Flackey drivers??.... XP??.... NAH... :p
You have the benefit of being able to play with 1000 meg card...

EDIT:
Just a thought....
Maybe the harddrives can't keep up with the network ...

[hilophilo]

i was reading about 1000 nic on personal systems and i think you are right abotu hardware not keeping up with the network. the hardrives that I use are too slow to take full advantage of the 1000nic cards.

the nics are using the same irq 10. i dont know why windows xp wont let me change it. i remember using NT and it wasnit a problem. is there anyway i can change it on winxp?

i was thinkin about the winxp drivers too. im looking for some hopefully updated ones.

if i take the eth0 out my windows system and just use the eth1 card connect directly to my linux syste. can i use that to go online? does that mean i need dhcp install on my linux?

[jumpedintothefire]

You would need to add the linux box as the gateway on the windows box, then add some forwarding rules in iptables. It's not that hard. Do you need the other boxes on the lan to access this one??

[hilophilo]

i seem to got it workin. the speed seems to be same as 100bit cards. i was checkin out my gigabit card it uses 64bit. my pci on my mb is only 32bit. could that a problem with speed? i also heard windows cant handle the speed as well. anyways thanks for help jumpintothefire.