Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


Sporadic error occurring for connectivity to Windows based file server from MAC X workstations

Posted on 2006-04-10
Medium Priority
Last Modified: 2013-11-17

  We have a bit of an unusual connectivity issue.  We have currently 45 or so MAC 10 workstations that authenticate against a Window NT domain.  That authentication is passed to certain shares/volumes on a Windows based file server.  Some users experience the error below when letting the automated script connect to this File Server.  This doesn't occur all the time but sporadically.   All MAC servers, workstations and printers are on the same VLAN.  This error started occurring when we went upgraded the wiring closet on the floor where all the MAC users are to newer Cisco switches and a VLAN scheme.  The users don't have any issues authenticating to the NT.Dom domain.  

  ISSUE:  When logging onto a PC in the morning, the user has to manually connect to the necessary file server to connect as sometimes the automatic connection gets the following message and never completes.  
  ERROR MESSAGE:  Looking up "<File Server Name>".  Nothing happens and it just sits there.  If you click ok and then manually map the drive, a user can connect immediately to the share.  

Question by:moha0018
  • 2

Accepted Solution

ryanhunt earned 1500 total points
ID: 16434142
What it sounds to me is delay/lag in getting DHCP/DNS information. The error says it 'looking up'.

I know that many of the Cisco auto-sensing ports take some time to detect on a mac, especially if you have spanning-tree turned on. You want to check that on those macs that are getting the erorrs, that at that stage they have an IP address, and proper DNS information. YOu also want to check when this script runs, if it's a StartupItem - make sure it's dependent on as many scripts as possible to ensure it runs last.

I'd say - if it's only 45 workstations, hard wire the hostname for the servers into a /etc/hosts file, it's lame, but it'll be a quick win. Also, you want to talk to your cisco guys to speeding up the macs network type connection. Possibly go into all the macs, and manually set their ethernet type (to say 100TX/Half Duplex) it might speed up the time it takes to detect the port.

Finally, check on the cisco's that they aren't blocking anything, or there is any form of whack cisco rate limiting going on. I'm not a cisco guy, but it's worth asking?


Author Comment

ID: 16438746
Hi Ryan,

  Thanks for the feedback.  I am goint to work with our Cisco folks and see what happens.  


Author Comment

ID: 16544187
Solution worked.  Hardwired the hostname.  It was also a permission issue on the particular volumes.  Cisco wasn't an issue but thanks for mentioning.

Point awarded fully.

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article we discuss how to recover the missing Outlook 2011 for Mac data like Emails and Contacts manually.
Worried about if Apple can protect your documents, photos, and everything else that gets stored in iCloud? Read on to find out what Apple really uses to make things secure.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Loops Section Overview

571 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question