Unable to connect to dns server windows xp

Report abuse. Details required :. Cancel Submit. As it says in the first pic connection 5 , the ip is invalid. Give it an ip. Which is within the valid range of your modem. Or put it on auto I would also change wireless from worldwide, to something else, if youre using wireless. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Nirmal S. Hi Gerhart. Access from a Windows Server R2, Windows 8. In this case, you receive an error message that resembles the following:.

You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Logon Failure: The target account name is incorrect. The SPN may be incorrect because it's registered for an old server.

That is, the first component of the SPN will always be the user supplied name as in the following example:. To resolve this issue on a file server that is running the SMB version 1 protocol, add the DisableStrictNameChecking value to the registry:. If you want to still give "alternate names" to servers, you can do so with the following command:.

Not recommended We do not recommend that you resolve this issue for a file server that is not Windows-based by typing the following commands in an elevated Command Prompt window on a Windows-based computer. If you use Windows Clustering, install the hotfix for down-level clients in which Windows XP or Windows Server computers cannot connect:.

Delete any existing File Server network connections. To do this, type the following command, and then press Enter:. To stop the network trace in an unsuccessful scenario, type the following command, and then press Enter:. I am in search of what these values really mean. To those of you that have followed this thread, I find it interesting that MS posted a KB on this very subject about 8 days after my first posting.

However, they fail to explain what each value means. I know setting it to 0 allows DNS to be administered from remote systems and the console. I do know that other values can restrict to only the local console, to only remote systems, or restrict all. I cannot find the documentation on which values those are. They are binary values, so combining allows you to restrict all.

Just so everyone knows, those dnscmd commands simply create the following registry values. You could just modify the registry and restart DNS. I prefer the dnscmd method as meddling with the registry could be dangerous. This is provided AS-IS with no warranties or guarantees and confers no rights. I know I wasn't able to answer dbowers question.

I wish I had the answer. Unfortunately, this has been publicly undocumented by Microsoft. I also attempted to find out what each value means for RpcProtocol and am left with questions. I don't recall what 7 means and technet doesn't list it as well. According to technet, the rpcprotocol command for dnscmd is as follows.

Thanks for the update. I'll see if I can find anything on this privately. Googling around, I couldn't find anything publicly, but I'm a little short on time to spend to look for it at the moment. However, based on the article you posted, my initial feelins is that setting it to "7" enables RPC over Named Pipes because it was disabled on Windows Server R2.

I am wondering if setting the rpcprotocol to 0x7 is the same end result as 0xFFFFFFFF, unless there are other protocols beyond 0x4 that aren't documented. Office Office Exchange Server. Not an IT pro? Windows Server TechCenter.

Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums.