> <mailto:
carlopmart@gmail.com>> wrote:
>
> 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
>
> >
> > 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
> > CentOS@centos.org <mailto:CentOS@centos.org>
> CentOS@centos.org <mailto:CentOS@centos.org>
SeLinux is disabled on both CentOS servers ...
>
> You said you tested different OS'es on the same hardware? or tested
> different OS'es on the same hardware but different servers?
Same hardware and same server, because all opsys are installed on a ESXi 3.5u4
server with vmware tools ...
>
> Maybe remotely could be a faulty NIC.
Maybe, but why only centos have problems??
>
>
>
> --
> "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"
>
>
> ------------------------------------------------------------------------