atari37

The option to prompt with options is already checked. What could be causing it to not work.

Usually, when you plug in a USB device with pictures, Windows pops up a little window with options on how and which application to open the pictures with. Where can I find this config in Windows?

I deactivated the scope but it was still grayed out. Do I have to delete the scope and recreate it? This will be a major headache.

From MS help docs: Make sure the Access database is set to open in shared mode, which is the default setting. How? On the Tools menu, click Options. On the Advanced tab, under Default open mode, click Shared.

I just realized that my DHCP is using the wrong subnet (255.255.0.0) instead of (255.255.255.0). The option to change this is grayed out, it's of course assigning the wrong subnet to the workstations as well. How do I correct this? Thanks

Thanks to all who helped...eyeball, I had the secondary DNS under server options and that wasn't working. I moved it to scope options after I read your post and that made it show up under ifconfig so I added the DNS domain name of the secondary server and all is well now. Again, thanks to all...

Not so much renewing the IP...I know the lease is not up yet but since I'm using DHCP, I would thing that rebooting the server will update the dns via DHCP.

It shouldn't matter that the secondary is not AD-integrated. All you're doing is telling clients to send requests to it. ipconfig /flushdns will clear out the resolver cache, and /registerdns will tell clients to send their info to a DNS server (your secondary server won't be able to register these connections itself). You need to do ipconfig /release all and /renew all in order to enforce the picking up of new settings (like DNS server addresses). As I previously mentioned...I did do the release and renew as well without any luck. Rebooting the workstations should take care of this, no? Even if this worked, it will defeat the purpose of trying to automate this process. I have way too many workstations to be doing this manually.

I tried this before leaving for the day but it didn't work. Did you try doing: ipconfig /release all ipconfig /renew all to force the changes to be picked up? Are you sure the workstations are DHCP clients (ie - not configured with static DNS settings)? Yes, the workstations are DHCP clients using DNS configured during AD setup. This secondary I'm trying to add however isn't AD integrated. I did the above and a couple others like ipconfig /flushdns and ipconfig /registerdns. Even rebooted workstations a couple of times without any results. It works fine when I manually add the secondary dns.

I tried this before leaving for the day but it didn't work.

The primary DNS is using DHCP to assign IP addresses however, the secondary DNS I'm trying to add doesn't have DHCP...Can I still use DHCP to complete this configuration? Do I add the secondary DNS server under the server options?

Follow cyberpyr8's instructions...It looks like you might have the "user" group in the "allow logon locally" setting. Remove it and create another group or use the power user group for those you want to give access to.

FYI: I solved this issue this morning. The idea to use the secondary DNS as a forwarded sounded a little weird but I gave it a try anyway. It didn't work. I created a zone for the secondary DNS...I had a record of the secondary DNS prior to things not working but after creating a zone for the secondary DNS, things started working 100%. Both DNS Servers work together now.

Is it possible to send text or short messages to all domain users via Active directory?

Is terminal server installed? Perhaps you can disable all user accounts except admin accounts? Is this server on a domain or standalone?

Do you have terminal server installed on this server? A regular user shouldn't be able to log into the server if terminal server is not installed unless the users account is also acting as a service account. Do you actually have users who can login?

I believe I found the setting in AD under computer configuration >admin template>DNS clients. I enabled DNS server and added both primary and secondary as such: 192.1.2.3 192.1.2.4 but it doesn't seem to be working. I rebooted my workstation but it didn't update the DNS servers. What am I doing wrong?

Is it possible to add a secondary DNS server to all workstation via AD or do I have to script it? I have a new DNS server I will like to use as secondary for my workstation but I don't feel like walking to each users desk. Doing it via AD will be the ideal way.

Yes - you have to configure the DNS forwarder servers. Open the DNS MMC snap-in. Find the primary DNS server in the list. Right-click on it, choose properties. Open the 'forwarders' tab. Add the secondary server's IP address in the list (you can specify a particular domain for forwarding to servers if you're on 2k3). Ensure that 'disable recursion' is NOT ticked. Don't set the query timeout too low. Default is 5 seconds. If you have network issues between DNS servers, you may want to consider increasing this a little to see if it helps. I know how to do this...I just didn't think I had to set my secondary as a forwarder on my DNS server for this to work. I will try it out tomorrow. Thanks

The primary DNS is AD-integrated, the secondary isn't. Both servers however act as authoritative zones. The primary DNS knows about "good", good is however not on the AD, it's on a different subnet. nslookup returns: server:nameofprimarydomain address:192.1.1.1 non-authoritative answer: etc.... One thing I haven't tried yet is making my secondary DNS server a forwarder in my DNS configuration, I didn't think this will be necessary since I'm telling the workstation to use a secondary DNS in case the primary fails. Amazingly, if I turn off my primary DNS server, secondary picks up and vise vesa but they don't work together. The primary is running server 2003 and the secondary is RedHat. Both of these DNS servers know about each other by way of host records. I don't want to write too much to prevent any confusion so I'll try to keep this short... Web Server is known as good on one network (subnet-primary DNS) and known as good2 on another network (subnet-secondary DNS). I should be able to get to this website (internal website by the way) with either good or good2 since both my primary and secondary servers have records of both names. Am I making any sense? In windows configuration, I can get to "good" by using my primary in the first entry...I can get to it by typing good2 if I use the secondary dns as my primary. All I want is to have my primary act as a primary and secondary act as a secondary...if primary can't resolve, send the request to secondary but that's not happening. I have to use one or the other and not both...And yes, I do need both names to resolve.

Oh, I already tried that...didn't work. I believe there's more to it than.

That was what I was hoping the issue was...How do I do that?

Get a password reset software...

Is this a network or local printer? I've seen this error before...I had to manually uninstall and reinstall the printer.

Both primary and secondary function okay. I have a Web Server which call good, there's a record in my Secondary DNS server for good. Now when I open change my Windows configuration to use the secondary DNS as my primary and type http://good in a browser, the page loads okay. Problem is when I change the configuration back to primary and secondary DNS, the page doesn't load anymore. I was under the impression that if the primary doesn't know about the web server, it will try using the secondary dns server (which knows about the web server) to find http://good...I'm I wrong? nslookup using both DNS server return the right output...it just seems like the secondary doesn't kick in when the primary can't resolve a name.