Netgear Trouble 3 (Pinging)

Netgear Trouble 3 (Pinging)

Post by Jon » Thu, 03 May 2001 20:27:19



Hi,

    Firstly I must thank everyone for the help that I have received.

    I have a couple of questions before I get on to the problem I am having
with pinging.

    1. What should be in Network Configurator under Host?
        I only have  127.0.0.1       arnie.mec(hostname)

    2. In Linuxconf what should I have in the primary name and domain for
adaptor 1?  At the moment it is blank.

    3. Also in Linuxconf should I select IPX networks?  We do have a Novell
Server, don't know if that makes much difference.

    Back to pinging.  I am still having trouble pinging to windows PCs.

    To help you understand what was going on I ran two terminals one running
a ping to 192.168.0.1 and one running tcpdump.  Below I have listed the
output from those programs.  I hope this helps narrow down the problem.

In terminal 1 I ran tcpdump

In terminal 2 I ran "ping 192.168.0.10"

Below is the output from terminal 2.

PING 192.168.0.10(192.168.0.10) from 192.168.0.123:56(84) bytes of data
From 192.168.0.123: Destination Host Unreachable
From 192.168.0.123: Destination Host Unreachable
From 192.168.0.123: Destination Host Unreachable
"I then pressed Ctrl C"
192.168.0.10 ping statistics
4 packets transmitted,0 packets received, +3 errors, 100% packet loss.

Below is output from terminal 1 as terminal 2 was running

tcpdump
Kernel filter, protocol ALL, datagram packet socket
tcpdump:listening on all devices
eth0 > arp who-has 192.168.0.10 tell 192.168.0.123 (0:a0:cc:db:27:57)
lo > arnie.mec.1044 > arnie.mec.domain:40764+ PTR?
10.0.168.192.in-addr.arpa.(43)
lo < arnie.mec.1044 > arnie.mec.domain:40764+ PTR?
10.0.168.192.in-addr.arpa.(43)
lo > arnie.mec > arnie.mec:icmp:arnie.mec udp port domain unreachable [tos
0xc0]
lo < arnie.mec > arnie.mec:icmp:arnie.mec udp port domain unreachable [tos
0xc0]
lo > arnie.mec.1044 > arnie.mec.domain:40764+ PTR?
10.0.168.192.in-addr.arpa.(43)
lo < arnie.mec.1044 > arnie.mec.domain:40764+ PTR?
10.0.168.192.in-addr.arpa.(43)
lo > arnie.mec > arnie.mec:icmp:arnie.mec udp port domain unreachable [tos
0xc0]
lo < arnie.mec > arnie.mec:icmp:arnie.mec udp port domain unreachable [tos
0xc0]
lo > arnie.mec.1045 > arnie.mec.domain:40765+ PTR?
123.0.168.192.in-addr.arpa. (44)
lo < arnie.mec.1045 > arnie.mec.domain:40765+ PTR?
123.0.168.192.in-addr.arpa. (44)
lo > arnie.mec > arnie.mec:icmp:arnie.mec udp port domain unreachable [tos
0xc0]
lo < arnie.mec > arnie.mec:icmp:arnie.mec udp port domain unreachable [tos
0xc0]
eth0 > arp who-has 192.168.0.10 tell 192.168.0.123 (0:a0:cc:db:27:57)
eth0 > arp who-has 192.168.0.10 tell 192.168.0.123 (0:a0:cc:db:27:57)
lo > 192.168.0.123 > 192.168.0.123:icmp:host 192.168.0.10 unreachable [tos
0xc0]
lo > 192.168.0.123 > 192.168.0.123:icmp:host 192.168.0.10 unreachable [tos
0xc0]
lo > 192.168.0.123 > 192.168.0.123:icmp:host 192.168.0.10 unreachable [tos
0xc0]
lo < 192.168.0.123 > 192.168.0.123:icmp:host 192.168.0.10 unreachable [tos
0xc0]
lo < 192.168.0.123 > 192.168.0.123:icmp:host 192.168.0.10 unreachable [tos
0xc0]
lo < 192.168.0.123 > 192.168.0.123:icmp:host 192.168.0.10 unreachable [tos
0xc0]
etc

