Windows 7 Pro DNS issue with static IP

0
down vote
favorite
I have been unable to solve a DNS problem I am having as follows:
I have a Windows 7 Professional (64 bit) computer running VirtualBox with a couple of Windows XP guests (not sure if this bit is relevant). After heavy file copying/transfer on both of the Windows XP machines, both the guest machines AND the host loose anything
DNS related, so I cannot call anything by name, but by direct IP works fine. The only resolution is to reboot the (host) machine and it will then work OK for a while until it happens again. The only trigger to make it seem to happen quicker is to re-initiate
the heavy file transfer and this then causes the DNS resolution to stop working again.
The machine has a fixed IP address, so it isn't related to DHCP.
I've tried the machine connected wired and wireless, no difference.
The IP settings are manual and I have tried giving it the DNS settings of the router (normal settings) and I have also tried giving it Google's DNS servers (8.8.8.8 & 8.8.4.4). No difference.
It seems to happen (sooner) during heavy traffic.
Other Windows 7 machines in the network work fine (though they are Home version, not Pro).
ONLY DNS fails, direct IP works OK.
Reboot seems only solution at the moment.
I am now lost as to what to try to resolve this issue, I do not really want to reload Windows 7 as it is a relatively new install... I have read about issues with wired connections on my router (BT Home Hub 2.0) so tried a wireless connection, still the
same.
Here is my ipconfig /all (it shows the BT Home Hub router DNS settings, but it also failed with Google's 8.8.8.8 and 8.8.4.4 entered here and also with the routers 192.168.1.254 (default).
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\G>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : e1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 30-85-A9-AD-07-81
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::59f:484a:827f:42ba%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.87(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 238060969
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
DNS Servers . . . . . . . . . . . : 217.32.171.21
213.120.234.30
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-28-56
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8d2d:7418:381b:8dc0%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 336068647
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{486D4DCC-9CB7-417E-A796-596E0E6B1D54}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{67455999-75A5-436E-9EAC-12B093363132}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\G>
Any ideas where to look, or what other info to provide for any assistance?
Many thanks in advance.

Hi,
This has just happened again, here is the content of the netstat results as requested...
If I kill the VirtualBox virtual machines, it starts working again. It is as if there are no ports left, but I am not occupying that many? Surely Windows 7 can cope with this?
I feel I am missing something important, but cannot put my finger on it...
Further below, I have re-run the netstat command AFTER I have closed the VirtualBox machines and the system works OK.
netstat results DURING ISSUE:
Active Connections
Proto Local Address          Foreign Address        State           PID
TCP    0.0.0.0:21             0.0.0.0:0              LISTENING       1444
[FileZilla Server.exe]
TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       1692
[MESMTPC.EXE]
TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    0.0.0.0:110            0.0.0.0:0              LISTENING       1660
[MEPOPS.EXE]
TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       752
RpcSs
[svchost.exe]
TCP    0.0.0.0:143            0.0.0.0:0              LISTENING       1524
[MEIMAPS.exe]
TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    0.0.0.0:1221           0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:2199           0.0.0.0:0              LISTENING       4820
[VirtualBox.exe]
TCP    0.0.0.0:3306           0.0.0.0:0              LISTENING       1756
[mysqld.exe]
TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       1104
CryptSvc
[svchost.exe]
TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
[WinVNC.exe]
TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
[WinVNC.exe]
TCP    0.0.0.0:8300           0.0.0.0:0              LISTENING       3464
[sc_serv.exe]
TCP    0.0.0.0:8301           0.0.0.0:0              LISTENING       3464
[sc_serv.exe]
TCP    0.0.0.0:8360           0.0.0.0:0              LISTENING       3080
[sc_serv.exe]
TCP    0.0.0.0:8361           0.0.0.0:0              LISTENING       3080
[sc_serv.exe]
TCP    0.0.0.0:9022           0.0.0.0:0              LISTENING       4804
[VirtualBox.exe]
TCP    0.0.0.0:9023           0.0.0.0:0              LISTENING       4804
[VirtualBox.exe]
TCP    0.0.0.0:9080           0.0.0.0:0              LISTENING       4804
[VirtualBox.exe]
TCP    0.0.0.0:10001          0.0.0.0:0              LISTENING       4828
[VirtualBox.exe]
TCP    0.0.0.0:10002          0.0.0.0:0              LISTENING       4828
[VirtualBox.exe]
TCP    0.0.0.0:10003          0.0.0.0:0              LISTENING       4828
[VirtualBox.exe]
TCP    0.0.0.0:10011          0.0.0.0:0              LISTENING       4780
[VirtualBox.exe]
TCP    0.0.0.0:10012          0.0.0.0:0              LISTENING       4780
[VirtualBox.exe]
TCP    0.0.0.0:10013          0.0.0.0:0              LISTENING       4780
[VirtualBox.exe]
TCP    0.0.0.0:25566          0.0.0.0:0              LISTENING       3648
[TerrariaServer.exe]
TCP    0.0.0.0:30001          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30002          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30003          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30004          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30005          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30006          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30007          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30020          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30021          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30039          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30080          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30081          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30082          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30083          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30084          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30085          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30086          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30087          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30088          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30089          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30090          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30091          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30092          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30093          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30094          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30095          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30096          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30097          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30098          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30099          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30101          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30102          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30103          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30104          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30105          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30106          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30107          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30108          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30109          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30110          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30111          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30112          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30113          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30114          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30115          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30116          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30117          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30118          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30119          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30120          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30121          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30139          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30180          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30181          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30182          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30183          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30184          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30185          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30186          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30187          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30188          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30189          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30190          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30191          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30192          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30193          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30194          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30195          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30196          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30197          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30198          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30199          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30201          0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:30239          0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:33306          0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       440
[wininit.exe]
TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       880
eventlog
[svchost.exe]
TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       1000
Schedule
[svchost.exe]
TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       508
[lsass.exe]
TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING       500
[services.exe]
TCP    0.0.0.0:49158          0.0.0.0:0              LISTENING       3048
PolicyAgent
[svchost.exe]
TCP    127.0.0.1:8361         127.0.0.1:49364        ESTABLISHED     3080
[sc_serv.exe]
TCP    127.0.0.1:14147        0.0.0.0:0              LISTENING       1444
[FileZilla Server.exe]
TCP    127.0.0.1:14147        127.0.0.1:49162        ESTABLISHED     1444
[FileZilla Server.exe]
TCP    127.0.0.1:49162        127.0.0.1:14147        ESTABLISHED     3156
[FileZilla Server Interface.exe]
TCP    127.0.0.1:49212        127.0.0.1:49213        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49213        127.0.0.1:49212        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49214        127.0.0.1:49215        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49215        127.0.0.1:49214        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49216        127.0.0.1:49217        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49217        127.0.0.1:49216        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49218        127.0.0.1:49219        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49219        127.0.0.1:49218        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49220        127.0.0.1:49221        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49221        127.0.0.1:49220        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49222        127.0.0.1:49223        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49223        127.0.0.1:49222        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49224        127.0.0.1:49225        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49225        127.0.0.1:49224        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49226        127.0.0.1:49227        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49227        127.0.0.1:49226        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49364        127.0.0.1:8361         ESTABLISHED     3100
[Instore_Radioboss.exe]
TCP    192.168.1.87:139       0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    192.168.1.87:3389      217.156.134.12:22971   ESTABLISHED     1104
CryptSvc
[svchost.exe]
TCP    192.168.1.87:8360      81.148.248.221:1026    ESTABLISHED     3080
[sc_serv.exe]
TCP    192.168.1.87:25565     0.0.0.0:0              LISTENING       4288
[java.exe]
TCP    192.168.1.87:50644     37.139.0.151:8233      ESTABLISHED     4796
[VirtualBox.exe]
TCP    192.168.1.87:51019     81.27.96.46:21         TIME_WAIT       0
TCP    192.168.1.87:53126     192.168.1.86:445       ESTABLISHED     4
Can not obtain ownership information
TCP    192.168.1.87:60462     192.168.1.86:445       CLOSE_WAIT      4
Can not obtain ownership information
TCP    192.168.1.87:65029     37.139.0.151:8231      ESTABLISHED     4796
[VirtualBox.exe]
TCP    192.168.56.1:139       0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    [::]:21                [::]:0                 LISTENING
1444
[FileZilla Server.exe]
TCP    [::]:25                [::]:0                 LISTENING
1692
[MESMTPC.EXE]
TCP    [::]:80                [::]:0                 LISTENING
4
Can not obtain ownership information
TCP    [::]:135               [::]:0                 LISTENING
752
RpcSs
[svchost.exe]
TCP    [::]:445               [::]:0                 LISTENING
4
Can not obtain ownership information
TCP    [::]:3306              [::]:0                 LISTENING
1756
[mysqld.exe]
TCP    [::]:3389              [::]:0                 LISTENING
1104
CryptSvc
[svchost.exe]
TCP    [::]:30239             [::]:0                 LISTENING
4796
[VirtualBox.exe]
TCP    [::]:49152             [::]:0                 LISTENING
440
[wininit.exe]
TCP    [::]:49153             [::]:0                 LISTENING
880
eventlog
[svchost.exe]
TCP    [::]:49154             [::]:0                 LISTENING
1000
Schedule
[svchost.exe]
TCP    [::]:49156             [::]:0                 LISTENING
508
[lsass.exe]
TCP    [::]:49157             [::]:0                 LISTENING
500
[services.exe]
TCP    [::]:49158             [::]:0                 LISTENING
3048
PolicyAgent
[svchost.exe]
TCP    [::1]:14147            [::]:0                 LISTENING       1444
[FileZilla Server.exe]
UDP    0.0.0.0:123            *:*
964
W32Time
[svchost.exe]
UDP    0.0.0.0:500            *:*
1000
IKEEXT
[svchost.exe]
UDP    0.0.0.0:3702           *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:3702           *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:4500           *:*
1000
IKEEXT
[svchost.exe]
UDP    0.0.0.0:5355           *:*
1104
Dnscache
[svchost.exe]
UDP    0.0.0.0:53274          *:*
4780
[VirtualBox.exe]
UDP    0.0.0.0:53727          *:*
4788
[VirtualBox.exe]
UDP    0.0.0.0:54111          *:*
4828
[VirtualBox.exe]
UDP    0.0.0.0:54112          *:*
4828
[VirtualBox.exe]
UDP    0.0.0.0:54113          *:*
4780
[VirtualBox.exe]
UDP    0.0.0.0:55421          *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:58596          *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:59838          *:*
4812
[VirtualBox.exe]
UDP    0.0.0.0:62498          *:*
4796
[VirtualBox.exe]
UDP    127.0.0.1:1900         *:*
4172
SSDPSRV
[svchost.exe]
UDP    127.0.0.1:55045        *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.1.87:137       *:*
4
Can not obtain ownership information
UDP    192.168.1.87:138       *:*
4
Can not obtain ownership information
UDP    192.168.1.87:1900      *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.1.87:55043     *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.56.1:137       *:*
4
Can not obtain ownership information
UDP    192.168.56.1:138       *:*
4
Can not obtain ownership information
UDP    192.168.56.1:1900      *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.56.1:55044     *:*
4172
SSDPSRV
[svchost.exe]
UDP    [::]:123               *:*
964
W32Time
[svchost.exe]
UDP    [::]:500               *:*
1000
IKEEXT
[svchost.exe]
UDP    [::]:3702              *:*
964
EventSystem
[svchost.exe]
UDP    [::]:3702              *:*
964
EventSystem
[svchost.exe]
UDP    [::]:4500              *:*
1000
IKEEXT
[svchost.exe]
UDP    [::]:5355              *:*
1104
Dnscache
[svchost.exe]
UDP    [::]:55422             *:*
964
EventSystem
[svchost.exe]
UDP    [::]:58597             *:*
964
EventSystem
[svchost.exe]
UDP    [::1]:1900             *:*
4172
SSDPSRV
[svchost.exe]
UDP    [::1]:55042            *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::59f:484a:827f:42ba%11]:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::59f:484a:827f:42ba%11]:55040 *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::11a6:2283:bc40:c0cb%16]:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::11a6:2283:bc40:c0cb%16]:55041 *:*
4172
SSDPSRV
[svchost.exe]

