Looks like pipes aren't working properly through telnet. Had seen this same
problem way in the past with UWin.
They work correctly with a local UWin shell.
Here is a reproducible example:
1) telnet into host
2) "route print"
$ route print
===========================================================================
Interface List
14 ...02 1e 4f 13 cc 88 ...... Microsoft Failover Cluster Virtual Adapter
11 ...00 1e 4f 13 cc 88 ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Cl
ient) #2
10 ...00 1e 4f 13 cc 86 ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Cl
ient)
1 ........................... Software Loopback Interface 1
.......
3) route print 2>&1 | grep Cluster
(No lines returned)
_________________________________________________________________
Windows Live helps you keep up with all your friends, in one place.
http://go.microsoft.com/?linkid=9660826
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