Hope that all of that helps

Jon

 
 
 

Netgear Trouble 3 (Pinging)

Post by Dean Thompso » Thu, 03 May 2001 22:16:28


Hi!,

Quote:> 1. What should be in Network Configurator under Host?
> I only have  127.0.0.1       arnie.mec(hostname)

Personally, I would have 127.0.0.1 set to be your localhost.localdomain

Quote:

> 2. In Linuxconf what should I have in the primary name and domain for
> adaptor 1?  At the moment it is blank.

You should allocate your IP address and hostname/domainname for adapter 1.
For example you could have the following:
192.168.0.10 as your IP address with the hostname of arnie.mech

Quote:

> 3. Also in Linuxconf should I select IPX networks?  We do have a Novell
> Server, don't know if that makes much difference.

You use the IPX settings to allow you to configure the IPX network number and
other parameters which are required for your machine to understand IPX traffic
which is flowing through the network.

Quote:

> Back to pinging.  I am still having trouble pinging to windows PCs.

> To help you understand what was going on I ran two terminals one running
> a ping to 192.168.0.1 and one running tcpdump.  Below I have listed the
> output from those programs.  I hope this helps narrow down the problem.

[...]

Quote:> PING 192.168.0.10(192.168.0.10) from 192.168.0.123:56(84) bytes of data
> From 192.168.0.123: Destination Host Unreachable
> From 192.168.0.123: Destination Host Unreachable
> From 192.168.0.123: Destination Host Unreachable
> "I then pressed Ctrl C"
> 192.168.0.10 ping statistics
> 4 packets transmitted,0 packets received, +3 errors, 100% packet loss.

This indiciates that the 192.168.0.10 machine does not have a route to get to
the 192.168.0.123 machine.  Overall, I suspect this is because the machine
does not have a route in existence for the 192.168.0 network.  This might be
partly the result of the fact that eth0 has not had an IP address allocated to
it based on your earlier post.

You may want to examine your routing tables on both your Linux and Windows box
to make sure that they have routes for the 192.168.0 network.

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

Netgear Trouble 3 (Pinging)

Post by Jon » Thu, 03 May 2001 22:44:31


Hi,

The network card is set with the IP address 192.168.0.123.

I am going to have a look at the routing in Linux using route. I will make a
post with the results from that.

How do I change routing tables on the Windows machine to make sure it is
routing correctly??

Thanks again for the help.

I am beginning to like Linux more as I keep trying it.

Jon


Quote:

> Hi!,

> > 1. What should be in Network Configurator under Host?
> > I only have  127.0.0.1       arnie.mec(hostname)

> Personally, I would have 127.0.0.1 set to be your localhost.localdomain

> > 2. In Linuxconf what should I have in the primary name and domain for
> > adaptor 1?  At the moment it is blank.

> You should allocate your IP address and hostname/domainname for adapter 1.
> For example you could have the following:
> 192.168.0.10 as your IP address with the hostname of arnie.mech

> > 3. Also in Linuxconf should I select IPX networks?  We do have a Novell
> > Server, don't know if that makes much difference.

> You use the IPX settings to allow you to configure the IPX network number
and
> other parameters which are required for your machine to understand IPX
traffic
> which is flowing through the network.

> > Back to pinging.  I am still having trouble pinging to windows PCs.

> > To help you understand what was going on I ran two terminals one running
> > a ping to 192.168.0.1 and one running tcpdump.  Below I have listed the
> > output from those programs.  I hope this helps narrow down the problem.

> [...]

> > PING 192.168.0.10(192.168.0.10) from 192.168.0.123:56(84) bytes of data
> > From 192.168.0.123: Destination Host Unreachable
> > From 192.168.0.123: Destination Host Unreachable
> > From 192.168.0.123: Destination Host Unreachable
> > "I then pressed Ctrl C"
> > 192.168.0.10 ping statistics
> > 4 packets transmitted,0 packets received, +3 errors, 100% packet loss.

