Topic: Server 9.1 fails to connect to internet

[dustyp]

Since yesterday, my server has failed to connect to the internet since I aplied the latest two updates. If I try to ping its router from a root login, I receive "destination port is unreachable" inspite of it being pingable from other devices on the network. Also the SME box can be pinged from the network. It can be accessed via server manager.
All connected via static addresses.
This is only used as an email and web server not as a gateway.
It appears that DNS is not working on the SME server.
Any ideas?

[guest22]

...since I aplied the latest two updates....

What exact updates?

[idp_qbn]

Hi, dustyp
Here's something to start on....

1. Check your cable from SME to the router/hub/switch - is it fully plugged in? Change the cable if necessary to really test.
2) Check the configuration of the SME - from the server itself (I assume you can't connect to it remotely via PuTTY).
    Type "console" to start the Console program,
    Select "Configure the server"
    Check the IP settings - IP, Subnet, Gateway.
    Check the DNS settings
3) After checking, exit console and reboot.

This may not fix the problem but I have found these three (in that order) have been very useful in the past.

Of course, the problem can actually be a hardware failure of some sort and that just requires spending a little time and money.

If you need further help, you need to give a lot more information regarding your network configuration, how the connection (to the server, the local PCs, the Internet etc) is made, what upgrades in particular and anything else you think may be of assistance to people who will try to help.

Good luck
Ian
 

[dustyp]

I had already tried the options in the suggestions made by Ian but to no positive outcome. Thanks anyway.
I have resorted to a new replacement installation having wiped the disks clean followed by restoring a back up from last week.
So far, my problems appear to have been solved.
Thank you,
  - Dusty

[CharlieBrady]

If I try to ping its router from a root login, I receive "destination port is unreachable" ...

Are you sure? Did it not same "destination host unreachable"? ping doesn't use a "port".

It appears that DNS is not working on the SME server.

DNS depends on access to the Internet, via the router.

Since you no longer have this system running, there's nothing further we can do to diagnose the problem you saw after the updates.

[dustyp]

You are, of course, completely correct. It did say 'host'.
A wipe and reinstall corrected the problem but once the restore had completed, the problem reappeared even though the backup was from two years ago.
I can ping the address from outside my network. It just that I can't ping anywhere from this server even though other machines via the same router can
Now off to rebuild again from scratch.
I'll report back when I've done that in a couple of days time.
 

Are you sure? Did it not same "destination host unreachable"? ping doesn't use a "port".

DNS depends on access to the Internet, via the router.

Since you no longer have this system running, there's nothing further we can do to diagnose the problem you saw after the updates.

[Stefano]

You are, of course, completely correct. It did say 'host'.
A wipe and reinstall corrected the problem but once the restore had completed, the problem reappeared even though the backup was from two years ago.
I can ping the address from outside my network. It just that I can't ping anywhere from this server even though other machines via the same router can
Now off to rebuild again from scratch.
I'll report back when I've done that in a couple of days time.
 

Starting from scratch won't help you and US to understand
Once you restored your backup, let US know and we'll try to steer you in the right direction

[dustyp]

Because this entire thread will be totally useless to other people with a similar problem, due to me trashing the installation and starting from new, Is there any way of deleting this thread?

[guest22]

We can't change history. Please add [SOLVED] to the original post subject.

[janet]

dustyp

It is not totally useless to others.
It demonstrates that if you want to solve a problem you need to be prepared to go through the troubleshooting process.

You chose to wipe & reinstall & restore, which did not solve your problem.

Linux is not Windows,  so the reinstall trick is not necessarily valid.

Find the real problem in Linux eg a rogue custom template or inappropriate configuration or whatever, & usually your Linux install will be fixed without needing to do a reinstall.

Hopefully your path taken (without obtaining a fix) will encourage others not to make the same mistake as you did.

[dustyp]

I've found the cause of my problems.
SME server - updates testing had been enabled in my repositories and one of the updates had screwed up my installation. There were about 20, so I have no idea which one caused the problem.
Is there any way of undoing any updates apart from trawling through my yum.log and uninstalling any recent updates?
I know from experience that updating from the iso will not cure it.

[Stefano]

Take a look here:
https://access.redhat.com/solutions/64069

[guest22]

I've found the cause of my problems.
SME server - updates testing had been enabled in my repositories and one of the updates had screwed up my installation.

The major question is why it was enabled for by default it is disabled. Check /root/.bash_history

[guest22]

Take a look here:
https://access.redhat.com/solutions/64069

And on our own wiki here: https://wiki.contribs.org/Useful_Commands#YUM.27ing_and_repositories

[dustyp]

Operator error. I incorrectly assumed that enabling all repositories would do no harm.
Assumption: the mother of all fuckups - Lesson one in all forms of management.

The major question is why it was enabled for by default it is disabled. Check /root/.bash_history