Re: [newbie] repost : lan problems
it has to be a configuration failure somewhere, i just switched the lan card on the linux box and it still doesnt work. has anybody suggestions on common conf. mistakes in win2000 and linux ? --quay
RE: [newbie] repost : lan problems
At 17:29 04.03.2001 -0500, you wrote: Go back to basics... With your lan card you should have gotten a utility disk. On that disk are two important programs (assuming that you are using a 10base2/10baseT card). The first program sets up the hardware on the lan card. It allocates IRQ's/IO, etc and permits you to test the settings. Built into the same program or separate from it is another utility which permits you to set up once machine as a MASTER and the other as a SLAVE for testing purposes. Hopefully both lan cards are identical. Connect everything up. Boot up from a dos disk and use the LAN CARD's utility disk. Check the settings for conflicts. There is a self test in there too. Run it and make sure it passes. Make sure that both cards are set to 10base2, NOT 10BaseT. yes they are both set to use 10base2.i already used the config utils.-... Finally use the Diagnostic utility to send packets back and forth from the two machines. Does this work? If not you have a hardware problem. If it works you have a configuration/software problem. -JMS hmm.unfortunately the 2 cards are not identical, but i have the config utility for both, so i will try what u suggested. btw. my cabling is ok, i checked the cable and the connectors/resistors today with another network and it worked pretty fine. --quay
Re: [newbie] repost : lan problems
ya ur ip... have to be different -DukeMaN --- Antonio De Luna [EMAIL PROTECTED] wrote: I think the probles is that you're using the same ip on both machines. Quaylar wrote: hi all ! i´m reposting because i still have my win-linux lan problem. let me describe: i have 1 win2k box and 1 mandrake box. win2k : 1) surecom ep325 configured to utilize BNC port 2) no resource conflicts 3) LAN connection is up with 192.168.0.1/24 4) firewall is down mandrake box: 1) 3com 3c509 : initialized - no resource conflicts - modules are loaded - using BNC port 2) eth0 is up with 192.168.0.1/24 3) routes are set properly by linux 4) ipchains is down the 2 boxes are connected via thin ethernet coax, cable lenght approx. 10m, terminated at each end. wiring and terminators are known to be ok, because switching them for new ones didnt solve my problem. problem : ping timeouts from win - linux and vice versa...100% packet loss plz, i would appreciate any advice, this is driving me crazy... --quay -- -Quaylar- Icq# 30932448 [EMAIL PROTECTED] ! Knowledge is power For confidental email plz encrypt with PGP __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Re: [newbie] repost : lan problems
to all accidentally reading this : the ips ARE DIFFERENT it was just a mistype ;) --quay
RE: [newbie] repost : lan problems
jose, today i tested my wiring : over the 15m BNC cable (with both T and resistors connected) i have 9 ohm resistance. T-conns are ok. resistors have 58 ohm. are this values ok ? --quay
RE: [newbie] repost : lan problems
Go back to basics... With your lan card you should have gotten a utility disk. On that disk are two important programs (assuming that you are using a 10base2/10baseT card). The first program sets up the hardware on the lan card. It allocates IRQ's/IO, etc and permits you to test the settings. Built into the same program or separate from it is another utility which permits you to set up once machine as a MASTER and the other as a SLAVE for testing purposes. Hopefully both lan cards are identical. Connect everything up. Boot up from a dos disk and use the LAN CARD's utility disk. Check the settings for conflicts. There is a self test in there too. Run it and make sure it passes. Make sure that both cards are set to 10base2, NOT 10BaseT. Finally use the Diagnostic utility to send packets back and forth from the two machines. Does this work? If not you have a hardware problem. If it works you have a configuration/software problem. -JMS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Quaylar Sent: Sunday, March 04, 2001 3:49 PM To: [EMAIL PROTECTED] Subject: RE: [newbie] repost : lan problems heres a weird thing i noticed just a few minutes ago: i checked the eth interfaces in both linux and win. under linux "ifconfig eth0" showed up "packets sent : xxx" whereas xxx increased when i tried to ping the win machine. so i know for sure that icmp packets from the linux box to the windows box pass the eth interface. then i had a look in win, rightclick on lan connection and saw : status of LAN connection : 0 packets sent 0 packets received i did a ping from the windos machine to the linux machine and looked again at the status window: status of LAN connection : 0 packets sent 0 packets received so it seems that there are absolutely no packets leaving the win machine over the ethernet card. i wonder where they are going.could this be a routing problem ?. i dont understand this, i set all the ip information in the properties of my LAN connection. any ideas ? --quay
RE: [newbie] repost : lan problems
I hope that your ethernet addresses were a mistype... You have both machines with the same address according to your message, which of course will not work! -JMS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Quaylar Sent: Saturday, March 03, 2001 4:45 PM To: [EMAIL PROTECTED] Subject: [newbie] repost : lan problems hi all ! im reposting because i still have my win-linux lan problem. let me describe: i have 1 win2k box and 1 mandrake box. win2k : 1) surecom ep325 configured to utilize BNC port 2) no resource conflicts 3) LAN connection is up with 192.168.0.1/24 4) firewall is down mandrake box: 1) 3com 3c509 : initialized - no resource conflicts - modules are loaded - using BNC port 2) eth0 is up with 192.168.0.1/24 3) routes are set properly by linux 4) ipchains is down the 2 boxes are connected via thin ethernet coax, cable lenght approx. 10m, terminated at each end. wiring and terminators are known to be ok, because switching them for new ones didnt solve my problem. problem : ping timeouts from win - linux and vice versa...100% packet loss plz, i would appreciate any advice, this is driving me crazy... --quay -- -Quaylar- Icq# 30932448 [EMAIL PROTECTED] ! Knowledge is power For confidental email plz encrypt with PGP
RE: [newbie] repost : lan problems
At 17:45 03.03.2001 -0500, you wrote: I hope that your ethernet addresses were a mistype... You have both machines with the same address according to your message, which of course will not work! -JMS hi jose, yes u are right, it was a mistype. i would have noticed such a dumb failure because i checked all settings approx. 100 times. of course linux box is at 192.168.0.1/24 and win box is at 192.168.0.2/24 u know, after your last reply i posted that my lan was working. i dont know why it did, but just a few days ago i tidied up all the cables under my desk and among others i unplugged the BNC cable at both ends. i plugged then in again, installed a 2nd nic in my linux box to connect it to my new adsl modem, and when i rebooted my local lan was (again) gone. i think its the same problem as it was before (still i dont know), it cant be the 2nd nic because its recognized correctly, routes are ok and i already established a adsl conn over it. so whatever it is.slowly i am beginning to think it should be in "x-files".:) --quay
RE: [newbie] repost : lan problems
Well, I'm guessing that you need Samba running. Regards Daryl -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Quaylar Sent: 03 March 2001 21:45 To: [EMAIL PROTECTED] Subject: [newbie] repost : lan problems hi all ! im reposting because i still have my win-linux lan problem. let me describe: i have 1 win2k box and 1 mandrake box. win2k : 1) surecom ep325 configured to utilize BNC port 2) no resource conflicts 3) LAN connection is up with 192.168.0.1/24 4) firewall is down mandrake box: 1) 3com 3c509 : initialized - no resource conflicts - modules are loaded - using BNC port 2) eth0 is up with 192.168.0.1/24 3) routes are set properly by linux 4) ipchains is down the 2 boxes are connected via thin ethernet coax, cable lenght approx. 10m, terminated at each end. wiring and terminators are known to be ok, because switching them for new ones didnt solve my problem. problem : ping timeouts from win - linux and vice versa...100% packet loss plz, i would appreciate any advice, this is driving me crazy... --quay -- -Quaylar- Icq# 30932448 [EMAIL PROTECTED] ! Knowledge is power For confidental email plz encrypt with PGP
RE: [newbie] repost : lan problems
Thinnet networks are subject to something akin to "standing waves". The signal "bounces" off of one end of the cable and back. This results in an "echo" which is 180 degrees out of phaze with the next incoming wave... The two cancel out and you end up with a dead spot on the cable, where if you plug something in, you get no response. The Ethernet terminators are there to reduce or eliminate this, which is why they are at the physical "ends" of the cable. They are not always successful. You may be seeing the same. You may have a bad "T" connector as well. I've seen more bad "T" connectors than one would expect. Check your lan cables. Make sure that the center pin is not being pushed into the socket when you plug it into the Ethernet card or T connector. This will also cause problems. The center pin must not move so it can penetrate the receptacle. Since your LAN setup worked for awhile look for a physical problem of some sort. -JMS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Quaylar Sent: Saturday, March 03, 2001 6:37 PM To: [EMAIL PROTECTED] Subject: RE: [newbie] repost : lan problems At 17:45 03.03.2001 -0500, you wrote: I hope that your ethernet addresses were a mistype... You have both machines with the same address according to your message, which of course will not work! -JMS hi jose, yes u are right, it was a mistype. i would have noticed such a dumb failure because i checked all settings approx. 100 times. of course linux box is at 192.168.0.1/24 and win box is at 192.168.0.2/24 u know, after your last reply i posted that my lan was working. i dont know why it did, but just a few days ago i tidied up all the cables under my desk and among others i unplugged the BNC cable at both ends. i plugged then in again, installed a 2nd nic in my linux box to connect it to my new adsl modem, and when i rebooted my local lan was (again) gone. i think its the same problem as it was before (still i dont know), it cant be the 2nd nic because its recognized correctly, routes are ok and i already established a adsl conn over it. so whatever it is.slowly i am beginning to think it should be in "x-files".:) --quay
RE: [newbie] repost : lan problems
At 19:48 03.03.2001 -0500, you wrote: Thinnet networks are subject to something akin to "standing waves". The signal "bounces" off of one end of the cable and back. This results in an "echo" which is 180 degrees out of phaze with the next incoming wave... The two cancel out and you end up with a dead spot on the cable, where if you plug something in, you get no response. The Ethernet terminators are there to reduce or eliminate this, which is why they are at the physical "ends" of the cable. They are not always successful. You may be seeing the same. i switched terminators to no avail. You may have a bad "T" connector as well. I've seen more bad "T" connectors than one would expect. Check your lan cables. Make sure that the center pin is not being pushed into the socket when you plug it into the Ethernet card or T connector. ah...i checked the lan cables and indeed 1 of the 2 center pins was pushed into the socket. i pulled it out to make sure it hits the receptacle. and i noticed that the center pins of the 2 T connectors i was using, were not as long as the center pins in 2 other T-connectors. so i switched them too. but it still doesnt work. This will also cause problems. The center pin must not move so it can penetrate the receptacle. Since your LAN setup worked for awhile look for a physical problem of some sort. mhm...i too think it has to be something physical, i tink i will buy a new cable/connectors/resistors... maybe it helps. thx.. --quay -JMS