> This indiciates that the 192.168.0.10 machine does not have a route to get
to
> the 192.168.0.123 machine.  Overall, I suspect this is because the machine
> does not have a route in existence for the 192.168.0 network.  This might
be
> partly the result of the fact that eth0 has not had an IP address
allocated to
> it based on your earlier post.

> You may want to examine your routing tables on both your Linux and Windows
box
> to make sure that they have routes for the 192.168.0 network.

> See ya

> Dean Thompson

> --

+____________________________+____________________________________________+

|
> | Bach. Computing (Hons)     | ICQ     - 45191180
|
> | PhD Student                | Office  - <Off-Campus>
|
> | School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)
|
> | MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077
|
> | Melbourne, Australia       |
|

+----------------------------+--------------------------------------------+
 
 
 

Netgear Trouble 3 (Pinging)

Post by Dean Thompso » Thu, 03 May 2001 22:53:00


Hi!,

Quote:> The network card is set with the IP address 192.168.0.123.
> I am going to have a look at the routing in Linux using route. I will make
> a post with the results from that.

> How do I change routing tables on the Windows machine to make sure it is
> routing correctly??

Normally the routing table in Windows is correct.  You can see what the
routing table looks like with the command: "route print".  In order to change
the routes you might like to type: "route --help" for a list of commands that
are available.  However, I suspect that the routing table should look okay.

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

Netgear Trouble 3 (Pinging)

Post by Jon » Thu, 03 May 2001 23:17:42


Here is the output from the command route

Kernel IP routing table

Destination        Gateway        GenMask            Flags        Metric
Ref        Use        Iface
192.168.0.0            *            255.255.255.0        U                0
0            0            eth0
127.0.0.1                *            255.0.0.0                U
0             0            0            lo

Also another thing when I ping to my linux box (192.168.0.123) from Win
machine(192.168.0.10) and I watch what happens on tcpdump I am even more
confused.  It seems to me that it is replying.  Here is a selection of the
output below.

eth0 B arp who-has 192.168.0.123 tell 192.168.0.10
eth0 > arp reply 192.168.0.123(0:a0:cc:db:27:57)  is at (0:a0:cc:db:27:57)
(0:c0:f0:29:e:89)

But on the Win machine it says Request time out.

Thanks

Jon


Quote:

> Hi!,

> > The network card is set with the IP address 192.168.0.123.
> > I am going to have a look at the routing in Linux using route. I will
make
> > a post with the results from that.

> > How do I change routing tables on the Windows machine to make sure it is
> > routing correctly??

> Normally the routing table in Windows is correct.  You can see what the
> routing table looks like with the command: "route print".  In order to
change
> the routes you might like to type: "route --help" for a list of commands
that
> are available.  However, I suspect that the routing table should look
okay.

> See ya

> Dean Thompson

> --

+____________________________+____________________________________________+

|
> | Bach. Computing (Hons)     | ICQ     - 45191180
|
> | PhD Student                | Office  - <Off-Campus>
|
> | School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)
|
> | MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077
|
> | Melbourne, Australia       |
|

+----------------------------+--------------------------------------------+
 
 
 

Netgear Trouble 3 (Pinging)

Post by Jon » Thu, 03 May 2001 23:20:22


Try again

Destination        Gateway        GenMask            Flags        Metric    Ref        Use        Iface
  192.168.0.0            *            255.255.255.0        U                0           0            0            eth0
 127.0.0.1                *            255.0.0.0                U                0             0            0            lo


> Here is the output from the command route

> Kernel IP routing table

> Destination        Gateway        GenMask            Flags        Metric
> Ref        Use        Iface
> 192.168.0.0            *            255.255.255.0        U                0
> 0            0            eth0
> 127.0.0.1                *            255.0.0.0                U
> 0             0            0            lo

> Also another thing when I ping to my linux box (192.168.0.123) from Win
> machine(192.168.0.10) and I watch what happens on tcpdump I am even more
> confused.  It seems to me that it is replying.  Here is a selection of the
> output below.

> eth0 B arp who-has 192.168.0.123 tell 192.168.0.10
> eth0 > arp reply 192.168.0.123(0:a0:cc:db:27:57)  is at (0:a0:cc:db:27:57)
> (0:c0:f0:29:e:89)

