I recently needed to print to our HP Laserjet 4050 which is set up as a networked printer connected by parallel port to a Windows NT 4.0 PC. The smbutil utility included in OS 10.1.x doesn't support print very well, apparently, and I was never able to successfully print with it. The complete Samba package does allow printing to Windows NT 4.0 machines, so I decided to try that. It's actually pretty easy to do. I've only done this with postscript files to a PostScript printer.
One of the nice things about having access to SSH is that you can port-forward a connection through an SSH tunnel and know that your connection is reasonably secure compared to an open data stream. Following the tips given on afp548.com, I was able to easily get Timbuktu to run through the SSH tunnel and connect to my home OS X machine by doing the following in Terminal:
ssh [servername or IP] -l username -L 10660:127.0.0.1:407
Authenticate the SSH connection and once you are in, switch over to Timbuktu and enter the following in the connection name:
You should immediately be connected to your remote Timbuktu host as if you were connecting through standard TB2 ports.
You can do a lot more with this handy trick; read through the rest of the article and get a feel for what can be done.
If you frequently move your laptop between networks, as I do, you will notice that when your IP address changes, server processes get upset. Darwin (and thus MacOSX) includes a way of detecting and fixing this situation.
I've composed a hint and sample files and posted them on my website. The hint is specific to SambaX, but the explanation should help you do this for any server process.
The company I work for uses a Novell network, which was fine when I was using Mac OS 9, but I recently got upgraded to a G4 800 running OS X. There isn't any Novell client for X (yet?). There is a "Novell Native File Access" product, but that's more money and the company's already spent a bundle on my hardware and software. So ... cheap fast fix time! I've got an old Pentium 120 in my office.
After getting our IT guy's go-ahead, I installed WarFTP (free) on it. I set myself up as a user and pointed the server at the mapped Novell network drive. On my Mac, I used RbrowserLite (free) logged in, and saw all the files I needed ... very cool.
A couple of drawbacks:
Resource forks will be bopped, if transferred to the server (I believe Native File Access allows resource forks).
The PC has to be on, logged into the network, and running WarFTP.
Other than that, it's mighty fine.
[Editor's note: A creative solution to a fairly large hole in OS X's networking abilities. If anyone has news or info on a solution that doesn't require a separate PC, please post what you know! We run Novell at work, and I'd love to get to it from my OS X box...]
The network diagnostic utility nmap compiles perfectly on OS X 10.1.4.
[Editor's note: If you have fink installed, you can simply do a "sudo fink install nmap" to get it up and running. nmap is a very powerful tool for finding open ports on your network, amongst other features. Of course, as with some of the other tools covered on macosxhints, it could be put to use in a malicious manner. Use it wisely to help secure your own network.]
For those who like statistics - and I suppose I'm one of them - here are some tips for viewing network traffic, both realtime and afterwards.
netmonitor is a small app that gives nice graphs, it can be adjusted to be displayed only in the menubar (no dock icon) and is a great little tool.
darkstat is a background deamon that gathers stats 24/7. Use it to view bandwidth per minute, hour, day or month and per host/protocol using a web-interface. Simple and effective.
ntop (also here) is a great app like 'top', but for networks. It's the app darkstat is a spin-off from, and it gives you a load of stats you can throw a stick at - also using a nice web-interface. Downside: it uses 75% of CPU resources here; I'm looking into it.
Use tcpflow if you want to see the data that goes in and out of your Mac in plain text. Great to cheat with flash games that submit scores to unknown hosts ;)
[Editor's note: I haven't tested any of these network monitoring apps.]
I've been looking for some time for a way to network our Epson SP 870 colour photo inkjet under OS X. It's been a nightmare - but three months on, I've finally got it working!
We have 18 Macs connected over an Airport Network in our office, all running OS X. Epson's drivers don't support networked printing over TCP/IP, and Apple told me that USB sharing was not available in classic. But it seems it is!
Read the rest of the article for our workaround solution...
Like a lot of OS X users on NT or Windows 2000 with ISA Server, I had a problem with authenticating behind a MS Proxy Server. Every time I used Explorer, I had to authenticate my user name and password. On top of that, programs like Software Update, Quicken and Watson could not communicate correctly.
Our IT person found that the Mac was not creating a session with the Proxy Server even though Macs were supposed to be able to communicate as a secured NAT client. However, there is a simple work around that has corrected these problems.
On the Proxy server, allow the leased or static IP address for the Mac to fully "open up" to the proxy. This allows the Mac to communicate directly with the Proxy, thus allowing the Mac to communicate as a secured NAT client. Once this happens, all the programs communicate with the Proxy Server and they no longer have to authenticate with every use. Since we have done this, I have not had to authenticate Explorer.
As it turns out, Apple File Sharing is configurable, via NetInfo. Despite the dearth of documentation, you can even share folders other than ~/Public. Alas, doing the NetInfo / System Preferences dance is a hassle. So I scripted it.
Now you can control your file sharing with a single command from the comfort of your shell of choice.
[Editor's note: You can also control shares with the shareware program SharePoints, which has been discussed here before. But it's nice to have a command-line option available as well, so thanks to 'logan' for putting this together.]
For a while, I have been trying to get the Java VNC viewer working so that I can VNC into my computer from any Java-compliant browser. this proved to be a bit of trouble but, don't worry, I finally got it working. After compiling the souce code, I played around with the class files and got it working. This, combined with OSXvnc, is a great solution to remotely control your computer from any computer terminal.
It can be found on this boring site of mine. I would like to say that I take no credit for creating a "port"; I merely compiled the source code and put it in a neat package ;-).
[Editor's note: The Java VNC client has been mentioned here previously, but instructions on compiling the client were not included; "c.i.t" has provided a ready-to-run version.]