moha0018
asked on
Sporadic error occurring for connectivity to Windows based file server from MAC X workstations
Greetings,
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.
Thanks!
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.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
Point awarded fully.
ASKER
Thanks for the feedback. I am goint to work with our Cisco folks and see what happens.
Monty