> But on the Win machine it says Request time out.

> Thanks

> Jon



> > Hi!,

> > > The network card is set with the IP address 192.168.0.123.
> > > I am going to have a look at the routing in Linux using route. I will
> make
> > > a post with the results from that.

> > > How do I change routing tables on the Windows machine to make sure it is
> > > routing correctly??

> > Normally the routing table in Windows is correct.  You can see what the
> > routing table looks like with the command: "route print".  In order to
> change
> > the routes you might like to type: "route --help" for a list of commands
> that
> > are available.  However, I suspect that the routing table should look
> okay.

> > See ya

> > Dean Thompson

> > --

> +____________________________+____________________________________________+

> |
> > | Bach. Computing (Hons)     | ICQ     - 45191180
> |
> > | PhD Student                | Office  - <Off-Campus>
> |
> > | School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)
> |
> > | MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077
> |
> > | Melbourne, Australia       |
> |

> +----------------------------+--------------------------------------------+

 
 
 

Netgear Trouble 3 (Pinging)

Post by Jon » Fri, 04 May 2001 00:06:43


Another thing that I have noticed when I ping 192.168.0.whatever   is that
the Use part of the route command doesn't go up.  So therefore I presume
that it can't be using the routing table.
Does anyone know what might be going on?

Thanks

Jon.


Try again

Destination        Gateway        GenMask            Flags        Metric
Ref        Use        Iface
  192.168.0.0            *            255.255.255.0        U
0           0            0            eth0
 127.0.0.1                *            255.0.0.0                U
0             0            0            lo


> Here is the output from the command route

> Kernel IP routing table

> Destination        Gateway        GenMask            Flags        Metric
> Ref        Use        Iface
> 192.168.0.0            *            255.255.255.0        U
0
> 0            0            eth0
> 127.0.0.1                *            255.0.0.0                U
> 0             0            0            lo

> Also another thing when I ping to my linux box (192.168.0.123) from Win
> machine(192.168.0.10) and I watch what happens on tcpdump I am even more
> confused.  It seems to me that it is replying.  Here is a selection of the
> output below.

> eth0 B arp who-has 192.168.0.123 tell 192.168.0.10
> eth0 > arp reply 192.168.0.123(0:a0:cc:db:27:57)  is at (0:a0:cc:db:27:57)
> (0:c0:f0:29:e:89)

> But on the Win machine it says Request time out.

> Thanks

> Jon



> > Hi!,

> > > The network card is set with the IP address 192.168.0.123.
> > > I am going to have a look at the routing in Linux using route. I will
> make
> > > a post with the results from that.

> > > How do I change routing tables on the Windows machine to make sure it
is
> > > routing correctly??

> > Normally the routing table in Windows is correct.  You can see what the
> > routing table looks like with the command: "route print".  In order to
> change
> > the routes you might like to type: "route --help" for a list of commands
> that
> > are available.  However, I suspect that the routing table should look
> okay.

> > See ya

> > Dean Thompson

> > --

+____________________________+____________________________________________+
Quote:> > | Dean Thompson              | E-mail  -


Quote:> |
> > | Bach. Computing (Hons)     | ICQ     - 45191180
> |
> > | PhD Student                | Office  - <Off-Campus>
> |
> > | School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)
> |
> > | MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077
> |
> > | Melbourne, Australia       |
> |

+----------------------------+--------------------------------------------+

- Show quoted text -

 
 
 

Netgear Trouble 3 (Pinging)

Post by Dean Thompso » Fri, 04 May 2001 00:17:57


Hi!,

Quote:>Destination        Gateway        GenMask            Flags        Metric
>Ref        Use        Iface
>192.168.0.0            *            255.255.255.0        U                0
>0            0            eth0
>127.0.0.1                *            255.0.0.0                U
>0             0            0            lo

> Also another thing when I ping to my linux box (192.168.0.123) from Win
> machine(192.168.0.10) and I watch what happens on tcpdump I am even more
> confused.  It seems to me that it is replying.  Here is a selection of the
> output below.

