Index: [Article Count Order] [Thread]

Date:  Wed, 25 Mar 2009 11:50:42 -0700
From:  "Ken Marcus - Precision Web Hosting, Inc." <kenmarcus (at mark) precisionweb.net>
Subject:  [coba-e:15387] Re: Ethernet issues
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <E76C1B90FDE44FD6BEAE983DEBB16778@OfficeKen>
References:  <49CA2FD0.4060906 (at mark) probass.com> <49CA311E.3060906 (at mark) virtbiz.com> <49CA32D7.60708 (at mark) probass.com> <49CA35D3.5040604 (at mark) virtbiz.com> <49CA40B9.1020108 (at mark) probass.com> <49CA73F1.5050204 (at mark) probass.com>
X-Mail-Count: 15387


----- Original Message ----- 
From: "Richard C. Barker Sr." <rc (at mark) probass.com>
To: <coba-e (at mark) bluequartz.org>
Sent: Wednesday, March 25, 2009 11:12 AM
Subject: [coba-e:15385] Re: Ethernet issues


> Ok I see what was the cause now how is BlueQuartx going to resolve the 
> issue.
>
> I had run the latest yum update and had to reboot yesterday today I had to 
> reboot
> another server and not that server can not ping the anything that does not 
> reside
> on that server. Soooooo Now I have two servers down.
>
> Can some please advise how to fix or back out that last yum update?
>
> Thanks in advance,
> RC
>
> Richard C. Barker Sr. wrote:
>> No NAT running at all, only DNS is the same for all other servers. The 
>> lookups are fine
>> and correct.
>>
>> Customers can get mail just fine, if they reply to an email that is where 
>> it starts as the sever
>> can not talk to the smart relay host is where all email goes to and comes 
>> from.
>>
>> RC
>>
>>
>> Chris Gebhardt - VIRTBIZ Internet wrote:
>>>
>>> Richard C. Barker Sr. wrote:
>>>> No my 5 other server are setup the same and can ping the gateway and 
>>>> the firewall.
>>>>
>>>> I am see the mailq building and all are saying (Deferred: Connection 
>>>> timed out with host.whatever.com)
>>>>
>>>> netstat -nr
>>>> 1.x.x.0    0.0.0.0         255.255.255.0   U         0 0          0 
>>>> eth0
>>>> 2.x.x.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0
>>>> 127.0.0.0       0.0.0.0         255.0.0.0       U         0 0 
>>>> 0 lo
>>>> 0.0.0.0         x.x.x.1   0.0.0.0         UG        0 0          0 eth0
>>>>
>>>
>>> Well I doubt it's a Layer2 issue.  You're using NAT on non-routable IPs 
>>> inside a firewall?  Hmmmm.   That's where I would be looking first.
>>>
>>> You could try re-running the netconfig and restarting the network.
>>>
>>> But wait... mailq is building?  Indicating customers are connecting? Are 
>>> you certain this isn't a DNS issue?
>>>
>>
>
> -- 
> +---------------------------------------------+
> Richard C. Barker Sr.
> CEO & President
> 1-800-510-3139
> ProBass Networks Inc.
>   http://www.probassnetworks.net
>   http://www.probass.net
> ***************************************
> DISCLAIMER : -
> This e-mail is confidential and intended only for the use
> of the individual or entity named above and may contain
> information that is privileged. If you are not the intended
> recipient, you are notified that any dissemination, distribution
> or copying of this e-mail is strictly prohibited. If you have
> received this email in error, please notify us immediately
> by return email or telephone and destroy the original message.


Richard

What if you just re-run the    /root/network_settings.sh    script.



----
Ken Marcus
Ecommerce Web Hosting by
Precision Web Hosting, Inc.
http://www.precisionweb.net