WordPress database error: [Table './cpzee_ithut/wp_wfHits' is marked as crashed and last (automatic?) repair failed]SELECT MAX(attackLogTime) FROM wp_wfHits
WordPress database error: [Table './cpzee_ithut/wp_wfHits' is marked as crashed and last (automatic?) repair failed]SHOW FULL COLUMNS FROM `wp_wfHits`
Howtos and Tutorials from behind the firewall
In my last post I told you how to change the interface metric from command line if your Ptcl smart tv is not working on your pc.
In this post I will tell you how to change the interface metric from GUI.
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
You can configure the following for the IPv6 protocol:
By default, link-local addresses are automatically configured for each interface on each IPv6 node (host or router) with a unique link-local IPv6 address. If you want to communicate with IPv6 nodes that are not on attached links, the host must have additional site-local or global unicast addresses. Additional addresses for hosts are either obtained from router advertisements sent by a router or assigned manually. Additional addresses for routers must be assigned manually.
To communicate with IPv6 nodes on other network segments, IPv6 must use a default router. A default router is automatically assigned based on the receipt of a router advertisement. Alternately, you can add a default route to the IPv6 routing table. You do not need to configure a default router for a network that consists of a single network segment.
You can use a Domain Name System (DNS) server to resolve host names to IPv6 addresses. When an IPv6 host is configured with the address of a DNS server, the host sends DNS name queries to the server for resolution. AAAA (quad-A) resource records, which are stored on your DNS servers, enable mapping from a host name to its IPv6 address.
To enable DNS name resolution, configure an IPv6 router with forwarding enabled and a global prefix that is advertised to clients. You can do this by using the netsh interface ipv6 add route and netsh interface ipv6 set interface commands.
To provide communication between DNS clients and servers, you can configure the clients with the IPv6 address of the DNS server, or you can configure your DNS server with one of the three default DNS server IPv6 addresses that are automatically configured on all IPv6 clients.
You can configure clients with the IPv6 address of the DNS server by using the netsh interface ipv6 add dns command at each client computer or in a logon script that is run each time a client logs on to the network.
To configure the DNS server with one of the three IPv6 addresses that are available on IPv6 client computers by default, use the netsh interface ipv6 add address command. The three default DNS server addresses are:
If your DNS server is on a different subnet than your IPv6 clients, configure a static route to the DNS server on any IPv6 router that is available on the DNS server’s subnet.
You can configure the DNS server to listen for DNS name registration and resolution requests over IPv6. When your DNS server is configured to listen on both IPv4 and IPv6:
To configure your DNS server to listen over IPv6, do the following:
For more information, see Install Windows Support Tools
dnscmd /config /EnableIPv6 1
source microsoft
After a recent Windows Update I could no longer access the folders on my Windows XP file server. A window popped up asking for a username and password even though they are both the same on the two computers. The error message each time was “Logon failure: unknown username or bad password.”
I typed in my username and password five times. It reached the point where I thought I had gone crazy and was typing in the wrong one: it kept on coming back to me with the dreaded “Logon failure: unknown username or bad password.”.
I quickly returned to my senses and guessed something was up with the authentication between XP and Windows 7. A few Google searches later I found out that a Local Security Policy needs changing.
It seems that a recent Windows Update has changed that policy’s settings to be undefined, which —from what I can tell— forces NTLMv2 session security always. My XP installation mustn’t have NTLMv2 capability and that is why I kept seeing “Logon failure: unknown username or bad password.” errors.
After changing the local policy I was immediately able to connect to my network shares again.