Okay, well your routing table looks okay apart from the fact that there is no
default route being present (although this shouldn't effect your local
network).  I presume that there are no firewalls of any sort running on either
computer which would be causing a packet to be absorbed without the system
responding to it.

Additionally, is it possible to take a look at your "ifconfig eth0" so that we
can see whether or not your Linux machine is actually putting packets back out
onto the ether.

On the Windows machine, I presume that the IP address and the subnet mask and
the gateway address are configured correctly and that when you do a "route
print" you can actually see a path which the computer can take to reach your
Linux computer.

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

Netgear Trouble 3 (Pinging)

Post by Jon » Fri, 04 May 2001 01:02:33


Hi,

There are no firewalls installed on the windows m/c and I presume that none are running on the linux box.

This is the output to route print on the windows machine

C:\WINDOWS>route print

===========================================================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x2 ...44 45 53 54 00 00 ...... PPP Adapter.

0x3 ...00 c0 f0 29 0e 89 ...... Realtek RTL8029(AS) Ethernet Adapt

============================================================

============================================================

Active Routes:

Network Destination         Netmask                 Gateway         Interface         Metric

127.0.0.0                              255.0.0.0                 127.0.0.1          127.0.0.1                 1

192.168.0.0                          255.255.255.0         192.168.0.10     192.168.0.10           1

192.168.0.10                        255.255.255.255     127.0.0.1           127.0.0.1                 1

192.168.0.255                     255.255.255.255      192.168.0.10     192.168.0.10           1

224.0.0.0                             224.0.0.0                   192.168.0.10     192.168.0.10         1

255.255.255.255                 255.255.255.255       192.168.0.10             2                     1

============================================================

Persistent Routes:

None

Output from ifconfig eth0

eth0    Link encap:Ethernet HWaddr 00:A0:CC:DB:27:57
           inet addr:192.168.0.123 Bcast:192.168.0.255 Mcast 255.255.255.0
           IPX/Ethernet 802.2 addr:00000016:00A0CCDB2757
           UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
           RX packets:63 errors:0 dropped:0 overruns:0 frame:0
           TX packets:6 errors:0 dropped:0 overruns:0 frame:0
           collisions:0 txqueuelen:100
            Interrupt:10 Base address:0xe000

Hope all of that helps
By the way the windows machine is running ME.  But I still can't ping to/from other win 95 machines on the network.

Thanks again

Jon


> Hi!,

> >Destination        Gateway        GenMask            Flags        Metric
> >Ref        Use        Iface
> >192.168.0.0            *            255.255.255.0        U                0
> >0            0            eth0
> >127.0.0.1                *            255.0.0.0                U
> >0             0            0            lo

> > Also another thing when I ping to my linux box (192.168.0.123) from Win
> > machine(192.168.0.10) and I watch what happens on tcpdump I am even more
> > confused.  It seems to me that it is replying.  Here is a selection of the
> > output below.

> Okay, well your routing table looks okay apart from the fact that there is no
> default route being present (although this shouldn't effect your local
> network).  I presume that there are no firewalls of any sort running on either
> computer which would be causing a packet to be absorbed without the system
> responding to it.

> Additionally, is it possible to take a look at your "ifconfig eth0" so that we
> can see whether or not your Linux machine is actually putting packets back out
> onto the ether.

> On the Windows machine, I presume that the IP address and the subnet mask and
> the gateway address are configured correctly and that when you do a "route
> print" you can actually see a path which the computer can take to reach your
> Linux computer.

> See ya

> Dean Thompson

> --
> +____________________________+____________________________________________+

> | Bach. Computing (Hons)     | ICQ     - 45191180                         |
> | PhD Student                | Office  - <Off-Campus>                     |
> | School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
> | MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
> | Melbourne, Australia       |                                            |
> +----------------------------+--------------------------------------------+

 
 
 

Netgear Trouble 3 (Pinging)

Post by Dean Thompso » Fri, 04 May 2001 09:56:41


Hi Jon,

Quote:> C:\WINDOWS>route print
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...44 45 53 54 00 00 ...... PPP Adapter.
> 0x3 ...00 c0 f0 29 0e 89 ...... Realtek RTL8029(AS) Ethernet Adapt
> ============================================================

