Board index Linux Networking

Strange Network behaviour

Strange Network behaviour

Post by Tim Woo » Tue, 24 Oct 2000 04:00:00



Hello,
          i'm hoping someone can help me trace a mistake in mty
settings.

I have a 10Base2 LAN connected to 3 Debian 2.2 boxes a Win98SE and a NT
box.

My desktop is used as a gateway to the Internet (IP 192.168.0.1) and my
Linux machines have it designated as gateway through "route".  They work
fine together - including taking ny laptop on and off the LAN evey two
weeks as I travel.

The Win98SE box is set with a static IP and DNS enabled using my ISP's
primary DNS. The gateway is set to 192.168.0.1.

The linux box hosts are all the same and I have checked each to make
sure that it's IP matches hosts.
Resolv.conf has only "nameserver    203.0.178.191" - that of my ISP.
I'm wondering if this is missing something essential.

On the Win98 machine I was downloading an update 11.2MB into a 15.5MB
file when the network crashed - I was away for quite a while waiting for
it so I don't know if the link broke.
Following that I could ping on the LAN.  I could ping the IP of the
other end of my ppp connection but nothing else.
Rebooting the gateway made no difference, nor did removing the NFS link
to my laptop.

I assume from this that it is a DNS problem but can't quite work it out.
I'd  be grateful for any assistance on this.

TIA
       Tim Wood

     the above adress is an antispam measure. Please address any direct

 
 
 
Top

Strange Network behaviour

Post by karl_he.. » Wed, 25 Oct 2000 12:41:42




Quote:> Hello,
>           i'm hoping someone can help me trace a mistake in mty
> settings.

> I have a 10Base2 LAN connected to 3 Debian 2.2 boxes a Win98SE and a NT box.

> My desktop is used as a gateway to the Internet (IP 192.168.0.1) and my Linux
> machines have it designated as gateway through "route".  They work fine
> together - including taking ny laptop on and off the LAN evey two weeks as I
> travel.

> The Win98SE box is set with a static IP and DNS enabled using my ISP's
> primary DNS. The gateway is set to 192.168.0.1.

> The linux box hosts are all the same and I have checked each to make sure
> that it's IP matches hosts. Resolv.conf has only "nameserver  
> 203.0.178.191" - that of my ISP. I'm wondering if this is missing something
> essential.

> On the Win98 machine I was downloading an update 11.2MB into a 15.5MB file
> when the network crashed - I was away for quite a while waiting for it so I
> don't know if the link broke. Following that I could ping on the LAN.  I
> could ping the IP of the other end of my ppp connection but nothing else.
> Rebooting the gateway made no difference, nor did removing the NFS link to my
> laptop.

> I assume from this that it is a DNS problem but can't quite work it out. I'd
> be grateful for any assistance on this.

try pinging the DNS server. then use nslookup/host to do a DNS query.
If the traffic is getting to their end then you can't do much else.

karl.

 
 
 
Top

1. Strange network behavior

I've been experiencing some strange network behavior
which I hope someone can explain:

I'm running MCC-interim 0.99pl10+. I got a call from the
network administrator this morning. He said that my
machine was flooding the campus gateway with ARP request
packets. At first, the packets listed my address as 0.0.192.78.
Later they listed this address as 0.0.192.78 and also listed
my correct address. I had pinged the gateway to see whether it
was up, so I'm not surprised that it was getting requests, but
I am surprised that it was getting flooded and that the strange
address 0.0.192.78 was listed.

Why was I pinging the gateway? Because I couldn't connect to
any other machine than my own, and was checking to see what was
happening.

When I booted Linux this morning, I was unable to connect to
any other machine. Does Linux need to connect to set my address
correctly? (In other words, could this be what was causing the
strange address 0.0.192.78?)

One more bit of information: I obviously have network access now.
Another campus network person came by and said that the network
bridge from our department to the rest of campus was malfunctioning,
and that was why I couldn't connect earlier. (In case this is
relevant.)

Any information at all would be appreciated. Obviously, the administrator
was not happy, and will be less happy if this happens again. I hope  that
I've provided enough information. If not, let me know.

(One more question: When I was unable to access the network, I also
was unable to start X. I found this odd, since I could connect to
my own machine, and don't see why X needs to connect to anything else.
What  was happening?)

Thanks in advance.

         -Vince Melfi


2. netscape 6.0

3. Strange Network Behavior

4. Linux IPAC datafile format

5. Strange Network Behaviour - Next Installment

6. Digital audio and Wearnes

7. strange network behaviour

8. kernel .config support?

9. Strange Networking behaviour Solaris 8

10. strange network behaviour

11. Strange network behavior

12. Strange behaviour of Network

13. strange behavior of redhat-config-network with 2 nic


All times are UTC
Board index