Windows 7 – There are currently no logon servers available to service this request

A Windows 7 laptop (on WiFi) that was previously added to a domain no longer authenticates users.  The error reads “There are currently no logon servers available to service this request.”  Clicking on Network ID to run the Wizard does not resolve the problem.  Installing the latest Windows 7 updates also doesn’t do the job.  For the Wireless network, the appropriate DNS server IP is configured but still nothing.  Removing the laptop from the domain and then adding it again does not work :/  Enabling “Always wait for the network at computer startup and logon” policy under Computer Configuration/Administrative Templates/System/Logon in the Group Policy and nada.  Running the commands gpupdate /force and ipconfig /flushdns also fail.  At your wits end you run regedit, find the HKLM\Software\Microsoft\Windows\CurrentVersion\Run registry key and add a string value %comspec% /c netsh wlan connect name=”<profile name>” to make sure that the WiFi network is available before logon.  To your dismay, this also does not work.  Finally, after digging through countless posts you opt for a simple solution buried deep in the confines of the internet.  You delete the WiFi profile and reconnect, then magic happens.

#there-are-currently-no-logon-servers, #windows-7, #windows-7-there-are-currently-no-logon-servers-available-to-service-this-request

Polycom IP 650 Boot Loop

In an organization using Adtran Netvanta 7100 PBX, the system firmware on the Netvanta 7100 was updated to R11.4.2.E.  After the Netvanta 7100 firmware update, changes to Voice User Accounts could not be made unless the phone model was updated.  In this case, 2 more line keys needed to be added on a Polycom IP 650 phone.  The phone model was changed to ADTRAN/Polycom IP 650 from the drop down menu under IP Phone Configs.  The changes were then applied successfully.  However, upon rebooting the phone, changes made to the phone’s configuration were not taking place.  Reset to Default – local configuration had no effect.  Reset to Default – Device Settings placed the phone in a reboot loop.  Ultimately, reviewing the MAC ADDRESS.cfg file for that voice account and comparing it to that of a working unit, revealed that it was missing an entry.  In the MAC ADDRESS.cfg file, under CONFIG_FILES=”polycomboot.cfg, customer-sip.cfg, customer-sip-MAC ADDRESS.cfg, customer-sip-spip650.cfg, adtran-sip_40x.cfg, xxxx-MAC ADDRESS.cfg”/> it was missing SIP.cfg.  Once sip.cfg was added between quotes the phone booted normally and changes applied to the phone’s configuration were in effect.

#adtran, #boot-loop, #netvanta-7100, #polycom-ip-650, #sip-cfg, #soundpoint-ip-650, #voip