Mailinglist Archive: opensuse (3378 mails)
| < Previous | Next > |
Re: [SLE] Baffled newbie trying to reach NT LAN
- From: Jesse Marlin <jlm@xxxxxxxxxxx>
- Date: Sun, 14 Apr 2002 12:48:51 -0400
- Message-id: <15545.45811.910087.833461@xxxxxxxxxxxxxxxx>
Brian Durant writes:
> On Wednesday 27 March 2002 10:03, jon@xxxxxxxxx wrote:
> > It sounds like your default gateway / route is wrong... can you email the
> > following;
> >
> > 1. Output of "ifconfig"
>
> I don't believe that I ever got a response to this posting, so I will try
> again. Hopefully the thread isn't irretrievably broken.
>
> Here is ifconfig:
>
> eth0 Link encap:Ethernet HWaddr 00:50:2C:01:2B:1B
> inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::250:2cff:fe01:2b1b/10 Scope:Link
> UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1
> RX packets:2163 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2079 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:602395 (588.2 Kb) TX bytes:153166 (149.5 Kb)
> Interrupt:11 Base address:0xec00
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:70 errors:0 dropped:0 overruns:0 frame:0
> TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4564 (4.4 Kb) TX bytes:4564 (4.4 Kb)
>
> > 2. Output of "route -n"
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
>
The routing table looks good. Is that 192.168.1.1 a router? Does the
NT box's routing match this. The netmask will be important. The only other
thing I can offer is that if 192.168.1.1 is a router, make sure it knows
about your address, and also make sure the cables are good.
> On Wednesday 27 March 2002 10:03, jon@xxxxxxxxx wrote:
> > It sounds like your default gateway / route is wrong... can you email the
> > following;
> >
> > 1. Output of "ifconfig"
>
> I don't believe that I ever got a response to this posting, so I will try
> again. Hopefully the thread isn't irretrievably broken.
>
> Here is ifconfig:
>
> eth0 Link encap:Ethernet HWaddr 00:50:2C:01:2B:1B
> inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::250:2cff:fe01:2b1b/10 Scope:Link
> UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1
> RX packets:2163 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2079 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:602395 (588.2 Kb) TX bytes:153166 (149.5 Kb)
> Interrupt:11 Base address:0xec00
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:70 errors:0 dropped:0 overruns:0 frame:0
> TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4564 (4.4 Kb) TX bytes:4564 (4.4 Kb)
>
> > 2. Output of "route -n"
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
>
The routing table looks good. Is that 192.168.1.1 a router? Does the
NT box's routing match this. The netmask will be important. The only other
thing I can offer is that if 192.168.1.1 is a router, make sure it knows
about your address, and also make sure the cables are good.
| < Previous | Next > |