Author: Bob Lin

Bob Lin, Chicagotech-MVP, MCSE & CNE Data recovery, Windows OS Recovery, Networking, and Computer Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com

Event ID 408: The DNS server could not open socket for address 10.0.0.84

Situation: The client keeps having a DNS problem. Sometimes, users have a problem to access some LAN resources.

Troubleshooting: We find there is Event error relate to DNS.

Log Name: DNS Server
Event ID: 408
Description:
The DNS server could not open socket for address 10.0.0.84.
Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.)

If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.

In checking DNS, we find one DC uses two IP addresses. One of IP address belongs to another DC. In the IPv4 Property>Advanced>IP Settings, we find there are two IP addresses. We assume they want to enter two DCs’ IP addresses but put them in wrong place. Removing another IP address fixes the problem.

DVMax can’t print to a shared DYMO Label Printer

Situation: The client has DVMaz v8.5 with two DYMO Label Printer on two workstations. The Label printer works on local computer. However, DVMax on other other computers can’t print.

Troubleshooting:

  1. Make sure the Label printer is shared for other computer to access it.
  2. Make sure the DVMax “This Station has an attached Label Printer should be checked” and “Shared with other stations” are checked in Setup Label Printers. Please refer to thispage:

Can’t print to label printer on DVMax – Chicagotech
www.chicagotech.net › WordPress › 2019/08/12 › cant-print-to-label-print… 3. Make sue you installed the shared Label printer on client workstation.

4. Make sure you have correct DVMax Label printer settings. Please refer to this post:

Can’t print to a shared label printer in DVMax – Chicagotech
www.chicagotech.net › WordPress › 2019/08/12 › cant-print-to-a-shared-l…

DYMO label printer doesn’t work on DVMax

Situation: The client use DVMax v8.5. None of DVMax can’t print to DYMO Label printers including the computer direct connecting to the label printer.

Troubleshooting: We follow this post and check all settigns, but can’t fix it:

Google Custom Search Can’t print to label printer on DVMax – Chicagotechwww.chicagotech.netwww.chicagotech.net/…/08/…/cant-print-to-label–printer-on-dvmax/

Later, we find an error message on the DVMax Label printer setup. It says: the label printer is on, but there are over 211 printing jobs in the queue. We close the DVMax on the server and restart it. That fixes some problems. But most computers still don’t work. Finally, we restart the DVMax server. That fixes the problem.

Can’t install 32 bit add-ins on Outlook

Situation: The client uses Office 365 and has a 32 bit add-ins. They have a problem to install the add-ins in new Dell computers.

Troubleshooting: 1. The Dell computer comes with Office 365 64 but.

2. When they install the Office from Office 365 website, it installed 63 bit automatically.

Uninstall Office 64 bit and re-install Office 32 bit. That should fix the problem.

Can’t access the FTP server with this “Could not read from socket: ECONNABORTED – Connection aborted” error.

Situation: The client has a FTP server using Syncplify.me. Some of FTP users have a problem to access the FTP server with this “Could not read from socket: ECONNABORTED – Connection aborted” error.

Troubleshooting: It could be FTP over TLS issue. try to use Only use plain FTP.

Can’t establish FTP with GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.

Situation: The client has a FTP server using Syncplify.me. Some of FTP users have a problem to access the FTP server with this “GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated” error.

Troubleshooting: It could be FTP over TLS issue. try to use Only use plain FTP.

Event ID 4105: The Remote Desktop license server cannot update the license attributes for user in the Active Directory Domain

Situation: The client has some Windows 2012 R2 servers as RD servers. The RD Server keeps having some problems and getting this event ID:

Log Name: System
Source: Microsoft-Windows-TerminalServices-Licensing
Event ID: 4105
Level: Warning
Description:
The Remote Desktop license server cannot update the license attributes for user in the Active Directory Domain “chicagotech.net”. Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain “chicagotech.net”.
If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.
If the license server is installed on a domain controller, after you have added the appropriate accounts to the Terminal Server License Servers group, you must restart the Remote Desktop Licensing service to track or report the usage of RDS Per User CALs.
Win32 error code: 0x80070005

Troubleshooting: