Mikezer: If it's not a network problem, it could be a problem with your shortcuts - in the prefs file.
One thing you can try doing is going to User/Library/Preferences and trashing. Then reinstall and see if life gets better. If this problem just sprang up and you've recently installed the 10.3.8 upgrade that could have caused grief. I did not have problems with ID but I did with Acrobat pro and MS Office apps, necessitating a reinstall.
You did not say how much RAM you have. Hope you have a lot to run 120 page ID docs.
One last thing you could have is a corrupted Adobe font cache. The Adobe fonts use their own cache, if the program crashes or stalls, requiring a forced quit, the cachce of the fonts in the doc can become corrupted - same as how a font in the fonts folder in 9 and earlier could get corrupted. Until the corrupted font cache is trashed, the problems will reoccur. So here goes my canned post on clearing caches, which I post all the time, because neither Apple nor Adobe does much to bring the problem to users' attention.
10.3 does not rely on the original font but on a cache of the original to avoid corruption of the original. Under OSX Adobe apps have their own caching system. One solution is to trash the Adobe font caches.
In Finder go to Find. In the Search box type "AdobeFnt" without the quotes. You chould get a result with things like "AdobeFnt.lst" and/or Adobe07Fnt.lst.
Make sure that all your Adobe apps are NOT running. You can then trash everything with the .lst file name extension. DO NOT trash anything that does not have the .lst file name extension. A restart of the machine is recommended after clearing a font cache.
There are other font caches within the various OSX folders. It's a good idea to clear these once in a while. It helps speed up performance and avoid corrupted caches. I once found 15,000 different caches on my machine. It's easiest to just download the shareware program Font Finagler to do this rather than searching all through your machine. You can find it via
Font Finagler does not clear the special Adobe caches.