Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I've read several messages on how to resolve this, but I still have not been fortunate to effectively apply it to my system.
I have a Windows Server 2003 (Standard) server, with one Windows XP client (yep, just giving myself a shot at learning a little Network Administration), using a D-Link router for my wired network connections, via high speed cable ISP. I already configured the Active Directory, basically using default settings provided by Windows during configuration.
Can someone please tell me how to properly configure my TCP/IP settings in the server, as well as in the client PC?
Any help will be appreciated. Thanks.
NT

Well, first of all I need more info to be able to help you and then I want to mention this fact that, usually it takes a while for windows 2K or 2K3 to load Active Directory (especially when there is not DHCP client).
Alireza

I have the same problem, and I use Local profiles. Users take too long to login to the server. Now,we'll need to have roaming profiles because different users use different computers in different shifts.
How to I go to fix the problem? do I need more memory in the server. ( I currently have 512 MB)or this is a Network problem?
thanks
zurnch

Set the DNS of the clients to the ip address of the server computer. That will speed up logon time quite a bit.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |