I believe that you won't be able to provide site2 over 192.168.1.160:443. It's an intentional limitation in IIS. The SSL negotiation provides to the client the certificate that identifies www.site1.com. That negotiation happens before the HTTP session starts. Because of that SSL negotiation, the browser will never ask for a particular virtual hosted site, because the site has already identified itself. You must run SSL-enabled web sites on different IP:port combinations. For instance, you could run site2 on 192.168.1.160:8443, and configure that port to be forwarded on your router. However, that port would need to be entered in the browser to pull up the page like so: "https://www.site2.com:8443/" If the user entered https://www.site2.com/, they would get an invalid certificate error, because they are connecting to 192.168.1.160:443 -- or site1.com. This may not be as big of an issue if everyone comes into http://www.site1.com and http://www.site2.com. Then, when pages on site1.com or site2.com send people to the encrypted pages, you can direct them appropriately to https://www.site1.com or https://www.site2.com:8443. You could also obtain a new public IP address for www.site2.com. There will probably be cost involved, though. If you're using a SOHO Linksys router, it may not be able to handle translating a second IP address on your Internet link. If you'd prefer to go down this road, you'll want to check the router documentation to see what it can do. Also check with your provider to see if they do offer multiple IP's. Hope this helps -BTKnight

You're on the right track. You don't need the -name parameter, though you'll probably want to make sure that each thing "find" locates is a file, and not something else like a directory or symlink. "find" can be somewhat annoying in that it will spit out the entire relative pathname for each file it finds. That is, find ./dirA -type f will yield ./dirA/file1 ./dirA/file2 To get around that, just chdir into dirA before doing the find.

$ cd dirA
$ touch file1 file2 file4 file5
$ cd ../dirB
$ touch file1 file3 file5 file6
$ cd ..
$ ls dirA
file1 file2 file4 file5
$ ls dirB
file1 file3 file5 file6
$ cd dirA
$ find . -type f -exec rm -f ../dirB/{} \;
$ cd ..
$ ls dirA
file1 file2 file4 file5
$ ls dirB
file3 file6
$

I would have answered earlier, but I only joined last week. :) Hope this late reply helps.