Search results

heh heh heh The last upgrade I did was to 10.4.4

I have a feeling you are going to find out that 10.4.6 is the culprit. I remember reading somewhere during my frantic search last night to resolve my issues that once you update to 10.4.6, you lose the ability to double click to open many Adobe files on a network server. I think it has...

Obtain a copy of Cocktail. Use it to clean out all of the caches on the system and it should bring back your user accounts without having to move them. I have run into this at one time or another on all of the G5's that I manage.

I've had the same issues as well on a couple of my G5's running Tiger. Booting into safe mode allowed me access to the machines, but I could not find anything wrong. The normal user account would exhibit the behavior, but any other account would work just fine. I used Cocktail to clean out...

I have two locations where I have just installed new G5's. Both locations have Win2K servers running SFM. One location get SBBOD, the other one does not (or very rarely). The difference between the locations is that one has Gigabit Ethernet to the desktop, and the other one does not (SBBOD...

I was wondering if anyone has used Helios Lan Test to test the speeds on the network between clients and servers. I have run tests on OS9, OSX clients to Windows 2K Servers running various flavors of AFP. The servers all remain on GB Ethernet (single pipe and LACP pipe) and all I do is change...

Monkey: You are correct about the slashes; Got them ackbasswards (Unix, Dos, Mac, I can never remember them all). As for the DNS, it depends on if you are on a private network with its own DNS (like here in my company), or using a public DNS. One trick I have found is to edit the Mac's hosts...

I think I found some clues to where to look to solve this issue. You cannot connect via AFP because Tiger changed the way it works; Tiger will only use AFP over IP, not AFP over Appletalk (which is what NT runs). Your SMB issue is most likely related to the fact that you will need to fiddle...

You also may want to look at the following site. It has a great deal of information on integrating Tiger and Windoz. http://www.macwindows.com/tiger.html

Try connecting via SMB. In your Connect to Server window try using smb:\\servername\sharename See if that works

After seeing that all of this worked up until you added the 10.4 machine into the mix sure smelled like the Active Directory issue everyone else has been having. Sorry I couldn't be more help, and please don't take the "IT Geek" comment personally; I am the IT Geek in my shop, and for the most...

Ask the IT Geeks? If you are him/her, you may want to seek out the ex-IT person and ask them. Short of that, look at all of your servers (Microsoft ones only) and see if they are running either Windows 2000 or 2003, and if they have users in the Active Directory User and Groups (under...

no negativity taken. . . just need to remember how to read

One last question: Do you know or can you find out if there is an Active Directory Server (it will be a Microsoft Windows 2000 or 2003 Server) on your network? I do know for a fact that there have been MANY issues with 10.4.x and Active Directory. In most shops that have Microsoft Windows...

I do not remember seeing anything in the posts regarding the Mac being able to connect to anything else. Can you connect to anything with the Mac (internet, another Mac, etc)? Can you open up a terminal window and use the ping command to ping anything else on your network? As for the...

My fault; I did not correctly read the OP. I just jumped into the "Big question" of forcing it to work.

Do you have any other servers on your network? If so, can you connect to any of them? Also, do you know of any reason why you are running NetBEUI Protocol NWLINk IPX/SPX Compatible Transport NWLink NetBios Ina purely IP network, you should not need them.

You may want to reset the router to it's factory defaults (not knowing where it's been, it could have been configured in a non-default way). Here is the url...

go to Start Menu --> Programs --> Administrative Tools --> Windows NT Diagnostics In the window that appears, it should tell you what version and what service pack it's running. You really should be on SP 6 with all of the security patches. As for your network protocols, I see you are...

Another quick question, what network protocols are you running on the NT box?