> Active Routes:

[...]

Quote:> eth0    Link encap:Ethernet HWaddr 00:A0:CC:DB:27:57
>            inet addr:192.168.0.123 Bcast:192.168.0.255 Mcast 255.255.255.0
>            IPX/Ethernet 802.2 addr:00000016:00A0CCDB2757
>            UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>            RX packets:63 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:6 errors:0 dropped:0 overruns:0 frame:0
>            collisions:0 txqueuelen:100
>             Interrupt:10 Base address:0xe000

The routing tables look good.  The only thing that slightly concerns me is the
low TX cound from the Linux box.  I would have thought that it might have been
talking a little more on the system than 6 packets worth.  I presume that the
machines are connected to the right port on the NetGear device and that
neither of the units are connected to the uplink port and that neither of the
units are using cross-over cables ?

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

Netgear Trouble 3 (Pinging)

Post by Jon » Fri, 04 May 2001 17:04:24


Hi,

Quote:> The routing tables look good.  The only thing that slightly concerns me is the
> low TX cound from the Linux box.  I would have thought that it might have been
> talking a little more on the system than 6 packets worth.  I presume that the
> machines are connected to the right port on the NetGear device and that
> neither of the units are connected to the uplink port and that neither of the
> units are using cross-over cables ?

There is only one connection on the Netgear card and the cat5 cable goes straight into a hub about 30cm away.  The hub works because
the windows machine I am trying to ping to is also connected to that hub, and the network works fine in win me.  Neither of the
units are connected to the uplink port and I am not using cross over cables.

Is it normally this hard to set up a network communication between Linux and windows.

Another thing - Do I have to set an address for a gateway for the Linux box?   Because I haven't got one set at the moment.

Thanks again

Jon

 
 
 

Netgear Trouble 3 (Pinging)

Post by Dean Thompso » Fri, 04 May 2001 17:44:58


Hi Jon,

Quote:>>The routing tables look good.  The only thing that slightly concerns me is
>>the low TX cound from the Linux box.  I would have thought that it might
>>have been talking a little more on the system than 6 packets worth.  I
>>presume that the machines are connected to the right port on the NetGear
>>device and that neither of the units are connected to the uplink port and
>>that neither of the units are using cross-over cables ?

> There is only one connection on the Netgear card and the cat5 cable goes
> straight into a hub about 30cm away.  The hub works because the windows
> machine I am trying to ping to is also connected to that hub, and the
> network works fine in win me.  Neither of the units are connected to the
> uplink port and I am not using cross over cables.

> Is it normally this hard to set up a network communication between Linux
> and windows ?

No, not normally.  Infact getting the networking to wokr in Linux shouldn't be
that hard.  The problems come more with Linux being able to identify and work
with the various types of network cards.

Quote:> Another thing - Do I have to set an address for a gateway for the Linux
> box?   Because I haven't got one set at the moment.

Eventually you will need to specify a gateway most likely the IP address of
your DSL router or cable modem or network device which is responsible for
connecting you to the outside world.  However, if your unit is just a hub and
does nothing special, you shouldn't need a gateway because the broadcast and
netmask should allow the other machine to see the network traffic.

Its confusing me now :|, I can't see why you can get a connection based on the
network settings that you have provided in previous posts.

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

Netgear Trouble 3 (Pinging)

Post by Jon » Fri, 04 May 2001 18:28:46


Hi,

Thanks for all your help again.

How do you suggest that I continue.


> Hi Jon,

> >>The routing tables look good.  The only thing that slightly concerns me is
> >>the low TX cound from the Linux box.  I would have thought that it might
> >>have been talking a little more on the system than 6 packets worth.  I
> >>presume that the machines are connected to the right port on the NetGear
> >>device and that neither of the units are connected to the uplink port and
> >>that neither of the units are using cross-over cables ?

> > There is only one connection on the Netgear card and the cat5 cable goes
> > straight into a hub about 30cm away.  The hub works because the windows
> > machine I am trying to ping to is also connected to that hub, and the
> > network works fine in win me.  Neither of the units are connected to the
> > uplink port and I am not using cross over cables.

