Cannot connect to Microsoft account remotely via either FTP or VNC

I had a local account on Windows 10 running on my old PC and set it up as an ftp and vnc server. (Sysax Multiserver for ftp and UltraVNC for vnc) That worked fine.

Now I got a new PC running Windows 10, and I let Microsoft talk me into using a Microsoft account.

But those same server applications do NOT seem to work with a Microsoft account. I can't even log in from inside my own LAN. I can think of two reasons for this:

1. They don't accept my user name with a space in the middle. I don't want to give my real name on this forum, but let's say my real name is "John Smith." Then my Microsoft account was named "John Smith" and that's how I log in. But the ftp and vnc clients don't seem to accept a username with a space in the middle like "John Smith." (My old local account name didn't have a space in the middle.)

2. Some kind of security problem. I turned off the firewall completely but I still can't get connected.

Has anybody here tried to set up a Microsoft account as an ftp or vnc server? How did you do it?

I re-edited this post because your suggestion does work--inside my LAN but not outside.

But now I'm still having trouble connecting to the ftp server from outside the LAN.

The only thing I changed from my old PC to my new PC is that I gave my new PC a static IP address inside my LAN, but I forwarded the ports to that new static IP address.

Turning off the firewall didn't fix it.

I still can only connect to VNC from inside my LAN, not outside, and I cannot ftp at all, either inside my LAN or from outside.

This is why I asked if anyone had actually gotten VNC or FTP to work with a Microsoft account. I'm getting error messages in the VNC log that I don't recognize and didn't see with local accounts.

Sat Sep 03 12:12:10 2016
vncmenu.cpp : ############### Usernames change: old="sdlit", new="sdlit"
Sat Sep 03 12:12:15 2016
vncmenu.cpp : ############### Usernames change: old="sdlit", new="sdlit"
--The system cannot find the file specified.
Sat Sep 03 12:12:20 2016
vncmenu.cpp : ############### Usernames change: old="sdlit", new="sdlit"
--The system cannot find the file specified.
Sat Sep 03 12:12:25 2016
vncmenu.cpp : ############### Usernames change: old="sdlit", new="sdlit"
--The system cannot find the file specified.
Sat Sep 03 12:13:03 2016
vncserver.cpp : authhosts set to ""
vncproperties.cpp : ***** DBG - Load User Preferences
vncproperties.cpp : clearing user settings
c:\users\rudi\desktop\ultravnc_1211\winvnc\winvnc\vncpasswd.h : PASSWD : FromClear called
vsocket.cpp : VSocket() m_pDSMPlugin = NULL
vsocket.cpp : VSocket() m_pDSMPlugin = NULL
vncsockconnect.cpp : started socket connection thread
vncproperties.cpp : $$$$$$$$$$ ApplyUserPrefs - Plugin NOT enabled
c:\users\rudi\desktop\ultravnc_1211\winvnc\winvnc\vncpasswd.h : PASSWD : ToText called
vnchttpconnect.cpp : started HTTP server thread
vncmenu.cpp : IsIconSet
Sat Sep 03 12:22:36 2016
vsocket.cpp : VSocket() m_pDSMPlugin = NULL
vncsockconnect.cpp : accepted connection from 198.199.98.246
vncserver.cpp : AddClient() started
vncclient.cpp : vncClient() executing...
vncclient.cpp : TEST 4
vncserver.cpp : AddClient() done
vncclient.cpp : client connected : 198.199.98.246 (1)
vncclient.cpp : DSMPlugin Pointer to socket OK
vncclient.cpp : Repeater connect
vncclient.cpp : Repeater connected, waiting viewer
vsocket.cpp : zero bytes read2
vncclient.cpp : Reconnect to repeater
vncserver.cpp : removing unauthorised client
vncserver.cpp : RemoveClient() done
vncclient.cpp : ~vncClient() executing...
vncclient.cpp : deleting socket
vsocket.cpp : closing socket

If anyone has actually done it successfully, please let me know. Otherwise, I'm giving up.

In my past experience, whenever I've fooled around with a mysterious problem for a day or more, it has usually turned out to be a Windows or Office bug or limitation that I have no control over. I'm suspecting that's the case here. So there's no point in my struggling with it on my own.

I checked the ports with a separate tool. The ports are open, but the server is still not making the connections.

I give up.

Kari,

First of all, let me apologize for having been a little dismissive of your advice. It turned out that you were right--but the applications were wrong.

There seems to be some fundamental incompatibility between Sysax Multiserver and Windows 10 Microsoft accounts. I switched to FileZilla as an FTP server and that worked the first time with your advice on naming. No bugs, no glitches, even with a Microsoft account. So I'm satisfied.

I'm going to mark this thread as solved. From now on, I'll just log in with "PC name\username" whenever just the username doesn't work.

Thanks for your help!