I realize that readers might be getting tired of the pipe-related tricks, but here's a quick one that may be of use to anyone running a webserver from OSX. As you realize, the Net is in for yet another round of annoyance with the introduction of the nimda worm. Like its CodeRed predecessors, it primarily targets Microsoft IIS servers, not Apache which is installed by default with OSX. While Apache is immune to this PARTICULAR attack**, it is still affected by the fact that an infected Windows system will launch hundreds of attempts to find other vulnerable systems, thereby creating a denial-of-service situation across the Internet.
Anyhow, if you do serve HTTP from your OSX box, here's a quick way to check if a nimda-infected system has contacted yours:
to show all the unique IPs of infected systems. Or you could add:
| wc -l
to the end of the above command to just see the total number of different attempts made.
** A gentle reminder that choosing the Mac as our platform doesn't inherently make us more secure from net attacks and exploits -- it's just the fact that more people are using Windows at this time, so that's where most of the blackhats turn their attention towards.
I had a devil of a time getting my DSL, LAN, and LW 16/600 to work together on OS 10.0.4. Finally today, thanks to one of the geniuses at the VA Apple store, I have it all working and I thought I would pass along what I did for those suffering the same agony.
Read the rest if you'd like to learn how to have one device (Ethernet) configured to use multiple protocols at the same time...
If you want to access your OS X computer from remote locations, you've probably encountered some of the same frustrations I did in easily connecting from anywhere. I've tracked down Java software that allows (more or less) secure, easy access from any computer with a web browser.
The built-in SSH server, and the VNC server compiled for OS X, are invaluable tools for complete remote control, but have a weakness: both require specialized client software at your remote location, which is difficult to find at a typical internet cafe, corporate, or educational computer.
Fortunately, smart people have written Java SSH, VNC, and FTP clients: so read the rest for my advice on setting up your built-in Apache server for full remote access.
Question: how can I automatically mount a server at login? I've got two machines both running OS X, and I want one to always access the other as a server when I log in, but can't for the life of me figure out how to do that.
I'm an instructor at a small technical college and the only Mac user in my department. Our network is heavy on Windows, as expected, with some UNIX. Our Graphic Design department uses Macs, of course.
Anyway, our printers are HP LaserJets shared over the network. They support all types of connections, including Appletalk and TCP/IP. Under OS X, the HP PPDs are only available using LPR (TCP/IP) printing and I couldn't seem to get that working. I had to use Appletalk instead which only allowed me to print Postscript. (I try to print text, as from BBedit and get an error message.)
Just this afternoon, however, I figured out how to connect to the printers using TCP/IP so I now have full use of the HP PPDs.
From the Print Center, select Add Printer and from the connection type pulldown list choose LPR Printers using IP. Enter the IP address (or IP printer name if it's registered) and uncheck the Use Default Queue on Server box. In the queue name field, enter in the name that you want to use for that printer. (Try not to use spaces. Use underscores instead.) Select the printer type from the pick list and click on Add. The printer will appear in your printer list and be ready to go.
My problem was that I was trying to use the default queue rather than setting up my own queue name. (Ironically, this came to me while teaching a group of students how to set up LPR printing in Windows.)
I am attempting to serve a site off my home machine (a G3 w/cable modem connection). I successfuly (I thought!) installed Apache-PHP-MySQL using the hints on this site. I have been happily coding PHP pages, creating and using MySQL databases, etc., and everything works like a charm when I view locally.
However, no one can seem to access the site from outside. Specifically, I have www.philwebster.com pointed (via a free domain hosting service) to my IP address; the redirection works, but then the browser hangs at "Connecting to [IP address]..."
This is mysterious to me because:
1) When I view the site "locally", I do NOT use 127.0.0.1, but rather the IP address assigned by my ISP (this is assigned using "DHCP" but does not change; I've checked numerous times). I thought this meant my request would go out over the internet and "re-enter" my box from the outside, but apparently not...
2) I KNOW I was able to access the site from outside in the past, and don't know what has changed in the meantime!
I've tried serving from /Library/WebServer/Documents as well as Users/pwebster/Sites and neither seems to work. I even messed around with various settings in httpd.conf, including Port, Listen, etc., thinking it was my ISP blocking Port 80, but to no avail. Ditto with pwebster.conf, .htaccess files, etc.
Anyone had this problem and/or have suggestions as to a fix? This is driving me absolutely crazy! Thanks in advance...
For those of you using a Cisco VPN server, they just released the Mac OS X version of their VPN client software. Ask your VPN support person, whoever that may be, for the specifics.
[Editor's note: I can't find any reference to the OS X Client on the Cisco web site, so it does appear you'll need to talk directly to your Cisco rep. If someone has a URL with more information, please pass it along as a comment to this article...]
If you're interested in seeing what things get sent out by your machine (for example, hidden data sent out as part of a software install or what cookies are getting set while browsing), check out tcpflow. tcpflow is a packet sniffer for unix-based operating systems. It's got more features than tcpdump (which is included with OS X). Marc Liyanage has created a Mac OS X installer package, which is available here: