Macintosh: Network connection fails after 5 to 10 minutes of initial session.

Correction:  ...server A will* with

Can anyone assist me with this problem?

Thanks.

What happens when it fails?  Is he working on a file?  Or does he just lose the mount on the desktop.  How long after can he connect again?  How is he connecting?  Afp or SMB? During the time when he cant connect, can other users connect?  DUring this time, is he connected to other servers with no problem?  

Thanks for your reply.  My answers to your questions are in Quotes.

What happens when it fails?
"He loses his connection to the Windows server A"

Is he working on a file?
"At times he is working on a file and is able to save and not at all either"

Or does he just lose the mount on the desktop.  
"He does lose the mount"

How long after can he connect again?  
"maybe 10 to 15 minutes later, and sometimes has to reboot"

How is he connecting?  Afp or SMB?
"SMB"

During the time when he cant connect, can other users connect?  
"Yes, according to the best of my knowledge"

DUring this time, is he connected to other servers with no problem?  
"Yes, according to the best of my knowledge"

Thanks for your assistance.

If this problem only happens with his workstation, then the problem is there.  I would repair disk permissions.  Also you might consider blowing away the user profile.  See the link below.

http://www.macattorney.com/ts.html

Also.
When it happens again, i would try the following:

Try connecting via afp
Pinging the server
Connecting to the server from another workstation
Connecting to another server from his workstation

Hope this helps.

Thanks for the heads up njxbean.  I will try it this morning around 10 am and will let you know how it pans out.

no luck with using the repair disk permissions.   do you have any other suggestions?

thanks.

Did you try:

Connecting via afp
Pinging the server
Connecting to the server from another workstation
Connecting to another server from his workstation

when it happened?  what was the result?

Sorry for the delayed response.  

I don't know how to connect using afp.

We were able to ping the server, we download a tool to ping.

We are able to connect to the server from another workstation successfully.

We are able to connect to the another server from his workstation successfully.

I also rebooted the server thinking the Mac services were hanging, but this didn't fix the problem.

Does the mac rely on a host file?  Maybe I could add an entry for the server in the host file.  Do you know where the host file location is?

Thanks for you help.

to connect va afp you have to have file services for mac running on the server.  THen you need to download the microsoft UAM module on the mac.

http://www.versiontracker.com/dyn/moreinfo/macosx/12677

then when you connect to server use afp://servername

Try that.  I think that will work better. Also, you dont need a third party tool to ping.  Its built into the network utility.  You can find that in the applications:utilites folder.

I also missed something- you mentioned to delete his profile, where would I go for that?

Thanks for the latest reply.

I have file services for mac running on the server.  So I need to download the microsoft UAM module and install it.

What do you think is happening?

I was thinking about adding server info in the host file.

Deleting the profile simply means creating a brand new user id and password for the person.  This can be done from the accounts pane in system preferences.  Before deleting anything, you should just create a new ID and see if it happens there.  If it does, then i wouldnt worry about it.  If it doesnt, then move all his data to the new ID.  

Hello njxbean,

I removed the profile and recreated the profile.  This time the connection lasted for 20 minutes before the error said dead connection.  

Error messages:
Kernal 0:  smbfs_aclsflunksniff:  group sid didnt map
Kernal 0:  smb_iod_sendrq; TRAN_SEND returned fatal error 32
KernalEvent Agent 29 received VQ_DEAD event (32)
KernalEventAgent type smbfs, mounted on /volume/public, from //domain, pcname, dead
KernalEventAgent found 1 filesystem with problem

Thanks again for your help.

it's funny you mentioned that because we had tried it shortly after my last post,

**drum roll please**

IT Worked.

Thanks for you help.