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 *
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 *
No comments:
Post a Comment