yeah like no attention has been paid to the windows box yet. What is its ip details? (I cannot remember what version of windows he is running, and the method of finding out varies)
On Thu, 19 Feb 2004 12:07:48 +1300 Matthew Gregan <[EMAIL PROTECTED]> wrote:
On Thu, Feb 19, 2004 at 12:01:05PM +1300, Patrick Dunford wrote:
rtl8139.c:v1.07 5/6/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.htmlOkay, that proves that the driver is initialising your card correctly.
eth0: RealTek RTL8139 Fast Ethernet at 0xfc00, IRQ 10, 00:05:1c:19:df:f4.
So maybe I should try the newer version that I have compiled. How do IThere's no need--from the information you've provided on the list, it
configure Linux to load a different driver?
appears your connectivity problem lies elsewhere.
someone, somewhere mentioned a firewall - in this case zonealarm
Just to prove zonealarm wasn't the problem I killed it but could still not ping.
[ZA is responsible for 99% of these situations as I found out when I had Apache installed on my home machine]
So I got a 2nd windows box going (Oh so much fun installing some of those early Pnp Ne2000 compat cards under early Windows Pnp versions) and configured it. It soon became clear that ZA was blocking ping packets. ZA was configured to exclude the network cards in each machine from being blocked and then pings and network browsing between the two Windows machines started working.
This is not something I was aware of before, as I always used Netbeui between Windows machines and ZA presumably doesn't bother itself with Netbeui.
I then plugged the main Windows box back into the Linux box,. and behold, both of them can ping each other.
Still can't browse anything on the Linux server but I assume that is a Samba issue and my friendlt local Samba man will know.
I can browse the web server on the Linux box fine so it looks like there was never anything wrong with the Linux box at all. And ZA can still block traffic even while it is not running.
Thanks all for your assistance.
