: Okay to answer you other quiry first no crossover cable am jacked into a
: 5 port hub with a standard cat5 patch cord.
: The box <win98> I'm trying to connect to is assigned an ip address of
: 126.96.36.199 and a subnet of 255.255.255.0. The box Im trying to connect
: from<linux> is assigned an ip adress of 188.8.131.52 and a subnet of
: 255.255.255.0. I have the gateway configged to 184.108.40.206, and the dns
: function set to the ip of my dial up account, but without even going
: into the routing and gateway Im unable to ping the ip addy of the win98
: box Ive been lead to believe all the info I have read in the online doc.
: Ive found that once the host <liux box> has been configged a ping via
: the network to the ip addy of the win98 box should be possible??
: I have enabled the eth0 and have the correct module choosen for the
: driver, irq, i/o.
: Does this sound correct as far as the setup should be, Im a total newbie
: to Linux and am what I would consider an "advanced lamer"
This sounds similar to how my LAN is setup, and seems correct. I use
192.168.*.* or 10.*.*.* address as I am familiar with those being in
the set of reserved IP's commonly used for lans (there are a couple
more sets that I don't remember without looking up.). If everything
is correct if sounds like the ping should work. Some things that I have
heard could cause problems that could be easily overlooked are: Are
both the network cards able to work at the same speed, ie. not trying to
use a 10mbs and 100mbs card. Another problem I heard someone mention
was using a 100 mbs nic on a 10mbs hub. Again, these problems were
word of mouth. My switch/hub requires all the boxes to hook up with
regular patch cable, but my cable modem required a cross over, that is
why I had asked about the cable you used also.
Make sure that the TCP/IP is setup and bound to the NIC on the win98
box. I have seen windows networking do weird things, especially is
an AOL dialup account is installed on the system (I had to do a total
wipe of the interfaces and binding in win98 and start over). Under
network setting in win98, under the Advanced TAb in the TCP/IP menu
item for your network card, try setting the "use this as the default
protocol" option and see if that affects anything.
You might try a different set of IP ranges, again I only remember the
two sets I mentioned above, the set you use might be in the reserved
set, but they dont seem to come to ming, try the 192.168.*.* set, I
know they are fine.
I'm not overly experienced with networking, but maybe some of this could
help. If I'm wrong about any of it I'm sure someone would poing it out.
I use 3c509 cards and D-Link 530TX+ cards in my network and Redhat 6.2
detected both brands trouble free out of the box. You might switch the
cards out and see how it goes if all else fails.
: I have encountered a new problem with Turbolinux as the dektop seems to
: be totally unstable and wants to "melt" and the distro I have lacks much
: doc. and I have reloaded a prior version on madrakes 7.0 complete
: distro, unfortunatly it doesnt seem to want to load the module for the
: drivers<I used your tip for lsmod and it appears that 8309 loads but
: ne2k-pci does not> ~sigh~ Ive followed the instructions on mandrakes
: site to a "T" as to how to setup the NIC and the address's etc.....Im
: thinking driver problems??<SMC was only supposed to send me the most
: current driver info 3 days ago time to call again>
: **(side note to anyone folowing this and intrested)
: totally user friendly for the new user.