Dhcp client stopped at startup

1- first you have to login using any user with administrative
privileges.
2- start---> Run---> regedit
3- go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip.
4- right-click on the Tcpip from the left tap menu and choose
permission.
5- Choose (Allow) for all listed groups and users, then press apply and
ok.
6- go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp.
7- do the same as before.
8- now plug your network cable or connect to the wireless, if u got an
IP from the DHCP then it's done, if not you have to open the services
from the administrative tools to run the DHCP clinet or stop and run the
service again.

*** YOU HAVE TO DO THIS EVERYTIME U LOG IN OR CONNECT TO THE
NETWORK.
*** THIS PROBLEM ASLO EXIST WITH WINDOWS 7 ULTIMATE.

This problem might be related to the DHCP server, seems like up-grading
from windows 2000 advanced server to windows 2003 may cause this probem,
or maybe the group policy in the active directory.


Or try this *netsh winsock reset catalog *

Creating local yum repository on RHEL 6.2

1. Mount the DVD or ISO
#mount -t cifs -o username=user,password=pass,domain=abc.com //servername/share /mnt
#mount /dev/cdrom /mnt
#mount -o ro,loop redhat.iso /mnt

2. Copy files
#mkdir -p /var/repo/rhel6
#cp -r /mnt/* /var/repo/rhel6/
#cd /var/repo/rhel6/Packages
#rpm -i createrepo...
#cd /var/repo
#createrepo .

3. Create file local.repo in /etc/yum.repos.d/
#cd  /etc/yum.repos.d/
#touch local.repo

[local]
enabled=1
gpgcheck=0
name=Red Hat Linux $releasever - $basearch - DVD
baseurl=file:///var/repo

Save and exit
Try to install a package:
#yum install httpd

Device eth0 does not seem to be present, delaying initialization

PROBLEM
You receive random errors failing to initialize your network card at boot time or during manual restart that look like the one below:

$ifup eth0
via-rhine device eth0 does not seem to be present, delaying initialization.
$

SOLUTION
There are a couple of potential solutions to this issue:

• Missing 'HWADDR' variable from '/etc/sysconfig/network-scripts/ifcfg-eth0'.  Try adding "HWADDR=01:23:45:67:89:AB" to '/etc/sysconfig/network-scripts/ifcfg-eth0' and rerunning 'ifup eth0' command.
   
• You could try renaming the interface you have to the one the system is currently configured for and regunning service network restart.  An example of renaming a wireless LAN card is below: $ cd /sys/class/net
  $ ll
  lrwxrwxrwx 1 root root 0 Jun 14 06:17 wlan1 -> ../../devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/net/wlan1
  $ ip link set dev wlan1 name wlan0
  $ ll
  lrwxrwxrwx 1 root root 0 Jun 14 06:17 wlan1 -> ../../devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/net/wlan1

To make the above change persistent across reboots, please see the following post Linux Networking: Persistent naming rules based on MAC for eth0 and wlan0.