INTERACT FORUM

Devices => PC's and Other Hardware => Topic started by: benn600 on June 29, 2009, 09:35:20 am

Title: Strange Mac Issue
Post by: benn600 on June 29, 2009, 09:35:20 am
When I first turn on my Mac, I can't connect to my two main shares.  After several minutes, I can.  If I go to finder and try to connect to the computer, it tries and says connection failed.  This makes my startup share connects fail plus I have to wait longer until I can actually connect.
Title: Re: Strange Mac Issue
Post by: bob on June 29, 2009, 01:41:25 pm
Try using the ip address directly and see if the behavior changes. i.e.

smb://10.0.0.1/whateversharename
Title: Re: Strange Mac Issue
Post by: newsposter on June 29, 2009, 05:44:17 pm
try also iSCSI as your storage sharing mechanism.  MSFT is moving to that pretty quickly.

Make sure that you've applied Server2003 tuning to your Vista 'server'.
Title: Re: Strange Mac Issue
Post by: benn600 on June 30, 2009, 12:44:48 am
This server is actually running Windows Server 2008 Enterprise x64 edition.  I continued setting it up--configured my web/email server software and placed it into production.  Since then, I don't have the problem on my Mac.  I will have to wait and see if it develops.  For now, I'm pleased to have the critical shared drive connect on startup.
Title: Re: Strange Mac Issue
Post by: benn600 on June 30, 2009, 09:41:07 am
So this morning it failed again.  At least now I have the IP address set static through DHCP so I can map it by IP address.  I'll see if it continues to work by IP.
Title: Re: Strange Mac Issue
Post by: zxsix on June 30, 2009, 10:54:56 am
First, I know nothing about macs.
Second, applying some IT knowledge of windows machines, check the settings for the network interface for a power saving setting and disable it.
We had a couple here at work that wouldn't reconnect to the network fast enough in the morning after waking them up and logging in that the login would fail since it couldn't connect to a DC to validate the login credentials.
This was solved by not allowing the network card to fall into it's sleep mode.