Windows 2008r2 cluster dns issue

We are running GW 8.0.2 not hot patches. System is running on a windows 2008r2 2 node cluster. When we failover the gwia from node 1 to node 2 we can no longer send email to the internet. We receive just fine, also imap and pop connections are working. We have checked firewall settings and they are the same for both nodes. We get 450 hosts unknown errors for all email going out. We think this is a dns issue, but can't find where the problem may be. We have checked the registry dns nameserver entries on both nodes and they match.
Thanks,
Bill

On the GWIA, is the bind exclusive set on the addressing tab?
The GWIA will send on the primary address of the box unless this box
is checked - but it will listen on all IP addresses (this inbound will
work but recieve will not)
T
On Fri, 01 Apr 2011 12:38:04 GMT, [email protected]: wrote:
>We are running GW 8.0.2 not hot patches. System is running on a windows 2008r2 2 node cluster. When we failover the gwia from node 1 to node 2 we can no longer send email to the internet. We receive just fine, also imap and pop connections are working. We have checked firewall settings and they are the same for both nodes. We get 450 hosts unknown errors for all email going out. We think this is a dns issue, but can't find where the problem may be. We have checked the registry dns nameserver entries on both nodes and they match.
>
>Thanks,
>Bill

Similar Messages

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]

Procedure to remove DHCP service off a Windows 2008R2 Cluster.

I cannot seem to find a procedure to remove DHCP off the Windows 2008 R2 Cluster.
I am not sure which comes first Delete the DHCP cluster service or uninstalling the role.
Thank you.

Hi,
Based on my exprience, it would be better to removal of the DHCP failover relationship firstly. Because if you remove the DHCP server role firstly, then you cannot communicate with the partner server. In addition, deleting a failover relationship that has
DHCP scopes associated with it will remove those scopes from the partner DHCP server, and the scopes will remain on the DHCP server where the failover relationship was deleted. So you can do that on the DHCP server that you want to keep. For detailed
information, please refer to the article below:
https://technet.microsoft.com/en-au/library/dn338986.aspx#delete
Then after you renew leases on the clients and make sure that only one server is responding to DHCP requests. After that, you can uninstall the role.
Best regards,
Susie
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 Subscriber Support, contact [email protected]

Failover Cluster Core Resources question on a Windows 2008R2 three node cluster

We have a three node Windows 2008R2 cluster with SQL Server 2008 R2 as a clustered resource. There are three resource groups in this cluster 1) Available Storage 2) Cluster Group 3) SQL Server. The Available Storage and SQL Server resource groups
reside on one node while the Cluster Group resides on another. The only resources residing in the Cluster Resource Group is the Cluster name and IP. I'd like to failover the Cluster Resource Group to be on the same node as everything else.
I'm not sure what the implications are on doing this. Failing over the Cluster Group shouldn't have any impact on the SQL Server Resource Group correct or would there be an interruption to SQL because of the failover of the Cluster Group. It's
an critical application of which I'm trying to gather some information for a change request and I know I'm going to be asked if this impacts the production database and everybody using it.
Thanks
RG

No, that should not impact anything. The cluster group is completely separate from the SQL group.
. : | : . : | : . tim

SAP GUI Compatibility issue with Windows 2008R2 64 Bit

Hi Gurus
Is anyone experienced connectivity issue with SAP GUI (32bit) on Windows 2008R2 64bit? Except base version of 7.3 every Service Pack failing
to connect, Strange thing was it was working with SP5 in WINDOWS 7 64bit.
Your inputs greatly appreciated.
-giri

Hi Giri
Yes, You can do the normal installation on windows 2008 / 2008 R2 systems. we are using in our environment. is this any error message while installation or SAPGUI execution time?
Refer the SAP Note 66971 - Supported SAP GUI platforms
BR
SS

Setup test envrionment for windows server 2008r2 cluster + oracle failsafe

Hi All,
Would like to set up windows server 2008r2 cluster + oracle failsafe for testing purpose.
Am new to this. I have a windows 7 desktop machine.
Can i acheive it using virtual box or?
Need your advise here.
thanks!

dbaing wrote:
Hi All,
Would like to set up windows server 2008r2 cluster + oracle failsafe for testing purpose.
Am new to this. I have a windows 7 desktop machine.
Can i acheive it using virtual box or?
Need your advise here.
thanks!http://www.oracle-base.com/articles/11g/oracle-db-11gr2-rac-installation-on-oel5-using-virtualbox.php

