On Mon, May 25, 2009 at 4:23 PM, carlopmart <carlopmart@xxxxxxxxx> wrote:
> <mailto:carlopmart@xxxxxxxxx>> wrote:> search hpulabs.org <http://hpulabs.org>
>
> RobertH wrote:
> > ive read most of the thread, yet not all. forgive me as i might
> have missed
> > some of this below in helping...
> >
> > carlopmart,
> >
> > what is in your /etc/resolv.conf
>
> nameserver 127.0.0.1> > CentOS@xxxxxxxxxx <mailto:CentOS@xxxxxxxxxx>
>
> >
> > is it configured correctly?
> >
> > are you using ipv6?
>
> no.
>
> >
> > if not, is it fully disabled / turned off?
> >
> > in modprobe.conf put
> >
> > alias net-pf-10 off
> > alias ipv6 off
>
> I have configured this previously ..
>
>
> >
> > reboot...
> >
> > also, are you loading those other opsys on the same machine and
> getting good
> > results or different machines?
>
> I have good results using different operating systems but using same
> hardware ..
>
>
> >
> > testing other opsys on different hardware could be problematic.
> >
> > did you bother to check the physical ports to see if any problems
> in the
> > switch or with ethtool on the server interface ?
>
> No, I didn't do it because i have good results using other opsys ...
> >
> > thoughtfully consinder following advise of others re: tcp and dns
> >
> > cables...
> >
> > - rh
> >
> > _______________________________________________
> > CentOS mailing list
> > http://lists.centos.org/mailman/listinfo/centos> CentOS@xxxxxxxxxx <mailto:CentOS@xxxxxxxxxx>
> >
>
>
> --
> CL Martinez
> carlopmart {at} gmail {d0t} com
> _______________________________________________
> CentOS mailing list
> http://lists.centos.org/mailman/listinfo/centosSeLinux is disabled on both CentOS servers ...
>
>
> Have you double checked your SELinux config?
Same hardware and same server, because all opsys are installed on a ESXi 3.5u4
>
> You said you tested different OS'es on the same hardware? or tested
> different OS'es on the same hardware but different servers?
server with vmware tools ...
Maybe, but why only centos have problems??
>
> Maybe remotely could be a faulty NIC.
> ------------------------------------------------------------------------
>
>
>
> --
> "It is human nature to think wisely and act in an absurd fashion."
>
> "Todo el desorden del mundo proviene de las profesiones mal o
> mediocremente servidas"
>
>
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
--
CL Martinez
carlopmart {at} gmail {d0t} com
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
So, the problem resides on an ESXi CentOS VM?
I thought you were using a dedicated server though.
If so, what are you using as a NIC?
Sometimes the driver for e1000 gets faulty on RHEL/CentOS VMs, happened to me a couple times, just add a new NIC to solve that.
--
"It is human nature to think wisely and act in an absurd fashion."
"Todo el desorden del mundo proviene de las profesiones mal o mediocremente servidas"
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos