On Wed, 2004-07-21 at 08:25, Lule George William wrote: > Tried it with a straight through, crossover and also a rollover(don't > laugh at this last one, I didn't :-) > I am trying everything to be sure) and it still > behaves the same.
Maintain the crossed cable between the router and your PC. What is your network setup like [what's connected to what and how]? if possible do a small ascii diagram. > When I reboot the machine, the LED on the router then goes on but on > pinging, I still get the same response. > Seeing this I put a switch in between the two. The switch sees both the > router and the NIC fine but on ping, this time I got no response > instead of the other network unreachable error. >From where are you pinging and what are you pinging? Can the Suse box ping both its own interfaces? Can the Suse box ping the router? vice-versa? > In this state, I > accidentally left the ping command running and went to check out on > someone and the router replied to only two pings out of 1002 ping(don't > ask me the percentage it calculated. Its embarrasing), but that is the > situation right now. What is the router saying? [the logs] > > > On Wednesday 21 July 2004 04:43, Lule George William wrote: > > <snip> > > > SuSEfirewall2 a million times but still no luck. I have disabled <Snip> > --------------------------------------------- > This service is hosted on the Infocom network > http://www.infocom.co.ug -- Ezra Banoba Network Engineer one2net www.one2net.co.ug "Doing well is a result of Doing good. That's what capitalism is all about." --------------------------------------------- This service is hosted on the Infocom network http://www.infocom.co.ug
