Mac OS

Hi there. I work with interconnecting Macs and PCs in my office. I have one Mac running as a file server, but only as an AppleTalk server. Are your Mac clients/servers OS9 or X?

If you're on OS X, I would recommend switching the Mac servers to DHCP (Win2K can easily hack it)--the lag may be in the Macs looking through DHCP records, then resorting to their IP tables to find the server.

HTH

sweethemlock

Sweethemlock -

Thanks for the reply! The Mac servers are both OS9 and the workstations are a mix of OS9 and a couple of OSX. Won't moving the Mac servers to DHCP just add to the problem - more machines using DHCP?

Thanks again,

Mike Simone

Hello, Mr. Simone--

If your servers are OS 9, do your Macs connect to them by AppleTalk or TCP/IP? If they're trying to get to the IP address, this may (I don't know why, but hey...) be causing a hiccup with Open Transport...switching to AppleTalk would alleviate that.

Another question--do your OS X users notice the same problem? It might be a client issue--I seem to recall that OS 9 had some funny DHCP issues. A Google Search brought up:
http://www.macwindows.com/MacOS9.html

Sad to say, the answer might be to upgrade to OS X (don't jump at the thought of $129US per client--Apple sells 5-packs for $199US and might have a break above that) or resetting the Macs to static IP addresses.

What you've got here is a trust issue between your old
NT domain and your new Win2K domain. You can test
this by logging a user or yourself into the old NT
domain using the older user info.. You would in
essence be logging into the domain as {yourdomain}/
USERNAME
Not the new USER.NAME. When you log into the
server Win2K this way you get right into the new
domain. When you log in otherwise your going through
NT to find the domain which takes forever.

Sounds confusing- thisissue would go away if you only
ran Win2K servers. Another way around this is to use
MSUAM for Macintosh which logs you into the domain
using Microsofts authentication dialog instead of the
Macs built in authentication scheme.

Along with the advice given, I have one question. How long have you been using DHCP??? Have you ever run jetpack against it from your domain controller? Jetpack is a database repair utility. I know it was available for NT4 and not sure about 2000.It can also be run against your WINS db, if you use WINS. Interestingly, the DHCP database, at least under NT4, looks and acts like an access db!! Jet will repair and compact this db, which in turn mau help your performance.

This question was closed by the author