Win7 office network issue

Countcussy

Countcussy

Countcussy

Associate
Joined
10 Nov 2006
Posts
1,356
We have 6 DELL Win7 machines, all of which are pretty similar, of which mine is the "primary" machine.
We run sage accounts and my machine holds all the data files. All the machines are connected to a Netgear ProSafe switch.

We are having an issue where one of the machines (lets call it Chloe) will randomly drop its network connection to my machine only. This means her Sage software crashes. During this disconnection, Chloe can see and access all the other machines on the network, and I can access Chloe no problem. But if Chloe tries to connect to my machine, we get the normal error message from windows saying the network path cannot be found and error 0x80070035

The most bizzare thing is that after a random period of time, the problem will fix itself and everything returns to normal, with no user input.
A reboot speeds this process up.

None of the other users in the office experience this issue.
All machines are running the same AV software. (Avira Proffesional)

I have googled 0X80070035 but none of the suggestions helps or applies to this situation.
Any help would be greatly appreciated. :)
 
what you describe there to me sounds like a Collision on the network where the connection is told to back off for a random amount of time and then try again.
check duplex setting on your machine and chloe's
 
Last edited:
Thank you for the reply.

The only duplex settings I can find on each card are set to Auto Negotiation.
They are both Realtek GB adaptors.
The switch lights indicate both connections are 1gb.

FWIW, I am no IT wiz, I know just enough to get by.:)
 
next thing i would do is connect Chloe to a different network port or swap hers with some one else and see if the problem follows the port or the user
 
Well, that did not take long.

Swapped her cable at the switch with another user. Chloe still getting the error. Seemingly more so today, which is strange as we have 2 machines unused.

The user using Chloe's old port has no issues.

Just as a bit more info. These issues appear to have started since we moved premises and added more machines to the office. Its been on and off for a few months. The only other thing that has changed, is that we now have 40meg Fibre and a BT hub 5.
 
Last edited:
Could it be you are running into the 20 Inbound Connection limit of Windows 7 (i.e. the one where you would buy a Server OS) - (bearing in mind connections can be left open, e.g. if users switch users but stay logged in etc.)
 
I presume not.

There are 4 of us working today, and each user has his/her machine. No one uses anyone else's desk.
I did look into changing some registry settings related to getting Win 7 to act as a server. I am reluctant to do this as only one user is affected. Other than this issue, our small office set up works really well.

Really appreciate the help so far.
 
Countcussy said:
I presume not.

There are 4 of us working today, and each user has his/her machine. No one uses anyone else's desk.
Click to expand...

Each user could be using more than 1 connection though, e.g. a shared printer would count as a connection as well.

Top of my head I can't remember how to retrieve the current number of connections though
 
maybe then check to see if a printer or another machine / device has the same ip address ? has chloe got a static ip? try changing it?
 
other things come to mind as well , are you all using the same dns setting
if you open command prompt and do nslookup (chloespcs name) 1 does it resolve and do you have the same server , do this from and to her machine with yours
 
No static IPs. All dynamic.

nslookup works from both sides at the moment. Chloe's connection is behaving. Default server is the same (BT business hub)
Address is also the same.

Perhaps I need to try that when her connection fails?
 
the other thing, is check the event log on both machines when the issue happenes
that is with out a doubt the best thing to do first :)
 
You must log in or register to reply here.
Back
Top Bottom