Some Notes on the Machines

A very good example is on this page:

http://ss64.com/nt/ftp.html

Here is an automatic generator of IPv6 private address ranges:

http://www.simpledns.com/private-ipv6.aspx

As long as you have an administrative password for the domain, this works:

http://www.howtonetworking.com/RemoteAccess/enablerdc1.htm

The noteworthy Liz Landry contributes:

Just wanted to let you know that I found out this morning that the newer Nvidia drivers are having problems with Remote Desktop and causing the computer to lock up and have to be hard booted.  The fix is as follows:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Add a DWORD and call it:

SessionImageSize 

Set it to hex size 20.

Then reboot and use RDP.  There should no longer be problems with the computer locking up.

The best FTP server software for Windows right now, is very probably zFTPServer:

http://www.zftpserver.com/

It has all the features of FileZilla, but works well under Server 2008, which FileZilla does not. It is free of charge, but there are for-pay additional modules, including a Windows authentication module which looks very interesting indeed.

To connect to a Windows 2003 domain controller by LDAP, and search for email addresses embedded in user objects, use the following, replacing the first line elements as if the local domain were “localdomain.local”.

dc=localdomain,dc=local
Port: 3268
Auth: NTLM
Object name: mail

ATT is managed aggressively against spam. It takes little to nothing for a domain to end up on their RBL list. To inform them that they have made a mistake, fill out everything here:

http://worldnet.att.net/general-info/bls_info/block_admin.html

including at least one or two things on the bottom, and in 2-4 days, it should be fixed.

Here is a very good page with sample SMTP commands via telnet:

http://www.yuki-onna.co.uk/email/smtp.html

Here is some excellent information:

http://www.owlfish.com/thoughts/winipp-cups-2003-07-20.html

This also works well on LAN/WAN with many print servers.

For most Internet time server synchronization to work, port 123 has to be open. This works for both NTP and SNTP. There are other protocols, not very often used; a comprehensive discussion is here:

http://www.kloth.net/software/timesrv1.php