> > Is it normally this hard to set up a network communication between Linux
> > and windows ?

> No, not normally.  Infact getting the networking to wokr in Linux shouldn't be
> that hard.  The problems come more with Linux being able to identify and work
> with the various types of network cards.

> > Another thing - Do I have to set an address for a gateway for the Linux
> > box?   Because I haven't got one set at the moment.

> Eventually you will need to specify a gateway most likely the IP address of
> your DSL router or cable modem or network device which is responsible for
> connecting you to the outside world.  However, if your unit is just a hub and
> does nothing special, you shouldn't need a gateway because the broadcast and
> netmask should allow the other machine to see the network traffic.

> Its confusing me now :|, I can't see why you can get a connection based on the
> network settings that you have provided in previous posts.

> See ya

> Dean Thompson

> --
> +____________________________+____________________________________________+

> | Bach. Computing (Hons)     | ICQ     - 45191180                         |
> | PhD Student                | Office  - <Off-Campus>                     |
> | School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
> | MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
> | Melbourne, Australia       |                                            |
> +----------------------------+--------------------------------------------+

 
 
 

Netgear Trouble 3 (Pinging)

Post by Mojo Nichol » Fri, 04 May 2001 19:19:42



> Hi,

> Thanks for all your help again.

> How do you suggest that I continue.

Try ruling out hardware problems.

Try a different port on the hub.

Is your ip static or dynamic?  Try disconnecting the windows and getting the linux box to work with your ISP.
from the same port in the hub....

