When you have multiple network connections, sometimes you want to prefer one to be used as “default” (i.e. because it has higher speed or lower latency).
Windows already tries to accommodate for that by assigning “metrics” to your network connections. They depend on the kind of network (wired over wireless) and speed of the connection.
To see the current default network routes and their metrics, you use the route print command and filter it with findstr like this:
route print | findstr /C:"Metric" /C:" 0.0.0.0"
The “0.0.0.0” string is to filter out the default routes, and “Metric” includes the header line.
For one of my XP machines, the result is this:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Now, even though both metric are 10, my 192.168.71.1 gateway is much slower than my 192.168.171.1 gateway, so I want to prefer the last one. Read the rest of this entry »
Never noticed this file before until I got some trouble with several systems sharing parts of a roaming profile.
The content of my %USERPROFILE%\ntuser.ini file is this: [General]
ExclusionList=AppData\Local;AppData\LocalLow;$Recycle.Bin;Tracing;PrivacIE
[ProfileLoadType]
LastUploadState=Complete
[[The ntuser.ini file is used to set up the user roaming profile components that are not copied to the server.]]
This can happen when your Windows Security Token bloat has struck:
… the problem could be minor, or relatively major. You may get weird access denied messages, applications crashing, or strange entries in your event logs. Or worse yet a SID for a group that has a ‘deny permission’ on an object could be dropped into the virtual bit bucket, allowing a user to access a resource they are not supposed to access.
…
Summary of fixes for token bloat:
Use global or universal groups instead of domain local.
Increase the MaxTokenSize on all computers
Convert security groups to distribution groups if they are only used for email lists.
…
There is a hard-coded limit of 1,024 SIDs for the Kerberos PAC (privilege attribute certificate)
…
Kerberos token size still remain to 64k in windows7 / win2008r2.
He is the kind of person that does use a computer, but doesn’t like change. No wonder, as he is well into the retirement age and the systems he has used in the past all lasted for a very long time.
So it is going to be a big change for him when he needs to upgrade from Windows XP – that he used for over 10 years – to something else. Probably more on that in a later stage (if Windows Live Mail exists by then).
Back to the problem at hand: he couldn’t see attachments from certain Outlook users, though those users insisted .
I hadn’t used Outlook nor Outlook Express for a long while but it was fairly easy to track down the cause by viewing the message source in either of these two ways:
As soon as you see the full message source, there is a ms-tnef encoded Winmail.dat attachment in the affected messages. You find it by searching for a line that starts with “begin” followed by 2 spaces, “666” or “664” (it is one of the means to fake UUencoded attachments and hide text from Outlook Express).
Winmail.dat is known to cause all sorts of problems, even the NY Times devoted an article about it. It basically encapsulates the content of a message including any attachments into RTF: a Microsoft proprietary – but documented – standard of encoding formatted text.
The “trick” is to configure Outlook for using HTML to format text (or use plain text without formatting) instead of RTF. You can do this either globally, or per recipient in the address book:
Researching this, I also found about TSWindowClipper which allows you to seamlessly integrates remote apps on your client by integrating a DLL inside the MSTSC software using the official virtual channels.
Back to rdesktop: I really wish the documentation was better, but it contains some very interesting source code.
rdesktop is an open source client for Windows Remote Desktop Services, capable of natively speaking Remote Desktop Protocol (RDP) in order to present the user’s Windows desktop. rdesktop is known to work with Windows versions such as NT 4 Terminal Server, 2000, XP, 2003, 2003 R2, Vista, 2008, 7, and 2008 R2.
rdesktop currently runs on most UNIX based platforms with the X Window System, and other ports should be fairly straightforward.
rdesktop is released under the GNU Public Licence (GPL), version 3. Please send feedback, bug reports and patches to the appropriate mailing list. Patches can also be submitted to the SF patch tracker.
The latest stable version of rdesktop is 1.7.1 (edit: this was at the time of writing, for the current latest, check here). This versions solves major issues with 64bit version and smartcard support among a few minor fixes.
The Wiert Corner - irregular stream of stuff 