Network Problem
#1
Scooby Regular
Thread Starter
Join Date: Nov 2000
Location: Glasgow
Posts: 1,432
Likes: 0
Received 0 Likes
on
0 Posts
This one has me stumped. I have a SBS network at work. One of the pc’s connected to the network seems to be acting a bit odd. It seems fine with applications such as Word and Excel but if you are plugged into the network and try to access folders on the PC’s C drive it takes ages. I have assigned the pc a different ip address, changed network cables and checked the NIC.
If it’s unplugged from the network it seems to work fine. All the other PC's seem to work fine (Win 2000) but the PC I am having problems with is running XP.
Any ideas
The user has not installed any software and I have done a virus scan. I have also deleted print drivers.
Cheers
If it’s unplugged from the network it seems to work fine. All the other PC's seem to work fine (Win 2000) but the PC I am having problems with is running XP.
Any ideas
The user has not installed any software and I have done a virus scan. I have also deleted print drivers.
Cheers
#2
Scooby Regular
iTrader: (3)
Join Date: Dec 1999
Location: UK
Posts: 13,274
Likes: 0
Received 0 Likes
on
0 Posts
Running through this logically:
And things you've already tried:
Software on the PC
NIC (although check the settings - Is duplex on?)
Cable to wall point (Do you have a cable tester?
Try:
Another PC at the same point, to determine whether its a PC fault or the cabling/patch panel/hub.
And the PC at a differnt point, to ensure it's not the network infrastructure.
If it's not the PC, try:
A different port on the hub, ideally a known working one!
Use different flyleads both ends.
Let us know how you get on!
And things you've already tried:
Software on the PC
NIC (although check the settings - Is duplex on?)
Cable to wall point (Do you have a cable tester?
Try:
Another PC at the same point, to determine whether its a PC fault or the cabling/patch panel/hub.
And the PC at a differnt point, to ensure it's not the network infrastructure.
If it's not the PC, try:
A different port on the hub, ideally a known working one!
Use different flyleads both ends.
Let us know how you get on!
#5
I assume this PC is a 98 machine?
If so try it connected without autheticating it to the domain... i.e hit cancel at the logon..
If that is ok I would look towards a file sharing issue - try turning it off or a network card issue - It wouldn't happen to be sharing the same irq as the hdd controller?
If so try it connected without autheticating it to the domain... i.e hit cancel at the logon..
If that is ok I would look towards a file sharing issue - try turning it off or a network card issue - It wouldn't happen to be sharing the same irq as the hdd controller?
#6
Scooby Regular
Thread Starter
Join Date: Nov 2000
Location: Glasgow
Posts: 1,432
Likes: 0
Received 0 Likes
on
0 Posts
What I thought I would do was disjoin the PC from the domain, rename and run the Client setup disk. The PC now can't find the domain on the server. I can run a \\10.0.0.* command and see the files on the server from the PC but it won't find the domain.
Willie it's running XP
Willie it's running XP
Trending Topics
#9
Scooby Regular
Thread Starter
Join Date: Nov 2000
Location: Glasgow
Posts: 1,432
Likes: 0
Received 0 Likes
on
0 Posts
Cheers Si
That seems to make it a bit faster, but it's still not right. It takes about three minutes to log on to the domain once on it's usable but still quite slow (the egg timer seems to run on applications for a while). I’m just about to install service pack etc to see if that helps.
It seems you should not use the 2000sbs disk to join a domain with XP.
Cheers
Jer
That seems to make it a bit faster, but it's still not right. It takes about three minutes to log on to the domain once on it's usable but still quite slow (the egg timer seems to run on applications for a while). I’m just about to install service pack etc to see if that helps.
It seems you should not use the 2000sbs disk to join a domain with XP.
Cheers
Jer
#10
This is a very simple problem and i think everyone has gone a little to deep in to it. I get this at work all the time, what is happening is when the machine is on the network, but has not correctly mapped the various drives, what happens is when word/excel etc.. try to open/save stuff it trys to look for the drives which would be there and it takes a while for it to realise they are unavailable, so that is why when it is not on the network it does not try these none working drives. Look at the mappings in "Explorer" and check the machine is mapping and can write to them correctly.
Thread
Thread Starter
Forum
Replies
Last Post