Windows 2012 RDS on hyperV - DNS issue

Strange issue, whilst fiddeling arround with some certificates on the connection broker and eventualy rolling back the snapshot I was unable to contact my RD session host.
When I try to connect through RD Web Access it gives me an untrusted certificate (which is correct) and after accepting this it seems to hang in a loop, just trying to connect for ever.
Looking at the CB I found some DNS issue;
Event 8014, DNS Client Events
The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings:..... (correct settings)
The reason the system could not register these RRs during the update request was because of a system problem. You can manually retry DNS registration
So I ran a ipconfig /registerdns but that gives me the same error.
I removed the connection broker from the domain and added it again. Upon moving it to a workgroup the entry on the DNS server was removed, when adding it back into the domain it appeared again. So it kind of works.
What I noticed, after removing it from the domain and adding it again, the RDP connection failed to find the server but didnt try to connect indefinatly. Once I ran ipconfig /registerdns I was back to the beginning, just trying to connect and nothing happens.
So it had some sort of effect.
I'm still unable to setup a connection to my session hosts.
Anyone??

Hi ,
Maybe you can get the accurate assistance from RDS forum :
http://social.technet.microsoft.com/Forums/en-US/home?forum=winserverTS&filter=alltypes&sort=lastpostdesc
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DFS - Cannot Create Namespace - RPC Server Is Unavailable windows 2008R2

Hi guys, I am back again with another question
I am trying to create a domain based namespace, enabled Windows 2008 mode and get the following
error...\\Miracle-Adventure.com\dfs. The namespace cannot be queried. The RPC server is unavailable.
I have 3 DC's - 2 Virtual DC (windows 2008R2) / 01 DC on a Physical Box Windows 2008R2. I am trying
to create the DFS Namespace in my Physical Box DC01.
Any Idea?

Hi,
You could update the HOST (A) records on the DNS server for the domain name, pointing to IP Addresses of some or all of the DCs to resolve the issue:
For more detailed information, please refer to the article below:
"The namespace cannot be queried. The RPC server is unavailable." error attempting to create a DFS namespace on Windows Server 2008
http://support.microsoft.com/kb/2021914
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SSRS 2012 SP2 - Windows 2008R2 - Microsoft.ReportingServices.ReportProcessing.RenderingObjectModelException: A generic error occurred in GDI+

Hi,
I have built new SQL 2012 SSRS SP2 with Windows 2008R2 and BAR reports are not showing (just "x" mark in the left corner).
Following is the log file information. I have gone through other forums and all are with windows 8 or windows 2012. Your help is much appreciated.
library!ReportServer_0-15!d7c!08/13/2014-10:52:17:: i INFO: RenderForNewSession('/ProductionReporting/PlantProduction')
reportrendering!ReportServer_0-15!d7c!08/13/2014-10:52:18:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.RenderingObjectModelException: , Microsoft.ReportingServices.ReportProcessing.RenderingObjectModelException: A generic error occurred
in GDI+. ---> System.Runtime.InteropServices.ExternalException: A generic error occurred in GDI+.
   at System.Drawing.Image.Save(Stream stream, ImageCodecInfo encoder, EncoderParameters encoderParams)
   at Microsoft.Reporting.Chart.WebForms.Chart.Save(Stream imageStream, ChartImageFormat format)
   at Microsoft.ReportingServices.OnDemandReportRendering.ChartMapper.GetImage(ImageType imageType)
   --- End of inner exception stack trace ---;
Thanks,
Vel
Vel Thavasi

Hi Vel,
According to the error message, the issue is related to GDI+. Based on my research, it is a known issue that the GDI+ need to be updated on Windows Server 2008 R2. If we want to know what version of GDI+, we can do a file search for Gdiplus.dll.
To fix this issue, please install the hotfix for your Windows Server 2008 R2 from the following kb:
http://support.microsoft.com/kb/2495074
There following thread about the similar issue is for your reference:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/50c071db-b4fc-4a2e-a9f4-e10e833c97d2/report-not-rendering-charts-in-pdf-a-generic-error-occurred-in-gdi?forum=sqlreportingservices
If there are any other questions, please let me know freely.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

