An unknown error occurred while validating the server
One thing to note, if there is any filtering, is that zone transfers (AFXR/IXFR) with windows do NOT use UDP/53. So if your network/VPN admin is saying 'oh yeah, we allow DNS' he may be only allowing port 53. One thing to note, if there is any filtering, is that zone transfers (AFXR/IXFR) with windows do NOT use UDP/53. So if your network/VPN admin is saying 'oh yeah, we allow DNS' he may be only allowing port 53.
PARKSERV side: access-list outside_20_cryptomap extended permit ip 192.168.250.0 255.255.255.0 192.168.251.0 255.255.255.0 [192.168.250.1 /24]BOALSBURG side: access-list outside_20_cryptomap extended permit ip 192.168.251.0 255.255.255.0 object-group DM_INLINE_NETWORK_1[192.168.251.1 /24] object-group network DM_INLINE_NETWORK_1 Didn't see any other parts of the config that would be affecting that traffic but I'm not a networking expert by any stretch - I have more experience than the in-house IT people but I'm not their Cisco guy.
I had to set up an system environmental variable named JAVA_HOME that pointed to the JDK directory.
Even after this change, I still ran into the "An unknown error occured while validating path." Right-click on the Net Beans install software and select "Run as Administrator...".
In the BES Console, you are getting an error similar to the following after logging in: in site #2 'Patches for Windows' HTTP Error 18: An unknown error occurred while transferring data from the server: transfer closed with outstanding read data remaining You then notice that the affected site has the latest version of the site gathered, but has zero content inside.
* This issue may occur on several machines running the BES Console while work for some.
However, when I attempt to create the blackberry.local forward lookup zone on Parkserv I get to the "Master DNS Server" page of the wizard and after I enter the IP address of Boalsburg (192.168.251.1) it fails.Built inbound UDP connection 1637567 for outside:192.168.251.1/59715 (192.168.251.1/59715) to inside: Parkserv/53 (Parkserv/53)Built inbound UDP connection 1637566 for outside:192.168.251.1/59715 (192.168.251.1/59715) to inside: Sharepoint/53 (Sharepoint/53)^High UDP port number originating from source to DNS port (53) destined for the two DCs in the domain. [yeah yeah, Sharepoint as a DC - didn't do it and only two servers on network]So now it's narrowed down to a single DC (PARKSERV).