atari37

Well, It looks like my production servers are doing the same thing so I'm guessing the ePO policy is what's blocking the ping. Windows firewall is not turned on. Another interesting discovery I made was that, I can ping the test server by IP address and not by name from a PC that's not on the same domain/dns server. Could this be because the PC and Server are not on the same subnet?

I have a Server configured as the Active Directory Server/DNS/DHCP. Server as far as I can tell works perfectly fine but I can't seem to ping the only workstation I have on the domain (either via IP or PC name). The PC is however on the domain, I'm able to ping the server from the PC, I'm also able to get only without any issues but I just can't ping the PC from the server with is odd. Both the server and the PC are on the same DNS (which is the actual server). The DHCP server (also the actual server) assigned an IP to the PC so what's going on here? Any ideas? This is a test environment so it hasn't been widely implemented yet?

Is it possible to sort all directories on Windows XP by details? I know I can open a window, go to view and click on detail but is there a setting to apply this behavior to all directories?

Does this server point to itself (and itself only) for DNS and/or WINS? Yes...

If that is the case, then make sure you take VERY frequent backups of the system state on that DC, and keep them somewhere safe in the event you need to do a restore of your AD. Also, if you only have one single DNS server, a failure there means a complete failure for lookups everywhere (but since it's also the only DC, you probably have bigger problems if that server fails anyway - and you'd need your system state backup to restore in this scenario). I am presented with a minor but annoying issue. 1. AD runs very slow on the server (I click on an OU and it take about 10-15 to open) Any Ideas?

Since I _know_ you aren't configuring your domain with only one single DC, you can install AD integrated DNS on that second DC you just dcpromoed . Single points of failure are bad, especially in AD - never, ever have just one DC if you can avoid it. Your DNS server is using the root hints to look up any unresolvable DNS names - this will work by default, but if your ISP provides you with a caching DNS server you can use as a forwarder, this will likely be a better option long-term. And you can do this with your current setup, but I strongly suggest another DC/DNS server. Thank you...good stuff. I currently have one DC for my domain and one DNS Server. I don't have another box to run dcpromo on.

Not exactly, but not the way you're thinking either. An AD domain has basically two states of operation, DNS is working fine, and all hell just broke lose. Hence the only DNS server the client machines are to use is the internal one running on your DC (192.168.0.135). Do Not configure a secondary DNS server on the client machined unless you happen to enjoy random connectivity and logon issues. Also do not configure a secondary DNS server on your DC as it will only cause the machine to loop through the DNS timeouts twice before failing anyway (if using the machine's IP), or worse fail to identify itself and refuse to authenticate anything including itself (if using an external DNS Server). Your DC will also use only itself for internal DNS lookups, and the forward lookups for external domains (e.g. the internet) to the DNS servers listed in the DNS forwarders list. Also Make sure if the DCPROMO wizzard configures your DNS server that you are not forwarding to yourself (at 192.168.0.135) if you use the loopback ip address (127.0.0.1) for the primary DNS server on your DC. <- This one drove me nuts for a week once trying to figure out why webrowsing was lagged badly on a T1) *Sigh* By default if DNS forwarding is enabled, the DNS server will forward all external domain lookups to the internet root (backbone) DNS servers (Which is the configuration I usually use), or you can add your ISP DNS servers to the forwarders list ... that's personal choice. First of all, thanks to all the contributed. I finally got this thing working. So, I was thinking about configuring a secondary DNS for the Server and configuring the client with a secondary/alternative DNS but you're saying not to. What happens when the primary DNS server fails? Also, I haven't listed any IP's in my DNS forwarders so how am I getting online without an external DNS? My goal is to setup AD/DNS (which I have) on the same box without using my ISP's DNS servers. So, if I'll be able to get online (internet) without a secondary dns and without using my ISP's DNS then this will be golden.

nslookup returns: Default Server: localhost Address: 127.0.0.1

Your DC and your machines all need to use the internal DNS server ONLY. Do _NOT_ use public DNS servers in your AD setup, unless you want DNS lookup problems. So, someone told me I needed an external DNS that's why I was using OpenDNS to configure my dns server. I have uninstalled both AD and DNS and re-installing with the following info. I will let you know if that works. Both servers are on a router with an internal DNS of 192.168.0.50, Server has an IP of 192.168.0.135 and the client XP box has an IP of 192.168.0.131. So, are you saying that I don't need an external DNS for the server to function properly? Thanks

I am aware of the IP classes and both Server and XP have internal IP addresses. This issue seems to deal with the DNS setup...I'll troubleshoot some more.

I did that already but it's not working. Perhaps i'm doing something wrong. I named my dns "mydns.local" but i'm unable to ping it. Could that be a clue as to what's going on? Before I run dcpromo, I went to the tcp/ip and added a static ip but didn't fill out the dns sesttings. After Active Directory and DNS were setup, I went ahead and added a DNS server 208.67.222.222 (which is from opendns). I then went to my xp pc, which already has a static IP and added the same DNS (208.67.222.222) as the server. I have a feeling i'm missing something but i'm not sure what. Any help will be greatly appreciated.

Can someone let me know if I'm missing something in the following steps? 1. I did a complete install of Server 2003 and gave the server a static IP address (dns address was left blank) 2. I run dcpromo to install Active Directory, which also setup a DNS Server. 3. I went to active directory, added an admin account, created an Workstation OU and added a Windows XP PC to that OU. 4. I then went to the XP machine to join the Domain but I'm getting the following error... What am I doing wrong? I just want to make sure I can join the domain before I create policies and such. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain mydns.local: The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.mydns.local Common causes of this error include the following: - The DNS SRV record is not registered in DNS. - One or more of the following zones do not include delegation to its child zone: mydns.local local . (the root zone)

I am currently installing Windows Server 2003 primarily as an Active Directory Domain Controller. I also need a DNS Server so my question is, can I make this same Server a DNS Server? Thanks

I have a notebook running Windows XP pro. The only account on the PC is the Administrator account, whoever setup this PC didn't document the password and has left the company so I'm trying to figure out a way to get in and change the password to prevent refreshing the drive. Can I somehow use the Window XP media to accomplish this?

I'm trying to figure out how my network drives at work were setup. I have a server 2003 with 1 local drive and 3 volumes (E, F, G). Now, in E: and G: we have a couple of shared folders. On the clients end (windows xp), the shared folders show up us networked drives with it's own drive letters? My question is how was this accomplished? I want to try this at home. I should mention that I know how the drives are mounted onto the clients side...What I want to know is how the shared folders in Drive E: shows up as a networked drive on a client. ----------------------------------------------------------------------------------------------------------- Nevermind, I actualy figured this out myself...Much easier than I thought.

Thanks guys...Good info to add to my knowledge bag. She'll be fine, I created a local account just in case...I tested IcemanND's suggestion earlier without any issues.

Too bad I can't test any of these myself. I'm setting up this notebook for a user going out of state, she really doesn't need to get on the domain but I figured I set it up that way in case she needed access to the network drives. I guess I could ask her to log into the domain to see if it works.

Is it even possible?

Hi guys, I have a notebook setup to connect to a domain. Will any user with a domain account be able to login to the domain from a home? In other words if, the user inputs the domain credentials and select the right domain from the drop-down, can they login?