I had no luck with any of out administrations wmf services.
I suppose you mean WMS. So far, I've had good luck with WMS (see below).
About WFS: I had no luck with the link you provided. Trying it with QGIS reports that Q does not support the WFS version for that server. Strange...
Anyway, that got me curious, so I used Google to try to find WFS servers I could use for testing. Here is what I found:
1. It is surprisingly difficult to find a functioning WFS server, even if you avoid US government servers that might be off due to the current partial shutdown.
2. It's routine for a WFS server to be misconfigured.
3. It's routine for WFS servers to be unthinkably slow.
A good example of 2 and 3 above is:
That is a WFS server run by the Massachusetts government which returns a huge number of "features" that are available. But the server is so incredibly slow it takes a while for those to appear. If you ask for one of them, even a very small one like the airports, consisting of a total of 42 points, it takes what seems to be almost five minutes for the server to provide the data.
At the same time, various layers within what is advertised to be a public server are forbidden to the public. Looking at the log, we see things like...
2019-01-11 09:44:31 Web request: (root)::[MassGIS]::[massgis:GISDATA.WETLANDSDEP_ARC] (DescribeFeatureType) (0.304 sec, 1.3 KB)
2019-01-11 09:44:32 Web request: (root)::[MassGIS]::[massgis:MASSNET.WEYMOUTH_FIBER_ARC] (DescribeFeatureType) (0.286 sec, 1.3 KB)
2019-01-11 09:44:32 *** (root)::[MassGIS]::[massgis:MASSNET.WEYMOUTH_FIBER_ARC] (DescribeFeatureType) The remote server returned an error: (403) Forbidden.
2019-01-11 09:44:32 Web request: (root)::[MassGIS]::[massgis:MORIS.DPA_WEYMOUTH_FORE_RIVER_ARC] (DescribeFeatureType) (0.315 sec, 1018 B)
2019-01-11 09:44:32 Web request: (root)::[MassGIS]::[massgis:WhitmanEnvironsL3TaxParAssess] (DescribeFeatureType) (0.310 sec, 5.7 KB)
The bottom line is that working with such servers can be frustrating because they may be misconfigured, or because when the server takes minutes to respond to even a tiny request it can appear that Manifold has hung, when it is simply waiting for a very slow server.
I think it should be possible to to abandon a too-slow server, and to allow a connection to a server to proceed while you do other things. I've written up and submitted a suggestion to that effect.
It looks like connection issues to WFS servers are fairly common. ESRI has written a page that I think was prompted by connection problems. It explains how to look at a WFS server in a browser:
That's a good idea, because if the WFS GetCapabilities URL won't return sensible results in a browser, it won't do so in Arc, Q or Manifold, either. So that's a good first filter to see if a WFS server is functioning well enough to try a connection.
If you ever encounter a WFS server that responds OK when you put the GetCapabilities URL into a browser, but it does not render as expected (after applying big patience in the case of slow servers), send a bug report to tech support. It could be a misconfigured server, or it could be a problem in Manifold, or it could be both. Let tech sort that out.
In the meantime, all the WMS servers I've tried seem to work. For example, the National Map WMS servers at
If anybody has a list of fast, guaranteed "on" WFS servers that are open to the public and can be used for testing, that would be very helpful!