Similar Messages

Windows 7 Firewire Issues with CS5 and ADVC-700

I've got a Windows 7, 64 bit system with CS 5. In dubbing out for playback, I route a firewire cable from the PC to an Canopus/Grass Valley ADVC-700. Both units are less than a year old and are having issues with "black outs" during the dub out process. I've read different things about Windows 7 having issues with firewire drivers. After speaking to someone with Adobe, I've changed my firewire driver to Legacy. That hasn't helped.
The ADVC-700 has s-video out running to preview monitor and BNC out/XLR audio running to my playback system for ingest. When the video goes to black (usually for a 1/2 second), the audio drops out with it.
I've reset the settings on the ADVC-700 with no luck.
Any suggestions on a fix or something else to try?

I did test with a JVC GY-HD200U and there weren't any performance issues which led me back to the PC or other on the PC.
The system is running Windows 7, 64 bit with CS5 Production Premium following an upgrade from the CS4 version.
I've got 12 GB of Ram, (2) Intel Xeon Quad Core E5560 -2.8 GHZ processoCrs.
(1) 500GB SATA2 hard drive, 7200 RPM, 32 MC (System Drive)
(3) 1 TB SATA2 Hard drives, 7200 RPM, 32 MC (3 TB, RAID0 Storage Drive)
Nvidia GeForce 9800GT graphics Card
Supermicro X8DAi motherboard, Intel 5520 Chipset, 2-PCIe X16, 1 PCIe x4, 3-PCI, 10-USB2 ports, 2-pro/1000 NIC, 8-channel HD audio, 6 SATA ports, RAID 0/1/5/10
I've got the legacy drivers for the firewire card. I've checked to make sure all of the power save options are off along with all screen saver options. I've cleaned my Adobe Cache out, deleted my Adobe Preferences, went from the 4pin/6pin cable to a 6pin/6pin cable to feed the ADVC-700 from the PC, reset the ADVC 700 back to factory specs...all of this with no luck.
The problem seems to be worse since the move from CS4 to CS5 but it's hard to tell.
I've also hooked up an older ADVC-500 unit with the same output results.
I think I noted in the first post that this is happening on two indentical systems with the same cabling and programs and the same ADVC-700 boxes.
I've been told by Adobe to clean my C; drive and reload the OS and Adobe CS5 as I should have done that when I upgraded instead of just upgrading the system from CS4 to CS5 using the discs. I haven't done this yet as I have to budget time/workflow to accomodate.

