Trying to connect to server

sammy26ntn

New Member
Reaction score
0
Location
Nashville TN
There are 3 computers (a) (b) and (c) that were hooked to a network and all are running windows xp service pack 3 group (b) computer is the source computer. My client said they came in one morning and the computer (a) was not accessing the source computer. I tried to remap the the drive and it still cant conect to the source. But when I am on the source pc (b) i can see computer (a). can anyone point me in the right direction?
 
I'll assume you already Powered off A and unplugged the network cable, then re-inserted cable and started up.

Are you able to \\ to the location you have mapped to from computer a? computer C is working as intended then? Can they all ping each other? Did they login to a on a different username than normal? No permissions/share settings were changed on that drive?
 
What changed?

Go to each computer...network properties...TCP/IP properties...Advanced button, WINS tab..and enable netbios over TCP/IP.
Power all computers down..and the router.
Power up router. Since this is a peer to peer network...no real server running Active Directory thus DNS, you're going by broadcast name resolution and the 3x workstations are probably having master browser debates. But the router is probably running DNS for the LAN. Or it could simple DNS relay to it's WAN..depends, but worth a shot.
Power up computer B (the stand in server)..allow to fully bootup and log in and sit for a few minutes.
Power up computers A and C.

Now...from the workstations...ping the server by host name, do you get replies?
I'm sure you'll get replies if you ping the IP address...but do it to be sure.

May want to set the "server" with a static LAN IP address...like 192.168.1.11/24 and use the routers LAN IP as its DNS (and gateway of course)
 
I forgot to mention this is a SONY VAIO VGC-RA940G desktop. it also has the following error message when I tried to connect

error occurred while reconnecting z:\\ jeff\data
microsoft windows network: the network path was not found the connection has not been restored
----------------------------------------------------
 
I second Stonecat's suggestion at setting a static IP. With just computers, I'd set static IP's for all 3. (Unless they're laptops, of course.)

Might also want to check stored credentials on the 2 client machines.
 
I am definitely NOT an end user but I can see why you think so. I have been fixing computers over a year, just finally got started working for myself and I am not familiar with networking... plus i just found this website and joined up. I dont feel I have to explain myself to you but I also have nothing to hide.... Thanks to all I go back to my client tomorrow and see if I can slay the dragon.... :cool:
 
Windows XP can be a pain in the balls sometimes about network shares. Check and make sure nobody blocked the computer in question via Windows XP firewall or 3rd party firewall/Internet security.

From the sounds of it, they might benefit from a dedicated server. Windows or Linux with SAMBA. Even if it is just a NAS or something. Maybe sit with them and create a plan to get them a new server or NAS and some updated clients over a period of time.

Consumer grade Desktops with Windows XP....probably pretty slow and hinder their productivity anyway.
 
ok I logged in tried pinging each computer ping (A) to (A) did NOT work. ping (A) to (B) the source pc it worked and so did (A) to (C)... When I ping (B) to (B) it worked So on and so forth but when I ping (B) to (A) or (C) to (A) it does not work!! who knew that networking could be such a pain!! I am going to look through the rest of the posts and try each one of those... If I make another workgroup do you think it might work? And if so do you have any recommendations. Like I said networking is not my thing but I will have to learn it... THANKS:mad:
 
issue solved!!!!!!! you will never guess what it was.. should have been the first thing I did. Norton Security antivirus has an automatic scan that was the issue... Once I disabled it I tried to connect back to the host PC and BOOM we were up and running!!! Thank you all for your input in this matter. I will be looking forward to to this forum !:o
 
Ahh yeah....home grade full antivirus/firewall suite is a common cause of that in networks. I should have known better and mentioned that after reading "sony pc" for a server.
 
Err.... sammy, no wish to seem rude but,

I dont know much about networking just trying my hand at it

I seriously suggest you get learning and hands on etc.

I have been fixing computers over a year, just finally got started working for myself and I am not familiar with networking

How on earth you've managed so far, without running into networks, I am not entirely sure, but again, see my above comment.

Read some info on peer to peer networking.

Err.... and client/server


I have come across a number of networking issues myself, where it turned out to be caused by Norton Security software.

Like I said networking is not my thing but I will have to learn it.

You certainly will, otherwise at some point you're going to start having problems, unless you just get someone else in all the time to deal with networking issues, of course.

Not being rude, just trying to be helpful :)
 
Back
Top