ITunes not responding due to DNS issues?

iTunes 11.1.0.126 on Windows 7, never had a problem in the past 5 years... iTunes runs 24/7 on this machine. It has been running for days since my last reboot, maybe a week. I was listening to a podcast, then went into the store to search for an artist, clicked on an album, listened to preview, back button, different album, preview, back button, different album, etc then one time when I clicked the back button iTunes became unresponsive until I had to kill it.
I can no longer open iTunes, it always opens as a transparent window with a border and is immediately "Not responding" in task manager. Same thing happens in safe mode. I tried rebooting too.
Around this time I started noticing other problems with my internet connection. Seems like my provider is having DNS issues because certain websites hosted on the east coast won't load, but west coast websites will (I am on the west coast). I tried loading these websites on my phone through cell data and they worked, so I figured my provider is having problems.
Now I'm wondering if iTunes calls home or tries to make some sort of connection when it loads, regardless of safe mode or not, and this causes the application to hang immediately. Does anyone know anything about this, or how I might be able to get the iTunes application to run again?

Well, it wasn't a DNS issue, it was a routing issue that affected ISP customers in half of the country. https://community.shaw.ca/thread/9284?start=0&tstart=0
I can confirm that iTunes will now open and is functional. It seems that if the application can't access some internet resource immediately when it launches it will immediately lock up and never come back! No offline mode??!?!

Where is Oracle 64 bit 11gR1 11.1.0.7 clusterware on windows 2008r2?

I am confused on something. I am trying to test Oracle 64 bit 11gR1 11.1.0.7 clusterware on windows 2008r2.
I am following Reall application cluster guide for 11g Release 1.
I downloaded Oracle 64bit 11gR1 11.1.0.7.
I couldn't get the window that has options to select
Oracle database 11g
Oracle client
Oracle Clusterware
It seems it only want to install Oracle database server, any clue?
Is it seperated download now?
Regards
Howard
Edited by: user12004308 on 16-Jun-2011 12:08 PM

Hi,
Windows 2008 R2 is not yet certified for running clusterware 11.1.0.7. You would need windows 2008 to be certified
you can get the installer from here
Cheers
FZheng

Windows 2008r2 and 450 Host down

We are running GW 8.0.2 on a Windows 2008r22 cluster. The server sits in the DMZ. A rule here as that no servers in the DMZ are allowed to be part of the main Windows domain of the company. Since clustering requires a domain controller we had to install our GWIA into its own Windows domain. My question is how will the following tid affect the server if we change the primay suffix of this computer as recommended by the tid.
"450 Host Down" errors GWIA on Windows 2008
This document (7005218) is provided subject to the disclaimer at the end of this document.
Environment
Microsoft Windows Server 2008
Novell GroupWise 8
Novell GroupWise 8 Internet Agent
Situation
When sending an outbound email with GWIA running on Windows 2008 Server, GWIA does not resolve DNS correctly and immediately shows a "450 Host Down" error (for the domain name of the recipient) when trying to send the message.
In Diag log mode, GWIA also shows a "No MX records found" error for each outbound message.
Resolution
Right-click My Computer
Go To Properties
Click on Change settings > Change
Go to the More tab then put the email domain name (such as "novell.com") in the "Primary DNS suffix of this computer" box.
Document
Document ID:7005218
Creation Date:01-25-2010
Modified Date:01-25-2011
Novell Product:GroupWise
Disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

[email protected]: wrote:
> My question is how will the following tid affect the server if we change the
> primay suffix of this computer as recommended by the tid.
Other than making it work? It won't have any adverse affect at all - just put
your normal company's internet domain in there.
Danita
Novell Knowledge Partner
Moving GroupWise to Linux?
http://www.caledonia.net/gwmove.html

Binding to Windows 2008r2 domain gives wrong kvno