Dns issues with one domain (Resolved)

i'm currently having dns issues with one domain, in that it won't resolve when I use bt's dns servers.
The domain is owned by a friend in the US who runs his own server for irc, web, and I also have a server that is on his connection, and resolves fine from other machines on different networks, and also resolves fine when I set windows to use the opendns servers, but when it's set to either my routers ip (using bt's dns), or set to automatic (using bt's dns via the homehub), this one domain will not resolve.
I'm pretty certain it's not a windows issue, as it's a clean install of windows 7 that I did yesterday. I've tried rebooting the homehub, and also flushing my dns on windows, but this has not solved the issue.
As I say, it resolves fine on other networks, and also when I use the opendns servers, so I know it's definately a dns issue.
Using bt's dns servers:
C:\Users\admin>ping chatnsn.com
Ping request could not find host chatnsn.com. Please check the name and try agai
n.
Using opendns:
C:\Users\admin>ping chatnsn.com
Pinging chatnsn.com [68.51.24.74] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 68.51.24.74:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
(The timeouts are normal...he has his router set to not respond to ping requests).
Has anyone got any ideas on how to sort this out? Preferably without having to phone the helpdesk...lets just say i've done it in the past, and according to the poeple I spoke to in india, I knew nothing about my own systems, and it was a problem at my end...which was not the case, and I proved this several times.
Edit: This issue appears to have resolved itself, and the domain is now resolving again using the homehub for dns resolution.

Hi,
When NSLOOKUP starts, before anything else, it checks the computer's network configuration to determine the IP address of the DNS server that the computer uses.
Then it does a reverse DNS lookup on that IP address to determine the name of the DNS server.
If reverse DNS for that IP address is not setup correctly, then NSLOOKUP cannot determine the name associated with the IP address.
http://support.simpledns.com/kb/a90/nslookup-cant-find-server-name___-default-server-unknown.aspx
Also refer to:
How to fix NSLOOKUP Default Server: UnKnown?
http://www.randika.info/2013/01/how-to-fix-nslookup-default-server.html
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

DNS Issues with Hyper-V 2012 R2 VDI Pooled Desktop Deployment

Good afternoon all!
We are running a POC VDI deployment on a Nutanix system, and I am having a DNS issue. I would appreciate some help trying to figure this out. Two situations that are causing issues that I can see:
1. VMs go into a saved state if not being used: This in itself is not an issue, and I see it as a way to save resources not being used; however, if a VM is saved for a few days, the DHCP address often gets reassigned. Now if users are connecting, and that
saved VM with the stale address is called to wake up, the VM is not found.
2. Recreating the pool after updating the golden image: This is the bigger issue. After a couple days of running smoothly, I was asked by my pilot users to add Firefox. I installed it and recreated all the VMs in the pool. When this happened, they all got
new IPs, but the old DNS records were not updated. This made the broker unable to find a single VM in the pool. I could not ping a single one.
Has anybody else run into these DNS issues with a VDI deployment? If so, what did you do to resolve it? If not, have any ideas on what is going on here?
Thank you in advance!
Eric

Hi Eric,
As per my research, I can say that the default behavior. When we will recreate the VM it will change the IP address dynamically. But from your description it seems the DNS record is not getting update and due to that you can’t find your VM with hostname or
IP. But for this you can set one option under DNS server with which DNS record can update the new IP address. The option you need to set is “Dynamic updates>Nonsecure and Secure” under general properties in sites. You can check below snap.
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Bootcamp windows 8.0 pro installation issue with early 2015 Macbook Pro

I am having this issue with installing Windows 8.0 pro (and 8.1 pro) on my early 2015 MacBook pro vs. Bootcamp. I have tried different method for multiple times and all failed. Any help is appreciated.
Hardware: (1) early 2015 MacBook Pro with 128GB (13 inches) , (2) Sony USB DVD burner. (3) Two 16 gb flash drive 2.0 version from two different manufactures
Software: (1) 8.0 Pro ISO on flash drive from Microsoft (I have two copies) (2) 8.1 Pro downloaded from Microsoft website.
Note - I was able to download the bootcamp supporting files successfully and copy to a USB flash drive.
Method 1 - Create the installation disk from ISO on flash drive and also tried copying ISO on hard drive (desktop)- failed.
I have a 16 GB flash drive (2.0V) connected
ISO is a valid 8.0 pro copy from Microsoft came on a flash drive.
I have the windows 8.0 pro ISO on a flash drive and plugged in.
Issue - It gets to around 50% of "Copying Windows files..." and then doesn't go any further. 8 hours later, still stuck at around 50%. I also tried to do the copy ISO from desktop. failed as well.
Method 2 - I repeat the above steps with Windows 8.1 ISO downloaded Microsoft website - failed. Stuck at 50% copying windows file for 9 hours.
Method 3 - I burned the Windows 8.0 pro ISO to a DVD and try to do the installation through a DVD instead. DVD was successfully created.
I was able to perform the partition. When the computer reboots, it starts the window installation. However, it got stuck at 7% forever. I tried this multiple times and failed.
Method 4 - I download a 8.1 Pro ISO from Microsoft website, I burned it to a DVD. Repeat method 3, Again, windows installation stuck at 7%.
Method 5 - I called Apple. - What they told me is pretty much repeat the above steps. Still failed.

The ISO file(s) being downloaded seem to be corrupted. Can you use Microsoft FCIV tool - https://support.microsoft.com/en-us/kb/841290?wa=wsignin1.0 ?
The DVDs should be burnt at the recommended rate for the physical media. DU should be used for burning the DVDs.
Reference Disk Utility 12.x: Burn a disk image to a CD or DVD and Boot Camp: Creating an ISO image from a Windows installation DVD - Apple Support.

Windows 7 Install Issues with Mac Pro

I have Mac Pro with Windows XP SP3 installed with Boot Camp on a separate, dedicated 250GB HD.
I purchased an upgrade version of Windows 7 Home Premium. I hoped to install the 64-bit version. I upgraded, per Boot Camp I&S Guide, Boot Camp to version 3.1. After Boot Camp upgrade, I mounted the Windows 7 64-bit installation disk. Since the Windows disk did not open automatically, I then attempted to open the Setup.exe file but got the following error message –
“D:/setup.exe is not a valid Win 32 application.”
I suspect the Boot Camp 3.1 upgrade was for the 32-bit Windows XP system currently installed and this caused Windows 7 (64-bit) not to open.
If my suspicion is correct, would upgrading to Boot Camp 3.1 (64-bit) cause problems with the currently installed Windows XP? Any advice would be appreciated.

I have since attempted to boot from the Windows 7 install disk by using both the OS 10.6.3 System Preferences/Startup Disk and from within Windows XP using the Boot Camp Control Panel. In both cases, all I saw was a black screen with a “Select CD-ROM Boot Type” and flashing cursor. No keyboard input was possible.
If anyone encounters this problem, go to the Boot Camp/Installation and Storage discussion and search for “Select CD-ROM Boot Type”. Hal Jay Greene has an excellent article here titled “Select CD-ROM Boot Type Error installing Windows 7 in Boot Camp walkthrough” dated Mar 20, 2010 that walks one through the process of creating a boot disk for installing Windows 7 x64. Two minor comments on his discussion. John Anderson’s blog is at www.AndersonsHatch.com (note extra s) and Imgburn can be downloaded free from www.imgburn.com.
I used Mr. Greene’s procedure and the resultant boot disk loaded Windows 7 correctly.
Unfortunately, a new issue arose. Installing Windows 7 over Windows XP requires a clean install that eliminates all Boot Camp installations. After installing Windows 7, I attempted to load Boot Camp by inserting the Mac SL installation disk and clicking on Setup in the Boot Camp folder. The result was this error message: “Boot Camp x64 is unsupported on this computer model”. Fortunately, there is a procedure that worked for me, and my MacPro, to bypass this error message. It can be found near the bottom of this article http://blog.andersonshatch.com/2009/01/11/windows-7-x64-on-a-macbook-pro-guide/ on John Anderson’s blog.
Message was edited by: johnshap

Internet DHCP/DNS issues with WRT1900ac

I've had a WRT1900ac now for about 2 weeks and the problems seem to be escalating. Need help. And yes, I've already read dozens of threads about these issues and nothing seems to be working.
Most of the problems seem to be centered around this DHCP/DNS issue that so many have been reporting.
First, the symptoms:
Galaxy S4 phones when connected via wifi have some apps that don't update (facebook and google play)
Some computers (both Win 7) will connect to the network just fine, both wired and wireless - but won't be able to get to the internet
I've spent the last 2-3 days of my life reading forums and trying all sorts of things to get this to work properly (like my old router) and I'm still stuck. Some things I've tried:
Firmware is up-to-date (latest version: 1.1.8.164461)
Manually assigned static DNS in router config settings (connectivity -> local network) to various combinations including the router address, 8.8.8.8, 8.8.4.4, 75.75.75.75, 75.75.76.76 (I have comcast), OpenDNS addresses, etc. I read that the router address is not needed, so I stopped including it.
I manually assigned IPs and DNS on the Galaxy S4 phones and that seemed to work... but also seems unnecessary.
I've reserved DHCP addresses on the computers in question, that didn't seem to work, I also manually set DNS on one of the comupters (can't on the other... long story/not my computer) and that worked for a while and then stopped working.
The only way to get one of the computers on the internet now is to turn on the guest network (even though the computer is hard wired to the router), connect, and then the wired network works. No clue why this is, but my guess is that it needs the guest network for DNS, then it fails back over to the wired network. Once that happens, I can actually turn off the wifi on the computer and everything works great... until I reboot. Key point: I can't change any settings on that box other than entering in SSID/passphrase info for the wireless connection. I can connect to the regular (non-Guest) wifi just fine - I just can't ever get to the internet.
I've tried massaging DHCP settings on the router until I'm blue in the face - Static DNS, reserving DHCP addresses, hell I even put one of the computers in the DMZ to see if that would work and it still can't connect to the internet (it's worth noting that with my old router, Linksys WRT310N, the setup was literally plug-and-play - no hassle with any of this).
I've tried countless router reboots, factory resets, turning off my modem and router for 2+ minutes, and nothing is working.
I even read somewhere that if you modify your DHCP settings at all that the WRT1900ac stops doing DNS properly and breaks, so I even tried several "hard" factory resets and used all the default DHCP/DNS settings. And it worked... for a few hours.
Seriously, I'm at my wit's end. I'm out a lot of money on this thing and it's been one headache after another. Please help.

I think for most people its a bad idea to hold out that hope, lol. It seems like a great piece of hardware but if you really need a router and don't want to have to 'play' with it, its probably not a good choice. I have an EA6900 that I am very happy with but it has the same restrictions as far as DNS and I really hate the idea that I am forced to use the smartwifi portal. I would really like for them to give me a choice of the old gui or the new one and let ME decide. Lots of routers to choose from out there now and new ones seem to be coming out all the time so do some reading and see if something suits you better. Good luck!

Thanks to Mandeep5062 Acrobat Pro download issue with Safari

Before your response arrived I shut down Safari, loaded Firefox, went directly to the Adobe download page and attempted a download. The download started correctly and then switched over to the Creative Cloud downloader and I thought, "Here we go again". However, the process completed and installed the Acrobat Pro software as advertised. This might be a work around others can use that are having issues with Safari.

Win 7 either comes with a virtural XP machine installed, or it's freelly availible. I forget which, but this may be a simple solution to your issue.
Here's a link that might help:
http://www.microsoft.com/windows/virtual-pc/
Thom Parker
The source for PDF Scripting Info
pdfscripting.com
The Acrobat JavaScript Reference, Use it Early and Often
http://www.adobe.com/devnet/acrobat/javascript.html
Then most important JavaScript Development tool in Acrobat
The Console Window (Video tutorial)
The Console Window(article)

Vista 64, Latest Driver & X-Fi Elite Pro: Audio issue with Pro Evolution Soccer 2008 (Pes 20

Hi,i have formatted XP S.P.2 and now i'm using Vista Ultimate 64.I have got an X-Fi Elite Pro and i have installed all the applications using the CD-Rom.I updated the driver, Alchemy and Mediasource to the latest version.The system is totally clean and updated (I used Windows Update when i finished to install Vista and nothing was installed). I would like to know why i cannot play Pro Evolution Soccer 2008 like in XP: when i enter in the game i have a noise (looks like the noise of the needle in old gramophones...) and i cannot use the speakers (Creative ProGamer G500).If i turn the volume to 0 i can hear it too... i have to switch off the speakers or exit the game to delete it.Is it another bug I tried to uninstall and doing a new installation of the game but... no way men... Thanks p.s.After year and 4 months (release date of Vista) is it possible to have a decent driver... The Audio Quality in Vista Ultimate 64 bit is lower than in XP and the same wave files have distortion with the low and middle-high volume (60-70).
Problems that i have never had in XP... i cannot reinstall XP another time. I bought Vista in 2006 and i cannot use it till you'll release a good sw.
Have we to wait till 200 for a fuc.ing working driver
My Hw.: Intel Core 2 Quad 6600, DFI Lanparty DK, 2GB DDR800 Team Group, X800XT 52MB, Enermax Noisetaker 600W, Creative X-Fi Elite Pro, Creative ProGamer G500, Plextor PX76SA, Logitech G5 and G5.

The problem is now official: other customers have problems with some games (Pes 2008 and Crysis in particular). I'll show u the main italian hw. forum. There is a thread of more than 500 pages just about Creative X-Fi: http://www.hwupgrade.it/forum/showth...42043&page=550 I would like to know if u test drivers before sharing... because i don't know what you did in more than year.You should meditate, people... I paid more than 400 $ for an Elite Pro and after year and 4 month i cannot install Vista 64 too for audio issues with mp3-wave files and Pes 2008 or Vista 32 bit for problems with Pes 2008. This is my latest Creative product, you can trust.

DNS Issues with Time Capsule - DNS Proxy periodically dies

hi all .... looking for some suggestions
I have a time capsule 1TB, connected to a linksys adsl modem in bridge mode, with the TC acting as DHCP server for my local clients. In the PPPoE settings I also enter the primary and secondary addresses for DNS that my ISP supplied.
I am able to successfully connect to the internet, and all clients successfully pick up an IP address, and each client picks up the TC as the DNS proxy. Everything works perfectly as it should.
Usually once per day, there seems to be a slight hickup with the internet connection (hard to tell whether I am losing the PPPoE or some other issue). When this happens, the PPPoE connection remains active, as I am able to access anything on the internet from an IP level. However, the DNS proxy service on the TC seems to die and as a result, all internet browsing fails. If I reboot the TC, everything comes back to normal. If I dont reboot, the only way to get browsing working is to manually enter the DNS IP address from ISP into the client PCs. However, this is a manual fix that I should not have to perform.
Looking for advice and guidance. Seems like a bug but I cant tell. If I was able to set the DHCP server to pass out the ISP supplied addresses that would also work, but I cant.

Just got off the phone with support for this very same problem. DNS Proxy is definitely dying in the TC, looks like a firmware issue to me.
This is the 3rd TC I'm on. First was a 500GB, had this problem, replaced it under warranty at Apple's direction, replacement did the same, just upgraded this weekend to 1GB, and same issue still. All on 7.3.2 firmware.
TC 1TB, PPPoE to my ISP, ISP's DNS Servers listed in the PPPoE config in the TC.
When a host gets DHCP from the TC the only DNS returned is the TC itself, since it proxies the ISP DNS servers.
Once every day or two, the DNS proxy dies. local network works, and I can add my ISP's DNS addresses in my host config and I have DNS again, but this is definitely something dying in the DNS proxy in the TC.
Just for kicks trying to switch from my ISP's DNS servers to OpenDNS now since someone said that worked for them, but I am not hopeful... I don't see this as a host DNS issues at all.
The dead proxy is very clear:
$ nslookup apple.com. 192.168.1.1 # that's the TC
Server: 192.168.1.1
Address: 192.168.1.1#53
** server can't find apple.com: SERVFAIL
$ nslookup apple.com. 208.67.222.222 # that's OpenDNS
Server: 208.67.222.222
Address: 208.67.222.222#53
Non-authoritative answer:
Name: apple.com
Address: 17.149.160.49
I replaced a linksys router with the TC and am kind of unhappy that a $500 router dies every couple of days. My cheapo Linksys router never needed to be restarted, it only ever got rebooted once every year or so when the house lost power long enough for the UPS to run out of battery.
Help us out here Apple, I replaced a $50 router with a $500 because I like the flavor of your kool aid, and this thing dies every day or two. Even if you can't fix why the proxy is dying every couple of days, can you please at least update the firmware to maybe restart the proxy if it quits working?

HP LaserJet Pro M401n issue with 10.10.2

LaserJet Pro 400 M401n, purchased 10/23/14 and has worked with 10.10.x, connected by USB to MBP (currently with 10.10.2).
LJ M401n has worked with 10.10.x until 3/26/15, when after completing a print job and immediately attempting another print job, I began seeing an error message “79 Service Error Turn Off Turn On” in the printer display.
When again attempting a print job from my MBP, I see the print job being sent to the printer (blinking green light on the printer) and then after a few seconds, the red error light (on the printer) comes on (displaying the error message) and the printer goes into an auto restart (causing the print job to pause). Once the printer restart completes, the print job remains paused; when resumed, the print job does not complete as another “79 Service Error” message occurs.
The LJ M401n remains correctly shown as my Default Printer in Yosemite Sys Pref Printers & Scanners.
From the HP Utility, I can successfully print a Test page as well as a Configuration Report. (Since I can print these test pages, I believe the USB cable, connecting the printer to my MBP, is Ok.)
Looking at other Settings within the HP Utility, everything looks normal. I’ve even compared a newly printed, Configuration Report to one I printed the day I purchased the printer, and all the details are the same, except the Total Impressions (which appears to be correctly keeping count).
I’ve attempted re-installing the HP Drivers 3.0 (from Apple’s web site), which did not achieve any change from what I’ve described above.
Any ideas as to what’s causing the “79 Service Error Turn Off Turn On” error?
(I've posted this same inquiry at HP's Support Forum; so if I get a resolution reply over there, I'll post here to help others.)

** Kappy, I understand I'm posting about an HP Printer, but this Apple Discussions' section is about OS X Yosemite and printers; and as others may have experienced the same issue, I thought it reasonable to post here seeking a resolution. (Please note I did previously mention I'd also posted at HP's Forum.) ...The printer was purchased at Staples; so, I don't expect much help from them. I think posting in this forum, as well as HP's, might achieve quicker results which others might also benefit.
** pmiles, I have done a "Reset the printing system," but issue subsequently remains. I've even deleted the printer from Printers (before reinstalling the HP Drivers 3.0), and added the LJ M401n back afterwards; no success. Each subsequent time I've gotten the 79 Service Error, I deleted the prior print job before initiating a new one. When the printer goes into the 79 Service Error, the printer does an automatic shutdown and restart. After the printer completes the auto-restart, it again shows in my Printers, but just needs to be Resumed.
However, I can provide more details that could provide further insight about this 79 Service Error issue:
I’ve now found that various, doc types (Text rtf, Pages doc, PNG & JPEG pictures) can be printed. PDFs, via Preview, can also be printed as long as the PDF is not generated from a Safari web page. PDFs saved from Safari (regardless of resulting PDF not being a large file - less than 2MB - and even though the LJ M401n has 128MB of memory) are causing the printer to result in the 79 Service Error. As of this writing, I’ve not tested more than a handful of doc types; but, it appears the printer (or possibly, the HP’s printer drivers) is having issue with Safari’s PDF formatting. (I've posted these additional details at HP Forum.)

DNS issues with replaced domain controllers

I have slight issue I hope some one can help with.
We recently replaced some domain controllers in our 2 core sites the process we followed is as below:-
moved FSMO roles to different already working servers
demoted the old domain controllers and decommissioned.
built virtual machine replacements with the same names.
depromo'd the servers
ran all the tests and it reported everything was fine.
moved the fsmo roles to the new servers.
repeated this for the remaining servers.
this was our 2003 domain to free up physical space but our new 2013 domain what will exist separately until all our applications our tested.
however the problem we now have is that non domain controllers have issues registering against the new servers despite being able to do look-ups against them all (replication testing looks fine). one of our regional DC's seems to have taken over as the primary
replica. as changes made else where disappeared but changes made there got replicated out perfectly.
I have managed to resolve this particular issue by added the domain controllers back into several locations in DNS manually (maining forward lookup zones>my domain>_tcp )but we still experience the odd issue with servers not registering in DNS properly
(although it's a lot better since the I did the above)
so basically does any one have a idea on what could have caused this issue and how I can resolve?

should the demotion not automatically remove it from sites and services automatically (it could well be this if not) the question then becomes how do we resolve the issues we have now.
Hello,
NO, as you can demote a DC and it still may run site-aware services like DFS and for this reason a DC is NOT automatically removed from AD sites and services during demotionprocess.
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://blogs.msmvps.com/MWeber
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Twitter:

Premiere Pro CS6 Issues with AJA and Black Magic

Has anyone had any issues outputting via AJA and Black Magic cards?
I have 3 Macs using Black Magic Intesnsity Pro HDMI cards and 1 Mac using an AJA IO Express. On all the machines, i get weird audio issues intermitantly. I press play, no audio comes out. I stop, press play again, no audio comes out but the PP VU meter is registering. I stop, and press play again, and i hear distortion coming from my speakers, i stop and play again, and everything is fine. These issues are consitantly happening, but not necisarily in that order. I also get out of sync audio, then stop and press play again, and its all good.
I fell as though i have narrowed it down to being between PP and the IO cards, because if i turn the cards off in PP, my audio is fine everytime.
I have the propper Premiere Pro drivers (for AJA) and all the latest firmware and drivers for black magic. I am playing Quicktime media, usually Apple Pro Res hq or 444. IO and data rate with same codecs works perfectly in FCP. I have also tried using media that is local as opposed to on our server.
Has anyone had issues with this? Is this a known bug with in PP? Will it ever get fixed???
Thanks.

I have expereinced this issue on my Mac Pro right before I switched to a PC.
Call AJA Support. They are there to help you!

Macbook Pro Retina issues with Wifi Speeds

I have one of the new Macbook Pro 15" Retina models and have been having issues with Wifi Speeds. Apple has replaced the computer but have the same issue with the new one. When doing a side-by-side comparison with older Macbook Pros and PC's I'm seeing around a 10 megabytes per second difference. Is anyone else experiencing the same issue?

So an update on what I've found. After testing two different MBP Retna's basically hourly for 4 weeks I found a few interesting things, but ultimately resolved my issue. The first thing I found consistently between both MBP Retina's both on my network and in the Apple store on their network was the first thunderbolt port closes to the screen is slower than if you try to use the LAN cable adapter on the second port. I saw about 10 GBps between the two ports. The second thing i found was these new MBP Retina's aren't really compatible with older Apple networking technology. I have a single band Airport Express and a single band Time Capsule. Using either router they only worked on the 2.4 5Ghz setting and even with that the speeds constantly fluxuated. Most times I got between 2 - 10 GBps. After hours of troubleshooting it was recommended to update either my Time Capsule or Airport Express to one of the newer dual bands, which I did. After purchasing and setting up a new dual band Airport Express and spliting the networks to have one band constantly on the 2.4 5Ghz setting and the other set to automatic both with differing network id's this solved my problem. I now consistently see download speeds of around 35GBps and upload around 6GBps. So connecting the dots and drawing logical conclusion, these new MBP Retinas are really only compatible with newer dual band Time Capsules or Airports. Even though my single band was also set to 2.4 5Ghz, the same as the dedicated network used now on my dual band Airport Express, this MBP Retina had issues maintaining WiFi speeds.

Windows 7 compatibility issues with Studio 8

Hi guys,
Sorry if this question has been asked before.
I can't afford to upgrade my Studio 8, and I would ideally like to install it clean on my Windows 7 rig which is working fine.
I understand that there is an issue with Flash and Windows 7, and I would like to know what it is (and how serious), and also whether there are any other compatibility issues that would make problems for myself.
Any advice gratefully received.

If compatibility is important to you, your best best is to run a virtual machine in your Windows 7 64-bit installation. You can do this using Virtual PC as part of Windows 7 Professional or Ultimate, or via VMWare's Player software ( http://www.vmware.com/products/player/ ).
Also just a reminder that CS5 betas are planned for later this year and Adobe typically only allows you to upgrade from the previous 3 versions (Studio 8 = CS2, CS5 will be the last version) and some of the Creative Suite applications are going to be 64-bit only(a couple products have updated FAQs stating this fact).

Windows 7 Pro DNS issue with static IP

Similar Messages

Maybe you are looking for