Main Forum > General Computer Support

This Dns clinet error problem haunts me. Is there a real fix?

<< < (19/20) > >>

jraju:
Hi, Boggins and Samson,
                                     So, both the two solutions try posted related to xp machine. I will do that. It seems that some routers have not made some changes to the windows 7 system, as it is entirely structured one from the xp, which does not support ipv6. So, the xp machines, which may lack security concerns, excels in all other things, like gif animation and it was a darling for all.
                                           While changing the system, it was expected that all the vendors also would give some kind of change thro software update. But , dlink totally lacks in. Ofcourse, firmware updates  are attempted by dlink, but not enough to last long. I asked about the solution regarding this as given as a cause,to link representative.
Enable the spanning tree portfast setting in your router
in the link below
https://social.technet.microsoft.com/wiki/contents/articles/3336.event-id-1014-microsoft-windows-dns-client.aspx
He says that it was already done in the latest version of dlink router which i possess now.
Moreover, the server settings and stand alone have something in common , which affects both of them, if a service or improvement is lacking in either of the two.
Net result in annoying issue of internet loss to the users.
Is there any restriction on the number of devices that one could connect? For eg, i may use pc and 2 smartphones on wifi. Would there by some limitations , so that this error crop up. How to know the no of device a router or connection has? Since my router supports 4 lan connections, (eithernet connections), iassume  that it would support atleast 4 devices support.
I have attempted all repairs, but how could i accomplish the last solution of making same channel selection in the router.
I have done the b+g+n to G only connection in the wifi settings in the router, but do not know, how to do the last part of it, in the  network and sharing  settings in the ipv4 properties. Could you say? Of course, i am having wifi router , and my pc is connected thro ethernet. There ia no showing of any wifi connections in the pc and only local area connection.

jraju:
Hi, boggins, After your solution of registry removal of profiles and signatures, which listed 2 settings of network, network 2 in the registry keys, the reboot restored only one network, which i actually have, the problem persisted.
Then i logged in to hidden admin account, thro gpedit.msc and tried to change the network id from business to home.
Then i just gone thro, each item of gpeditor.
AS i browsed thro each item, there were lot of unconfigured entries, almost all in the gpedit.msc, which will override anything in computer settings .
i stumbled upon a registry entry netlogon. As the term was somewhat related to logon, i just read and enabled the first two entries from unconfigured, which is attached herewith for easy reference.
It had stropped disconnecting, after enabling the first two, with the last chance of trying before reinstalling once again.
Now , it appears that it no more disconnects while restarting. i have not tried shutdown chances. I tried those on reboot and there was no disconnect of dsl.
MVP does not touch their answers on gpedit.msc in any of their replies.
If your router manufacturers do not know , the computer settings, they would not fix this problem.
Let us see some more attempts.
I am enclosing those settings , so any one may try in his own risk, after creating system restore point.
The main directory is  gpedit.msc ,in run command
Computer configuration>administrative templates>System>netlogon>dclocator dns records folder and the first two entries as shown in the first and second settings


jraju:
In continuation of the above , please see the description part of the two settings:
The Domain Controller (DC) Locator APIs return IP address of the DC with the other part of the information. Before the support of IPv6, the returned DC IP address was IPv4. But with the support of IPv6, the DC Locator APIs can return IPv6 DC address. The returned IPv6 DC address may not be correctly handled by some of the existing applications. So this policy is provided to support such scenarios.

By default, DC Locator APIs can return IPv4/IPv6 DC address. But if some applications are broken due to the returned IPv6 DC address, this policy can be used to disable the default behavior and enforce to return ONLY IPv4 DC address. Once applications are fixed, this policy can be used to enable the default behavior.

If you enable this policy setting, DC Locator APIs can return IPv4/IPv6 DC address. This is the default behavior of the DC Locator.

If you disable this policy setting, DC Locator APIs will ONLY return IPv4 DC address if any. So if the domain controller supports both IPv4 and IPv6 addresses, DC Locator APIs will return IPv4 address. But if the domain controller supports only IPv6 address, then DC Locator APIs will fail.

If you do not configure this policy setting, DC Locator APIs can return IPv4/IPv6 DC address. This is the default behavior of the DC Locator.
2.Specifies whether the computers to which this setting is applied attempt DNS name resolution of a single-label domain names.

By default, when a computer (or the DC Locator running on a computer, to be more specific) needs to locate a domain controller hosting an Active Directory domain specified with a single-label name, the computer exclusively uses NetBIOS name resolution, but not the DNS name resolution, unless the computer is joined to an Active Directory forest in which at least one domain has a single-label DNS name.

If this setting is enabled, computers to which this policy is applied will attempt to locate a domain controller hosting an Active Directory domain specified with a single-label name using DNS name resolution.

If this setting is disabled, computers to which this setting is applied will attempt to locate a domain controller hosting an Active Directory domain specified with a single-label name only using NetBIOS name resolution, but not the DNS name resolution, unless the computer is searching for a domain with a single label DNS name that exists in the Active Directory forest to which this computer is joined.

If this setting is not configured, it is not applied to any computers, and computers use their local configuration.

Boggin:
That's deeper than I've ever gone into Network settings, but gpedit.exe is only available to Pro versions of Windows and above, although there are steps to enable gpedit in Home versions of Windows.

So is everything fixed now ?

jraju:
Hi, Boggins,
                    I have not gone deep in to it. Or i do not know anything of the settings before. I just opened gpedit.msc when i want to log in as admin to make sure changes .
                   There i just clicked something which suddenly shows that inner settings page. Call it a fluke or chance shown to me . I read and it was related to ipv4 and ipv6. I thought of reinstall.  So, just did not bother about anything. Just enabled the first two. I decided to leave others as it is . Restarted the pc and found that there was no dsl disconnect.
                        I do not know, what i have done and i have not enabled any special log. I do not know, where are the logs of these changes in the event viewer.
Here, i just gone to the gpedit once again, and click each item to find enabled . I could have just opt filter or choose all settings in the page. i did not know. I was opening one menu after the other and found that it is in the system tab on the administrative templates. Then i wrote to you about those details.
                  Lucky find! Dlink routers would have changed to other routers because of this persistent problem. How to know those settings? The clue is the hidden admin login i tried which gives me the group policy editor page.
                       I tried restart switch for one or two times and the internet stays so the dsl .
After a few more log on , i will tell exactly whether the problem is solved or not.
i do not know that there is net logon service and it is controlled in gpedit also.
messing around the dependencies of windows dns client services have almost led to fatal errors, even to log in . But by somehow, switch the users and log on to the user account.
                       The first point is deleting the network2 profile with your registry tweak. When it shows only one profile, i thought of doing anything before the last resort to reinstall the windows .

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version