Windows Echo & Microsoft account not logged in

Windows has an echo, the first reaction is the Dolby sound effect secretly behind me open the Living room mode (after looking at the next and no this mode, something ... ）。

Again I tried to open it and found that the network could not connect, so I uninstalled directly, but Echo can not solve.

I found out later that it was my microphone and stereo mix that made the link.

After the ban, it will be solved.

This time I want to download it back to Dolby Access and find a connection to the Microsoft store network and find a number of ways to do it online (even I try to reset the entire system network).

After tossing and leaving records ~

Microsoft's login program has a call to IExplore, and if set up the proxy will not open the landing page.

Inetcpl.cpl can quickly open the proxy interface and close it.

If you open the interface, but still unable to login account can continue to look down.

Can release and register NetBIOS name and restore LSP Network programming interface to default state

Nbtstat-rr
netsh winsock reset

If the problem is to see if it is a problem with DNS resolution, use this command to take effect immediately.

Ipconfig/flushdns

If not, you can try the initialization program, such as the App Store is wsreset.exe waiting for two minutes to automatically reopen the store.

——————

What is a WINS server? What's the role?
Sctrue0 comments 1374 People read 2010-08-15 23:03:17
WINS full name for Windows Internet Names Service, which is the Windows Internet Naming services. Like DNS, it is used to convert host names to IP addresses. But in the Internet to resolve hostname is DNS, in fact wins is mainly used in LAN to alleviate the network storm.
WINS is based on the NetBIOS name of the computer, so to understand wins, you must have a preliminary understanding of the computer name, NetBIOS, and NetBIOS names.
In Microsoft's system, any computer, whether or not networked, must define a character that is not more than 15 characters as the computer name, which is specified at system installation, and is randomly generated by the system, if not specified. Once set, it can be viewed and managed on my Computer-Properties-Computer tab (WIN2000 or above) or My Network Places-Properties-Identity Options Advant (WinME), and if the computer is in a network environment, the computer name must also be guaranteed to be unique across the network. The existence of this computer name is the precondition for implementing NetBIOS.
In the early days of the development of the LAN, in order to realize the network capability on the PC, MS and IBM developed a network protocol that, like the BIOS of the computer, would become the most basic network access interface, so the use of NetBIOS (network Basic input/output System) that name. MS is using the NetBIOS interface to develop the network server and the corresponding customer software, later, through the NetBIOS and network physical layer of the various specific interface NetBEUI (NetBIOS Extend User Interface) and developed successfully, become the enhanced version of NetBIOS. It directly controls the token Ring (token Ring) and the Ethernet (Ethernet) driver, so that it can only run on the LAN, the disadvantage is that it does not support routing, to communicate between large or routed networks, you must use a routing-based transport mechanism (typically TCP/IP) to supplement, Called NetBIOS over TCP/IP (NetBT), which means NetBIOS running on a TCP/IP basis. The NetBIOS name is enforced by computers WIN2000 the following, and the NetBIOS name is reserved for computers above WIN2000 to maintain communication in the network and computers below WIN2000.
The first 15 bits of the NetBIOS name follow the computer name, and the last one is added as a suffix to identify a service or application, so multiple NetBIOS names can be generated for the same computer name, and multiple services on the same computer can be registered to the NetBIOS name of the other computer. are distinguished by the suffix. The server service dedicated to file and printer sharing in WIN2000 is a typical example, with a suffix of octal 20.
It is not difficult to see that, even if there is no WINS server, as long as the NetBIOS-based host, they can manage themselves, the principle is as follows:
When host a logs on to the network, it sends a registration broadcast 6--10 to the network, declares its own NetBIOS name, ensures that the message is received by other hosts in the network, and if the name is the same as Host B, Host B will issue a broadcast packet that includes its own NetBIOS name, requiring host A to stop registering, Host A will issue a negative name registration (negative name registration) broadcast as a response, host a registration fails, and if no other host is opposed, a is successfully registered.
At the same time, other hosts on the network send a broadcast packet that includes their NetBIOS name to a, declaring their presence. This is in the form of the other host's network neighbor window after the refresh will appear that host a NetBIOS name, and host A's Network neighbor window also appears in the other host's NetBIOS name, that is commonly known as the computer name.
When host a contacts Host B, a broadcasts an address request that contains the NetBIOS name of the B host, and if B is online, it responds to host a by broadcasting a positive name query (positive name) message that includes its own IP address, and a can then use this address to connect to Host B ；
When host A is properly shut down, the name release operation occurs automatically, and other hosts can log on to the network with the name of host a, but when host a is not properly shut down, the host name will still be in the Network Neighbor window of the other host, and a "network path cannot be found" error message appears when you double-click: Host A
This "non-organized and non-disciplined" self-management, resulting in a significant decline in communication efficiency: each host in the landing and re-login network, will be sent to the network broadcast, and then all the host to send it broadcast, and then the host between the requirements of communication are broadcast in the way ..., every host is always yelling, Its huge data traffic will cause the network response to decline linearly, which is the most unacceptable network problem.
Therefore, there must be a "boss" for all the host's NetBIOS name and IP address centralized unified management and maintenance, NetBIOS client by directly with the "Boss" name registration, update, query and release operations, to minimize the amount of broadcast traffic. This "Boss" is the WINS server.
In wins, the NetBIOS name can be registered as a unique name, when it corresponds to an IP address, or it can be mapped to the name of a group, which corresponds to multiple IP addresses. So, to be precise, the WINS service should be called the NetBIOS name Service of WINS, which makes it possible to resolve NetBIOS name-to-address.
For a deeper understanding of wins, we also describe four methods (also called nodes, nodes) of the WINS name resolution specified by NetBT: ①nodeb: Broadcast Method (broadcast); ②NODEP: Equivalent Method (Peer-to-peer), Query directly in the WINS server; ③nodem: Mixed Method (mixed), that is, the Union uses NodeB and NODEP, the default is B;④nodeh: Another hybrid method (hybrid), same as Nodem, but NODEP by default. If there is no WINS server in the network, the system uses the B-node method by default, as described earlier, and if there is at least one WINS server in the system, the system uses the H-node method by default.
The NetBIOS client-the work flow that WINS clients register, update, query, and release to a WINS server is similar to the workflow of DHCP: It is done in the form of a lease-but it is more like the act of signing an employment contract between the boss and the employee. Examples of client A and B are still described below:

First, registration
When client a starts, it sends a name Query request (a contract) to the WINS server specified in the TCP/IP configuration, asks to register its NetBIOS name and IP address, and if WINS is online, it first checks to see if the NetBIOS name already exists in its own database. If client B has the same name as that, WINS sends three name query requests to B at 500 milliseconds to determine if B is still working, and if a response is received, a negative name registration (negative name registration) is issued to a. A registration fails; If a registration succeeds, the WINS server records the correspondence (re) in its own database and returns a successful registered message to the client, including a specified lifetime TTL (time to live)-- Its presence indicates that the WINS client is only a one-time maid, at which point the contract is successfully signed.
Once a three contact WINS server fails, it means that the WINS server is down or unavailable, and if no other WINS servers exist in the network, then back to the undisciplined, rogue state, WINS clients are given the opportunity to work in the "broadcast" manner described above.

Second, update
By default, the WINS server database update time (contract term) is the TTL of six days, and if the client does not issue an update request (to renew the contract), the name registration is invalidated (termination of the contract) and WINS will remove the employee from the roster, which is the function of the TTL.
Therefore, in general, the client will be the corresponding TTL value in the past 50% or three days to the server issued a name refresh request, stating that they are still working hard to continue to work, when the WINS server receives the request, the client is issued with a new TTL name Refresh response, That the contract is already re-signed.

Third, query
When a needs to contact B, it first checks the cache to see if the NetBIOS name of B corresponds to the record of the IP address, and if not, issues an IP query request for that NetBIOS name to the WINS server, which requires wins to respond to its IP address. If there is no WINS server response, or if a WINS server issues a "requested name Does not Exist" message (The requested name does not exist), the client is enabled for broadcast lookup, if it is still not responding, if there is a prior setting, Host A also to make the last effort, to find their own database file Lmhost, still invalid time, just give up.

Iv. Release
If WINS client a stops a registered network service or shuts down gracefully, it issues a release request that includes a-machine IP address and NetBIOS name to wins directly for a registered service or the NetBIOS name of a (requires rescission of the contract). After wins receives the request, it checks its database and, if WINS finds a corresponding record, sends a positive name to a (positive name release) message as a response, which includes the released NetBIOS name and a TTL with a value of 0. At the same time, the record is marked as released in the database, and the contract is formally lifted;
If WINS does not find the corresponding record or the NetBIOS name is pointed to another IP address, WINS sends a negative name release (negative name release) message to a in response. The contract cannot be lifted.
If a is not properly shut down, the name release message is not issued, obviously, the WINS server database will have a more "false" record, when B issued to wins a address request, WINS will still give B to the address information of a no longer exist, of course B can not be contacted by this address A, There will eventually be a timeout error. In the Network neighbor window of B, the presence of a only proves that a "has been".
High-level applications for WINS servers that are limited to post-spoke, WINS and DNS integration, WINS proxies, and management maintenance and troubleshooting for multiple WINS servers are only discussed later.
WINS is a cliché, I hope this article on the veteran of network management friends can restudying, to the beginning of humanely new network management friends can have some help. Please be advised to correct the matter.

Windows Echo & Microsoft account not logged in