I'm getting inconsistent results binding a 10.6.6 system to a windows 2008r2 domain with two DCs. The domain join always appears to work, but in some cases I'm not getting a usable /etc/krb5.keytab file. The upshot is that I can't use GSSAPI with ssh to access the mac from other unix systems.
In the failure case, the KVNOs in /etc/rb5.keytab disagree with the values in AD. Using 'klist -k -t' on the mac, I see all the KVNOs are 1, but looking on the windows side with ADSIedit, the msDS-KeyVersionNumber on the computer account is 2.
In the success case, there are duplicate entries for all the keys in the Mac keytab file, one set with KVNO 1 and one set with KVNO 2, windows reports KVNO 2, and everything (ssh) works.
This also affects kerberos console logins with the /etc/authorizations 'builtin:krb5authenticate,privileged' patch (krb5authnoverify works in both cases).
I have inconsistent results with Directory Utility (sometimes I get a working krb5.keytab and sometimes I get the broken one). I haven't seen any rhyme or reason to the behavior. I go away for awhile, and maybe it works when I come back (and maybe not). But never an error; DU always thinks it successfully bound. As an aside, with dsconfigad I always get the broken keytab file.
Any assistance is most appreciated. Thanks!
David Thompson
The University of Wisconsin-Madison
Waisman Brain Imaging Lab

Thanks for your reply!!
Yes! I have done it both ways but still the same thing. Now, something interesting, since I'm in the initial setup of the Domain, I decided to reconfigure it to be mydomain.net, instead of mydomain.local. Now I try to bind and I get an error saying that the DNS name forest is incorrect. However, I cannot change the Directory forest from the default value, which is Automatic. So now, I wonder if its that the domain name needs to be set to my.domain.net rather than mydomain.net. I'm lost here.

Windows Failover Cluster (Errors retrieving file shares)

I'm having an issue with Windows Failover Cluster with a Windows Server 2012 R2 machine. I have two cluster nodes (nodeA and nodeB). My issue is that when nodeA is the owner node, and I open failover cluster manager <clusterName> >>
roles >> <fileserver role> >> shares tab it will hang and say that it is loading, but this will occur infinitely. Although when I go to nodeB (not the owner node) and I go to shares it will show me all of the shares that I have. Next when
I go to <clusterName> >> Nodes >> click on Roles tab the information says "There were errors retrieving file shares."
Now when I switch the nobeB to the owner node, I cannot view the shares on that machine but can now view them on nodeA.
We alse have a test network where I have recreated the machines, environment and the failover cluster to as close as the production network as I can except everything works great in the test network

For anybody searching on this later...
I was getting "There were errors retrieving file shares" no matter which node of my cluster
owned the fileshare service. Turns out my problem was that my servers don't have internet access and I had set a system proxy. The fix described in the link below was to exclude the local domain from the proxy.
http://blogs.technet.com/b/askcore/archive/2012/12/03/cluster-aware-updating-cau-interaction-with-proxy-servers.aspx

IP Resource Errors While Building a Windows Failover Cluster on Azure

I have setup a failover cluster in Microsoft Azure on four VMs. I have two nodes in one subnet/region, one node in another subnet/region and a final node in a third subnet/region. The cluster passed the validation wizard and was successfully built, but the
two nodes in other subnets will not go online, reporting "Failed to bring the resource 'IP Address x.x.x.x' online".
Azure Vnet Setup
Vnet 1 - South Central US - 10.16.16.0/16 - Nodes 1 & 2 - Online
Vnet 2 - West US - 10.116.16.0/16 - Node 3 - Offline
Vnet 3 - East US - 10.216.16.0/16 - Node 4 - Offline
All three IP Address resources are DHCP. I've attempted to make them static but they still failed while coming online. If I click "Information Details" on the error I get:
Error code: 0x80071397
The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource.
It seems to be an issue with the way Azure DHCP works, but I'm stalled. There must be a way to get his working. What am I missing?

Hi Michael Lapidakis,
Starting in Windows Server 2008, a feature called an “OR dependency” was added to Failover Clustering which gave admins the ability to have nodes with a Network Name that
could use one IP Address OR another IP Address .In a multisite cluster, it is expected that 1 IP address is offline as it is an OR relationship.
You can refer the following related article to realize more detail settings of multi-site site cluster IP settings.
IP Resource Errors While Building a Windows Failover Cluster on Azure
https://social.technet.microsoft.com/Forums/en-US/ca2cbf5e-abef-4c23-9cff-7b6ca44acc23/ip-resource-errors-while-building-a-windows-failover-cluster-on-azure?forum=winserverClustering
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows 2008r2 cluster dns issue

Similar Messages

Maybe you are looking for