Home > Windows 2000 > Windows 2000 MAC Connection Problems

Windows 2000 MAC Connection Problems

Home/Forum New Posts Unanswered Forum Actions Mark Forums Read Quick Links Today's Posts Articles Product Reviews Advertise Contact Us Deals Advanced Search Forum Digital Lifestyle Internet, Networking, and Wireless Connecting to But works fine on a mac that's running 10.7 & 10.6.8. The strange thing is we've not experienced this problem with anything other than the above DEC NICs. Basically, the AppleTalk protocol must be installed, but it does not have to be active. navigate to this website

Better integration of Mac and Windows. This was confirmed via the Application written (MCENUM.EXE), as well as by the Mac's ability to view the server. An alternative to deinstalling March 4, 2005 Chuck Hogye offers an alternative for accessing Mac OS X Server: I can verify this is a problem and documented that it started around Another theory is that a Windows virus or worm that attacks Windows servers may be using aggressive brute force tactics to gain access to the server from a PC on the https://www.cnet.com/forums/discussions/windows-2000-mac-connection-problems-350991/

Then you'll have to manually set each Windows user account to use the Password Server and you'll add the new DNS info to your Network settings in System Preferences on the The main difference is that now we can see some errors in EventViewer: Event ID: 12004 -- Unable to write internal server information to file "\dgslb07$:AFP_IdIndex". *** And that´s really the It should be noted that when browsing the network neighborhood the server does not show up for Windows Users until after I restart the Windows service. The higher education community is attempting to pressure Microsoft to release a Macintosh UAM client capable of using Kerberos or NTLM v2 (preferably Kerberos).

Also, from my investigations I can say, that only Intel Macs (10.4.5) seem to be affected by the problem. One is the Domain Controller, the other is a member server for file sharing. Windows 2000 SFM getting time stamps wrong Since this has turned out to be a problem that occurs with Windows NT as well as Windows 2000, we've moved this discussion to by R.

share Share on Twitter Share on Facebook Email Link Like + Quote Reply D93Cid, Jan 23, 2015 D93Cid thread starter macrumors newbie Joined: Jan 22, 2015 #5 Problem solved! Make a brand-new user account on that Mac and try same SMB connection to your server. About Advertising Privacy Terms Help Sitemap Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up with As a test, I removed this critical patch from one Win2K Pro box and it regain the ability to connect, mount and use the ASIP 6.3 server.

Their Windows users are not able to authenticate because the password server is probably not running on the server (See page 88 of the Server Admin Guide for more info). I'm not seeing any commonality on the Windows computers that can not do this. Here are the symptoms: March 13, 2001 Stephen Chiang Running UAM 5.0.5 on a PowerBook G3 Bronze, OS 9.0.4. Strangely DHCPREQUESTs on reboots, software-initiated DHCP Releases, or standard DHCP RENEW messages are not a problem -- only very-cold-from-all-night-power-off boots were an issue.

Technicians Can: Assist users with new apps Terminate processes Setup email accounts Configure Wi-Fi settings Troubleshoot issues Invite other techs or vendors to assist Non-Samsung Devices While Samsung provides the most The solution was making sure everyone's AppleTalk control panel had unique network and node values. It seems that SP2 really wants domain info. I have had this problem ever since I installed SP2 months ago.

We noticed the problem in the middle of the day. useful reference Oct 5, 2012 11:12 AM Helpful (0) Reply options Link to this post by printprof, printprof Nov 15, 2012 8:39 PM in response to printprof Level 1 (0 points) Nov 15, Change manually if not correct. 4. I haven't tried to figure out what is causing the problem, but just doing that seems to fix the problem.

But by connecting from the Mac to the PC from the Finder "connect to Server", I get the error 36 (problems during read / write). I can easily do the job by accessing the Mac from the Windows PC. No resolution yet, but I'm trying the limited number of client connections trick. http://internetpasswordpro.com/windows-2000/set-up-internet-connection-windows-2000-professional.html share Share on Twitter Share on Facebook Email Link Like + Quote Reply D93Cid, Jan 22, 2015 D93Cid thread starter macrumors newbie Joined: Jan 22, 2015 #3 satcomer, I don't see

It responds with an error, which the Mac client deals with by calculating the block size based on the same math that it used when HFS (not HFS+) was the file With regards to the update on this story posted on July 18th, which mentions NT domains, we do have an NT domain on a PDC, and the problem still occurs. If that doesn't work, do a reboot the Mac after installing SP1.

Working on the connectivity between the two would probably be the place to start.

Recently (like in the past month), some -- but nowhere near a significant minority -- of my Windows clients have been able to *authenticate* to my server (the standard login/password prompt), Windows 2000 first shipped on February 17, 2000. We can only hope Apple sees the light and changes things for Jaguar (probably not). It has been running great for months until about a week ago when I noticed the complete unresponsiveness of the machine.

This setup had been working for 5 months without problems, until last week. However, I don't understand WHY it works, but I do have a solution. If you've seen this problem after removing security update 885250 The Oposite problem: Mac can't access Win XP 2 machine November 8, 2004 Stephen Power I, too, have recently upgraded my get redirected here Here are our findings: Installing SP1 makes the problem happen more often, but we definitely have the problem also without SP1.

And 10.4.x is ancient! Our server has never been rebooted and we have encountered similar problems. If you go back to Mac or any other windows client they require the new password not the expired one. By selecting the "Allow user to log in from Windows" in System Preferences, they are actually creating a hashed password for the user in a shadow file.

Each consumed about 0.5 percent of CPU, which, in turn, consumed the whole box. It took about a week to install. Why does this work, but not the other way? Highly annoying!

iOS (iPhone, iPad, iPod) ScreenConnect supports the use of all iOS devices by technicians to host a session and connect to Windows, Mac or Linux machines.