Um - yeah. Your problem is that you can't see 192.168.0.1 from .2, and/or vice-versa; 
not gateway problems. Sorry for misleading you! 

And the resolv.conf file - "man resolver" says that a line starting with "nameserver" 
should give the ip address immediately after it - so if the nameserver you want to use 
is x.x.x.x, put "nameserver x.x.x.x" on that line, or enter x.x.x.x in linuxconf.

But - that probably still isn't what's keeping you from seeing the other machine. 
Since you are seeing both eth0 and lo in ifconfig, the driver for your card must be 
loaded OK (did it display ip addresses with both eth0 and lo?). 

You can ping 127.0.0.1 from the linux box? 
You can ping 127.0.0.1 from the windows box? 
You can ping 192.168.0.1 from the windows box? 
You can ping 192.168.0.2 from the linux box? 

-Dusty

>>> [EMAIL PROTECTED] 08/24/00 01:37PM >>>
I guess I hadn't saved the default gateway setting in 
linuxconf.  Regardless, that wasn't the problem.  I changed it and it 
didn't help...  :(

Here's my route output:

Destination     Gateway      Genmask                Fl    Met  Ref  Use  Iface
192.168.0.2    #                   255.255.255.255   UH  0     0       0 
     eth0
92.168.0.0    #                   255.255.255.0        U     0     0 
0        eth0
127.0.0.0         #                   255.0.0.0                 U     0 
0       0         lo
default              Shag            0.0.0.0                     UG  0 
0       0        eth0

Shag is mapped to 192.168.0.1 in /etc/hosts.

I notice in linuxconf that there is an 'Error' tab that says "Invalid line 
2 in /etc/resolv.conf".  In my resolve.conf, I have two lines:

search localdomain
nameserver

Any new ideas??

Jason

At 11:54 AM 8/24/00 -0500, you wrote:
>You might see what /sbin/route gives you ... although I tried this on a 
>box at work and the command doesn't exist. So I must have something on my 
>home machine that I don't have at work. If the route command works, you 
>can check your gateway that way - your gateway should show up as a line 
>labeled "default", mask 0.0.0.0 at the bottom of the list, interface eth0 
>in your situation. Also, is the ip address that's bound to eth0 192.168.0.2 ?
>
>-Dusty.
>
> >>> [EMAIL PROTECTED] 08/24/00 11:44AM >>>
>Yes, I am sure the eth0 interface is up and running.  When I do a 
>'ifconfig' it shows up with the
>proper IP, etc.  I will attempt to ping the loopback when I get home.  As 
>for the webpage, I don't
>have Apache installed on the linux box yet, I was waiting to get the 
>networking up first.  Unless
>Apache is installed by default (std. Workstation install), I can't check that.
>
>I have tried pinging using both IP and name with no luck either way.
>
>The 2 boxes are connected via a switch and 2 10/100 NICs.  The linux box 
>has a triple boot
>(Win98/Win2k/RH6.0) and the LAN works fine in both other OS's.  So, I 
>don't think it's a hardware
>issue.
>
>Someone earlier asked me if I had the routes setup properly.  I haven't a 
>clue.  Any thoughts?
>
>Jason
>
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED] 
>https://listman.redhat.com/mailman/listinfo/redhat-list 

-----------------------------------------------------
Click here for Free Video!!
http://www.gohip.com/free_video/ 



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED] 
https://listman.redhat.com/mailman/listinfo/redhat-list



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to