Are we talking file sharing here? AFP services to your NT servers or SMB? Any relevant info in the logs? What troubleshooting steps have you tried?Krazykrl said:Since upgrading I can no longer connect to my NT-servers.
A weird thing that seems to work for no obvious reason. Open Network Utility in applications/utilities. In the info panel, switch the Network Interface dropdown from whatever it's on to one of the other options. Wait 30 seconds. Switch it back. Close Network Utility. Try connecting to a server.Krazykrl said:I have recently upgraded some of my macs to 10.4.2. Since upgrading I can no longer connect to my NT-servers.
Panther works just fine.
it was probably a configuration problem, there is no way that tiger and panther networks do not work with each other.jayscheuerle said:Tiger is incompatible with our older Mac network here (We have only 3 machines running OSX and they're all 10.3.9). It took me a day and a half to get my machine back to 10.3.9, which required a complete wipe and reinstall.
I'm done guineapigging. I should have brought my iBook in (10.4.2) and tested it first...
I concur. Of the ~150 Macs I suspport, they're mixed with 10.2, 10.3, and 10.4. With a dash of Win2k3 and AD thrown in for taste.superbovine said:it was probably a configuration problem, there is no way that tiger and panther networks do not work with each other.
We are talking AFP. Possibly SMB as well since browsing thru the Finder I believe is SMB.yellow said:Are we talking file sharing here? AFP services to your NT servers or SMB? Any relevant info in the logs? What troubleshooting steps have you tried?
Glad to know I am not alone.AlBDamned said:This is exactly the same problem we are having but thisnew thread is much clearer in the problem description than mine is.
We've got2 new Tiger G5's and they won't see our NT server. Neither does my Powerook, though it sees my Desktop and nothing else. It's really odd.
yellow said:Idle speculation: Is AppleTalk turned on on the Tiger box? Its possible that an ancient beast like NT is using actual AppleTalk to communicate, rather then AFPviaTCP?
Thanks for the link. I will check Appletalk on the Tiger boxes when I get in tomorrow.yellow said:I'm just saying that you may not have turned AppleTalk (the service) on on the Tiger box. And it may be that NT is relying upon AppleTalk. I don't know how up to date the AFP services on NT4 are.. I suspect they are really, really, really, really, old. I don't know if they cope with AFPoverTCP (I suspect not) which is what Apple officially switched after 8.6, but still leaves legacy stuff that gets depreicated with each passing iteration of the OS. Make sure AppleTalk is turn on (in Directory Access is one place to turn it on) before continuing to try and connect to the NT server.
What's SMB?yellow said:I suppose all the files are on a Mac volume on the NT server too, so you cannot get to them using SMB?
I hate to say this to you two, but someone has to..
Maybe it's time to drop the 10 year old depricated Windows NT Servers? You could leap forward in time by 5 years with Win2k Server!
There's just so much wrong here..AlBDamned said:What's SMB?
Our IT guy just glared at me when I relayed the Win2K server idea. There's no way they will do it in the near future apparently. Stuck with an injured tiger!
Won't you stop hijacking this thread please? If you want to help out, I would appreciate that.jayscheuerle said:Tiger's the first version of OSX that MUST connect via TCP. Our server is older and not configured that way. I'm the OSX guinea pig and the IT guys won't do ANYTHING for me alone...
Not kidding about SMB, hence the smiley. I'm no computing grad just taken more than a keen interest in Macs since I started using them seriously professionally. Subsequently, most things like protocols, SMB etc etc, still go way over my head.yellow said:There's just so much wrong here..
You're kidding about SMB, right?
SMB = Server Message Block, basically the TCP protocol that Micorosoft Windows uses to do file transfers. On UNIX, there's a service implementation called Samba (SaMBa, get it?) that is used to talk SMB with Windows boxes. This is how a Mac can communicate with Windows boxes without resorting to turning on AFP services on the Windows boxes.
Hopefully your IT person isn't resisting because he's stubborn and doesn't like change. Hopefully you're still rocking WinNT out of necessity.
No. THEY work together. It's just that once moving to Tiger, I could no longer connect to our server. I found this:superbovine said:it was probably a configuration problem, there is no way that tiger and panther networks do not work with each other.