Troubleshooting Server unable to look up internal FDQN "result too large", unable to RDP to server, but can browse and read eventlogs

 nslookup internaldomain.local

 Troubleshooting Server unable to look up internal FDQN "result too large", unable to RDP to server, but can browse and read eventlogs

Quick answer: port exhaustion, kb out there to fix this stuff.

nslookup

 internalserver.internaldomain.local can't find internaldomain.local: unspecified error

1. clear dns servers

2. added dns servers in Core Data centre

3. tried different dns servers in nslookup

3a. tried local dns server

4. modified host file with internal.local to server

fail

Check firewall (disable)

netsh advfirewall set allprofiles state off

result:

ok

Check Group Policy

Gpupdate /force

result:

Updating Policy...User Policy update has completed successfully.Computer policy could not be updated successfully. The following errors were encountered:The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).

To diagnose the failure, review the event log or run GPRESULT /H GPReport.html from the command line to access information about Group Policy results.

check time

w32tm /query /peers

more nslookup

set debug

internaldomain.local

result

-------------

truncated answer

connect failed: result too large

-------------

check server's services

net stop dnscache

net start dnscache

net stop workstation

net start netlogon

Check Ports!

netstat -a -n

problem located - port exhaustion !!! 10000's of time_wait

----Hotfix Time---- (with bonus hotfix)

Windows6.1-KB2553549-v3-x64

Windows6.1-KB2264080-x64

there is a better rollup available(windows6.1-kb2775511-x64) but my server is not SP1. 

enjoy.

Stuck at "Please wait for the Group Policy client..." on Windows 2008 R2

My fellow workmate and myself were working on a two servers that were recently handed over to us.

These servers had multiple nics. Did the usual checked and also change the network provider order to have the "production" network first, because this it the way I roll.

We both joined the servers to the domain, rebooted and everything was fine, could logon etc.
my workmates server was  Stuck at "Please wait for the Group Policy client..."

So did the usual ; trying to view remote event logs, force a remote shutdown (which didn't work).
Decided that it was the fact that the bind order was stopping the logon from working
(Tried remote netsh, that didnt work remotely for some reason, most likely me)

Solutions to fix the problem to allow logon:
Add the blue cable
Add network cable to all NICs on the box (I dont have physical access to the box)
this should give IP address to all NICs


Disable NICs in BIOS
If you in the BIOS disable network card this might also be a option

Remote Connection and Disable the NIC(S) via netsh

1. download psexec from microsoft
2. connect to remote server psexec \\<servername> cmd.exe
3. perform a netsh interface ip show config or ipconfig /all
4. review the network setup, write down the names of the unused NICs or NICS with 169.254 addresses
5. go and disable the nics for example netsh interface set interface "Local Area Connection 3" DISABLED

make sure you don't disable the NIC you are working off! (of course)

Solution to fix the issue:
 change the network provider order to have the "production" network first,

Cleaning up old Windows Drive

Gettings trusted installer errors when trying to delete C:\windows folder
sooo

first tried rename to windows.old incase it a protected folder  - fail
then..
takeown.exe /F D:\windows.old /R /A
icacls "D:\windows.old" /RESET /T /Q /C
rd "D:\Windows.old" /Q /S
or
for /f %i in ('dir /ad /b') do rd %i /s /q

stop that pesky Startup Repair

bcdedit /set {default} bootstatuspolicy ignoreallfailures

Windows 7 64bit Network Freezing

So, had a issue where my laptop which is running windows 7 64bit and the network was freezing copying large files.

On the laptop

• ipv4/ipv6
• virutalbox
• citrix access gateway plugin

The symptoms were large copies were freezing with 0kb/s

removed virutalbox and able to copy files again.

If i get time to investigate then look into if issue between CAG plugin and Virutalbox.

Update:

so the problem came back for some reason, also seems my virtualbox didn't uninstall correctly.

1. only did part..

http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/very-slow-200kbsec-file-copy-between-win7-machines/b8736b1b-0a91-4567-ba33-215084ffc906

a. Running as Administrator in Command Prompt, type: "netsh int tcp set heuristics disabled"

b. Next, follow the instructions that Amrita wrote above.

                  First enter: "netsh int tcp set global autotuninglevel=disabled" and reboot.

2. mucked around with the settings in intel network card properties (latest driver)