Hi, Pl. helps me out with this. I have following Hardware and software installed. Server computer with Windows 2003 Enterprise Server as a domain controller with a domain name test.local with static IP address 192.168.1.250. and NETBIOS name as TEST. IBM ThinkPad laptop with windows XP Professional with static IP address 192.168.1.251 and NETBIOS name as TEST01 with DNS address 192.168.1.250 Linksys Router acts as a Gateway, DHPC server and connected to ISP. On the server in DNS console the forwarders for this DNS server are two IP addresses provided by ISP. The DNS server is functioning perfectly. I checked up with nslookup. In nslookup I am getting default server test.test.local with address 192.168.1.250. Also it resolves different web sites like yahoo.com, Microsoft.com, google.com even it resolves Test01 laptop. On the server I created a user Test123. My issue is: If I logged in as administrator from the IBM laptop, it allows me to access Internet where as if I logged in as Test123 it won’t allow me to access Internet. Is there a way the test01 user from IBM laptop can access internet? In Test123 user nslookup resolves web sites and default server. My second issue is: I am getting message “The local policy of this system does not permit you to logon interactively” while try to login as Test123 on server and it won’t allow me to log in. Is there a solution for this? My third issue is: If I dynamically configure my IBM laptop from DHCP server which is linksys router then I am able to login as administrator and Test123 but not able to access network resources from server and Internet. I want to configure my laptop as Dynamic IP address. What to configure DNS on server side so that without the server as DHCP server and linksys router as DHCP server the users from dynamically assigned computers can use network share and access internet? Thanks a lot for any help?

First of all, excuse my very poor english. The solution you look for might be this one: (please understand that I am an admin of a Windows 2003 Server in spanish lang, so I have to translate the directions I give to you; may someone can re-write this right?) - I think you should forget the client and go to the server, as an admin. - "Issue one": First of all let's be sure of the right configuration of the internet access _for your users_ and that should be done going to Control Panel, Network Connections, Select Internet Connection, Properties, Options tab, Check On Show Connection Progress, Ask Name and Password and Include Windows Session Domain or something like that in english (I hope). Accept all. Please be sure of login as root and do connect on the account, then check "Store this username and password" and "Only Me" on the zone. Then connect to accept that change. Disconnect if you want. Now, when a user wants to use that connection, the server will ask name, password and domain (if necessary) to that connection in particular, so the user must know the internet account data for using it, thats pretty useful in some environments and awful on others, I don't know what's yours. There is another way. But i'm tired. - Then let go to "issue 2": It's quite simple, just needs admin work; login as one. Go to Admin Tools and open Local Security Directives (or something like that in english). Select User Rights Asignation (or similar in english); on the right side of the window, right click on "Allow local session" (or...) and add user or group that you want to log locally on the server (watch out your decisions, anyway). By the way, for sec reasons you may want this one too: go a little down to "Have access to this machine from network" and take out the _group_ All (or All Users) that allow _anyone_ to have access to your services or log on it. Please _don't_ take me wrong, but it surprise me that you can work out a DNS, router and DHCP server and not Administrative Rights. I wonder how hard and bumpy you learn. I might be very wrong over all this, so don't feel offensed. - "Issue 3": I quite don't understand your english ;). It must be worser than mine for me to catch it, man! XD But as I could understand, you are up now since issues one are two must be solved. I gave a good read to that and I possibly understood this: You are confused on how to achieve what you want :) And maybe you want to replace the DHCP server with a DNS, but you want to _have_ dynamically assigned PC's; thats what I call paradox, only because I am a very bad, bad child of mom and want dynamic IP's from DHCP Server. For doing what I understand you want, you should design a namespace for Active directory... and... Why in the world you don't evolve your server to GNU/Linux for Christ sake?!. Apparently your IP Routing is not active either, and your actual interaction between DNS and DHCP appears to be unnecessary... the possibilities are too much since you don't give enough data about your network and I am tired of _guessing_. Is your firewall on and allowing what you want to do? Is your client configured to access your router or proxy, not internet directly? Are your network shares allowed to accept your clients, let's say: the group of your user client? Are the gateway (if there's any; _might_ be one) configured to accept your particular client? (sounds stupid, but I have seen _so_ much...) Is your internet access a ppp or pppoe configured on-demand or not, or is always up? Is Windows 2003 Server the best you can have or you'll like to try GNU @ last?. If I missed something... I don't know, you might find me again. Or someone wiser. > Thanks a lot for any help? Thank you for your patience. -What's GNU? -GNU's Not Unix. -I asked what _is_ GNU, not what's not; but I assume that negative affirmation is enough for a dork isn't? -Is not.

Hi runner_crashed, Thanks for your help, Solved first and second issue. Still third issue is pending. Let me give you detail. The linksys router is the DHCP router and W2k3 server is the DNS server and if the IBM laptop get IP address from linksys router then I am not able to accesss network drives or internet if I login to the server. Is there any thing wrong in the configuration of DNS on the server side. Pl. Help me out.

Know that my directions in english lang (and my use in general) should be wrong because I'm a spanish lang W2003S user. Any corrections are welcome. vianuroberet, I don't know if the "linksys router" is a broadband internet router or another kind, anyway, I will try to cover all cases: If I was you (but isn't _me_ asking here), I'll set your router to forward DHCP requests to the W2K3 (obviously converting W2K3 in a DHCP server, centralizing); then set all your clients DNS settings to point to the 2003 server (in the DHCP settings); then set the W2K3 DNS to forward unanswered requests to the router. Do you have a DHCP Server on W2K3? When router starts forwarding DHCP requests to your server, you'll need it. Be very aware of what changes you'll do (write them to be able to undo them). Remember to set your network IP's range on the W2K3 DHCP Server. In this case above you should get all kind of network access, including shares of course, and Internet access for your clients directly from the router, means: if your server's down your internet connection is still up. Take good care of your router security conforming what you and your clients needs. _If otherwise_, what you want is share the internet through your W2K3 instead of your linksys router, possibly you need to set up the router has DNS enabled, then the W2K3 should be able to connect to the internet. You will then need to enable Internet Connection Sharing on the W2K3. Then setup the clients to automatically find IP address and DNS. If that doesn't work, try setting the DNS on the client to the IP address of the W2K3. You know, I will never have great Windows experience over DNS's (more over GNU/Linux instead) so Active Directory is some kind of black magic to me. If AD is necessary for something, I just will miss that completely. _If, in other case_, you need forced access to DHCP through your router, because of a complex network, and being logged by your W2K3, I will jump over that and wait for you to say so, and to give me some sort of network map, necessary for this. Anyway you can consult your Windows 2003 server's help and tech support on your main menu, searching "DNS with DHCP", that should answer better than me. Note: If nothing of the above couldn't help you, and you have the time, I will recommend you reading Justin Thyme and Jon's answers into this other forum: http://www.computing.net/windows2003/wwwboard/forum/1926.html See what's the problem of Steven and see if their answers covers some of your expectations. Thanks for your patience. "Sometimes I think God is teasing me... just like he teased Moses in the desert." Homer Simpson.