Finally if all else fails walk away from it for a while, when you get back., start with a clean state:-(
I know that sounds like a waste, but if I think back to all the trouble I had with networking early on it was
all pretty basic.  Check all of your ip numbers again.  What is in the file /etc/hosts.allow ? /etc/hosts.deny?
And a  question below.


> > Hi Jon,

> > >>The routing tables look good.  The only thing that slightly concerns me is
> > >>the low TX cound from the Linux box.  I would have thought that it might
> > >>have been talking a little more on the system than 6 packets worth.  I
> > >>presume that the machines are connected to the right port on the NetGear
> > >>device and that neither of the units are connected to the uplink port and
> > >>that neither of the units are using cross-over cables ?

> > > There is only one connection on the Netgear card and the cat5 cable goes
> > > straight into a hub about 30cm away.  The hub works because the windows
> > > machine I am trying to ping to is also connected to that hub, and the
> > > network works fine in win me.

Can you draw this network out.  ie:

linux ---------------|
                                            |
                                          hub----cable modem?
                                            |
windows-------------|

replace the names with actual  ip address as reported by the machines

- Show quoted text -

>  Neither of the units are connected to the
> > > uplink port and I am not using cross over cables.

> > > Is it normally this hard to set up a network communication between Linux
> > > and windows ?

> > No, not normally.  Infact getting the networking to wokr in Linux shouldn't be
> > that hard.  The problems come more with Linux being able to identify and work
> > with the various types of network cards.

> > > Another thing - Do I have to set an address for a gateway for the Linux
> > > box?   Because I haven't got one set at the moment.

> > Eventually you will need to specify a gateway most likely the IP address of
> > your DSL router or cable modem or network device which is responsible for
> > connecting you to the outside world.  However, if your unit is just a hub and
> > does nothing special, you shouldn't need a gateway because the broadcast and
> > netmask should allow the other machine to see the network traffic.

> > Its confusing me now :|, I can't see why you can get a connection based on the
> > network settings that you have provided in previous posts.

> > See ya

> > Dean Thompson

> > --
> > +____________________________+____________________________________________+

> > | Bach. Computing (Hons)     | ICQ     - 45191180                         |
> > | PhD Student                | Office  - <Off-Campus>                     |
> > | School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
> > | MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
> > | Melbourne, Australia       |                                            |
> > +----------------------------+--------------------------------------------+

 
 
 

Netgear Trouble 3 (Pinging)

Post by Jon » Fri, 04 May 2001 22:46:13


Hi,

The hosts.allow and host.deny were both empty.
Below is a picture of this part of the network as requested.

                                                                                                          I ---------192.168.0.10
(Windows ME)
 Novell Netware File Server---Patch Panel-----------------HUB-----I----------192.168.0.123(Linux Box)
                                                                                                          I----------192.168.0.1
(Windows 95)

This is just a section of the network.  Overall there are about 10 computers

Jon



> > Hi,

> > Thanks for all your help again.

> > How do you suggest that I continue.

> Try ruling out hardware problems.

> Try a different port on the hub.

> Is your ip static or dynamic?  Try disconnecting the windows and getting the linux box to work with your ISP.
> from the same port in the hub....

> Finally if all else fails walk away from it for a while, when you get back., start with a clean state:-(
> I know that sounds like a waste, but if I think back to all the trouble I had with networking early on it was
> all pretty basic.  Check all of your ip numbers again.  What is in the file /etc/hosts.allow ? /etc/hosts.deny?
> And a  question below.


> > > Hi Jon,

> > > >>The routing tables look good.  The only thing that slightly concerns me is
> > > >>the low TX cound from the Linux box.  I would have thought that it might
> > > >>have been talking a little more on the system than 6 packets worth.  I
> > > >>presume that the machines are connected to the right port on the NetGear
> > > >>device and that neither of the units are connected to the uplink port and
> > > >>that neither of the units are using cross-over cables ?

> > > > There is only one connection on the Netgear card and the cat5 cable goes
> > > > straight into a hub about 30cm away.  The hub works because the windows
> > > > machine I am trying to ping to is also connected to that hub, and the
> > > > network works fine in win me.

> Can you draw this network out.  ie:

> linux ---------------|
>                                             |
>                                           hub----cable modem?
>                                             |
> windows-------------|

> replace the names with actual  ip address as reported by the machines

> >  Neither of the units are connected to the
> > > > uplink port and I am not using cross over cables.

> > > > Is it normally this hard to set up a network communication between Linux
> > > > and windows ?

> > > No, not normally.  Infact getting the networking to wokr in Linux shouldn't be
> > > that hard.  The problems come more with Linux being able to identify and work
> > > with the various types of network cards.

> > > > Another thing - Do I have to set an address for a gateway for the Linux
> > > > box?   Because I haven't got one set at the moment.

> > > Eventually you will need to specify a gateway most likely the IP address of
> > > your DSL router or cable modem or network device which is responsible for
> > > connecting you to the outside world.  However, if your unit is just a hub and
> > > does nothing special, you shouldn't need a gateway because the broadcast and
> > > netmask should allow the other machine to see the network traffic.

> > > Its confusing me now :|, I can't see why you can get a connection based on the
> > > network settings that you have provided in previous posts.

> > > See ya

> > > Dean Thompson

> > > --
> > > +____________________________+____________________________________________+

> > > | Bach. Computing (Hons)     | ICQ     - 45191180                         |
> > > | PhD Student                | Office  - <Off-Campus>                     |
> > > | School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
> > > | MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
> > > | Melbourne, Australia       |                                            |
> > > +----------------------------+--------------------------------------------+

 
 
 

1. NETGEAR FA410 Can PING out can't be PING'd

Weird one here....I have a Dell Laptop with a PCMCIA Netgear FA410 network
card.

Up until recently I was able to communicate to and from this machine on my
subnet.

Now, for some weird reason machines on my subnet cannot ping my machine?
But this RedHat 7.0 installation can ping other non-Linux boxes (WinNT,
Win98, etc)

Any ideas?

Also, I get an insmod error on boot-up

Regards,
John

2. Konqueror menu problem

3. A pings B, B pings C, C cannot ping A

4. how to remove redunt word from space seperated word string

5. Netgear linux and netgear DG824MI

6. Sendfile, loopback, and TCP header checksum

7. netgear ma301 and non-netgear PCMCIA wireless adapter compatability

8. lint

9. natsemi trouble with netgear fa311 in 2.4.6

10. Please HELP: Netgear FA311 troubles

11. dual netgear FA310TX trouble

12. Netgear 410TX trouble in RedHat 7

13. HP pavilion 4430 computer (Trouble with netgear FA310TX)