Re: Connectivity problem
- From: Roy Jones <sroyjones@xxxxxxxxxxxxx>
- Date: Sat, 08 Jul 2006 22:02:30 GMT
On Wed, 05 Jul 2006 13:41:43 +0100, BearItAll wrote:
Roy Jones wrote:
I've installed SUSE10 (non-commercial distro) and everything seems to have
gone OK except that the
system lost connectivity after the setup completed.
I know the NIC is OK because the machine ran the updates from the Internet
during the setup process with no trouble but when it rebooted after the
installation, I couldn't ping or connect to anything.
I show a link at the NIC and the switch port. A packet trace shows it got
an IP address (DHCP) but it gets no response to an ARP request for the
router's MAC, but the same trace shows one of my host network's DNS
servers responding with a "no such host" message. The SUSE firewall is
disabled. I can't ping any local or remote address, either by number or
name and none of the other machines on the LAN can ping the Linux box.
Anybody have any suggestions?
Roy
In the list has it definately found only one NIC, I know that on my mother
board they are two but only one has a connector and it happens to default
to eth1 after install, whilst the installer had correctly found this to be
the active one, after install the system took eth0 as the default. (Suse
and FDC5 did the same with this mobo). But it isn't difficult to sort out,
because you go into yast enable the correct one and disable the other, or
you can sometimes swap them in the bios.
The card would get a dhcp result (assuming it is reaching the dhcp server)
at startup because that is triggered from bios at start up, telling the
card to get going basically, mainly because it might have to boot from
there. Plus you do not suggest that it is not in the same class as your
other network, so we can assume that the DHCP side is working.
We know the card is working in other respects too because you did the
updates through it at install time.
So, it brings us to one thing, the card isn't being used by your system.
Here are some suggestions.
1. Could be a simple 'Activate' in the NIC hardware part of yast.
2. Your card has not been selected as the default for local traffic. As I
said above it could be a 2nd NIC that exists onboard even if there is no
external connector. Browsing your hardware should find that, if is isn't
listed in the NICs. Also look into your bios as it comes up, if they are
two you might want to swap them.
3. You have no network services running. Start them up.
You were right about the NIC not being used. What confused me at first was
that it worked during the initial installation and then quit after the
process finished.
It turned out that the problem was the updates. The OS starts an updater by
default and offers to download the latest updates and patches...several
dozen of them in my case. I accepted all the updates on the original
installation and the networking system choked. I reinstalled the OS and
skipped the updates and now all works OK.
I guess I'll have to go back through all the updates and be more selective
about which ones I allow.
R.
.
- References:
- Connectivity problem
- From: Roy Jones
- Re: Connectivity problem
- From: BearItAll
- Connectivity problem
- Prev by Date: Re: Discover machines on local network
- Next by Date: Partitioning question
- Previous by thread: Re: Connectivity problem
- Next by thread: Winmonitors are here!
- Index(es):
Relevant Pages
|
