On 2015-04-24, Grant Edwards <grant.b.edwa...@gmail.com> wrote:

> [11:10:38:431] [18829:18830] [ERROR][com.freerdp.core.nego] - Protocol 
> Security Negotiation Failure
> [11:10:38:431] [18829:18830] [ERROR][com.freerdp.core] - 
> freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x2000C]
> [11:10:38:431] [18829:18830] [ERROR][com.freerdp.core.connection] - Error: 
> protocol security negotiation or connection failure
> [11:10:38:432] [18829:18830] [ERROR][com.freerdp.client.x11] - Authentication 
> only, exit status 1

[...]

> However, the power was out the day before yesterday and all the
> servers got power cycled.

Sorry, it looks like it was a network routing problem.

Apparently, my Linux machine came up before the Windows DHCP server
did, and one of my network interfaces failed to come up.  [Why the
dhcp client didn't retry in the background until it worked is the next
question.]

For some reason, with that interface down I could still ping the
servers (apparently via a router/firewall somehow). But, remote
desktop connections via that route weren't allowed.

Or something like that.

After restarting the network interface that was down, everything's
back...

-- 
Grant Edwards               grant.b.edwards        Yow! All of life is a blur
                                  at               of Republicans and meat!
                              gmail.com            


------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Reply via email to