alright, I'm on here from work- we've got network problems and I'm sick of it. Our IT guy is stumped- so lets here your ideas-


I'm at an architecture firm- we run 8 network drives off of two servers. Cat6 cable to all machines (58)
(2) 3com switches

we have 5 terabit sized drives, (2) 30 gigs, and (1) 150 gig
the data drive, all the project files is the H drive-


People are getting randomly booted from the network- I got booted about 30 mins ago- no errors, no logs- you just get dropped. you will have access to the direct file tree you are working in, and any related structures and the accounting drive (the job log/billing program) you get dropped from the other 6 drives or how ever many you aren't actively using
so for example-- the H drive houses all files from 2002- 02.xxx thru 07.400
I was in 07.176 and 05.208 I had access to those file trees, but the rest of the server was inaccessible.

you can try to resynchronize, it says it has re-established the connection but you aren't connected. the only way to reconnect is to restart.

we thought it was the upper 3com switch (and had it replaced) since the majority of the people getting dropped were on the upper switch...but I'm on the lower switch.


any ideas?
TIA-

Justin

 

I'll take a stab at it...

It doesn't sound like a network switch problem, since you can still access some resources on the server.

I assume you're running Windows Server? If so, there is an auto-disconnect feature for server connctions... this may be your problem.

The shares are disconnected after a period of inactivity. IF It is auto disconnect causing your issue, you can configure it on the server.

Take a peek at the linked Microsoft support article. If you choose to change the configuration, I'd use the command line option first (rather than changing the registry). Also look at the "More information" section at the bottom, as it points to the possibilty that your application may not work after the disconnect occurs.

http://support.microsoft.com/kb/297684

 

All that money for useless CAT6 cable and then you toss in 3com switches? Tsk tsk tsk...

Too little info to even begin troubleshooting. VyPeR maybe onto something, but its a shot in the dark.

 

Definitely was a shot in the dark (but nonetheless an educated shot for a windows based server)

Could certainly also be related to a misbehaving network protocol, though it's hard to tell.