I run Windows 2000 professional on a small network. My computer is
the server and the other PCs can all see and use files on my computer.
However, a week ago something happened. Now everytime I try to do
anything to do with networking, my PC freezes. I can't map network
drives. I can't see other computers on the network, although I can
still ping them.
Right clicking "My Computer", and pressing "Properties" and then
"Networking Identification", and then "Properties", it tells me on the
"identification changes screen" that I can change the name of the
computer, but I must install networking before I can change my
computer's domain membership.
How do I install networking????
I would rather not have to reinstall Windows - my version in now SP3,
but the original version on CD is SP2 so I can't reinstall it easily
or use it to fix problems.
I tried to fix the problem by buying a new network card, but the
problem still remains.
I also tried to fix the problem by disabling the broadband connection,
but the problem still remains. |
Clarification of Question by
dickyp-ga
on
08 Dec 2002 11:47 PST
I have reinstalled SP3.
I have also uninstalled, rebooted, and reinstalled the network
components as you suggested.
Unfortunately neither worked.
For clarification, you are right, I run Windows 2000 Pro, not Server.
I just call my computer the server because other computers access
files off it.
My computer freezes when, for instance, I click "Computers near me" or
when I try to map a network drive, or if I try to look at other
computers on the LAN. Other computers can still look at my computer,
access the files etc and there is no detrimental effect on either
computer. My computer can still ping other computers in the command
prompt.
|
Hello dickyp.
First off, I have to warn you that this "answer" won't likely contain
the answer to your problem. Troubleshooting is a back-and-forth
process, and I consider this answer merely the first step and a
signing-up, if you will, for the rest of the problem.
With that out of the way, I have a few suggestions, and some
questions. Please let me know, as accurately as you can, what happens
when you try the suggestions. Thanks!
Have you changed the cabling, hubs or switches, etc. since the network
was working? Have you installed any new software or hardware into the
server PC?
You mentioned that pinging the other computers works, and doesn't lock
up. Have you tried higher-level protocols? Can you use HTTP, FTP,
SSH, etc. to connect?
When you unplug your server from the network, can you access "my
network places" and see your own computer?
When you click properties on your network connection, what protocols
do you see checked? How are they configured?
Is your computer battery-backed? Have their been any electrical
outages, surges, etc. since the network worked?
With that information, I can advise you on the next set of questions
to ask as we narrow down what the cause of your troubles is.
-Haversian |
Request for Answer Clarification by
dickyp-ga
on
10 Dec 2002 01:39 PST
I have changed the cables, but that has not solved the problem so I
have changed them back. I have not changed the hubs or switches, but
I have changed the socket in which my computer plugs into the switch,
but that does not work. the switch is working fine because other
computers on the LAN can see each other.
I have changed the network card for the LAN on my computer, but this
did not work. I have not installed any new software.
When i unplug the network cable, I cannot see my own computer on my
network places. It freezes up if I try.
Electrical surges or outages. Possibly, but I can't say definately.
Not battery backed.
The network protocols are Client for Microsoft Networks, File and
Printer Sharing for Microsoft Networks and Internet Protocol TCP/IP.
As per the comment below, I uninstalled and reinstalled these
protocols. Unfortunately none of the computers on my network can see
or access files on my computer now, which they could do before - the
other computers say they can't find the workgroup.
I have broadband connected so I have two network cards in my computer.
This means that the broadband connection obtains its IP address
automatically, but I have to give a fixed IP address 192.168.0.1 to
the LAN.
I can still ping other computers. I wouldn't know how to use other
protocols, HTTP, FTP, SSH etc
|
Clarification of Answer by
haversian-ga
on
10 Dec 2002 12:03 PST
> I have changed the socket in which my computer plugs into the switch
Have all the computers been rebooted (not necessarily at the same
time) since then?
>I have changed the network card for the LAN on my computer, but this
did not work.
Please cut and paste the output of "ipconfig /all" typed into a DOS
window (Start | Run | type "command" into the box).
> the other computers say they can't find the workgroup.
All the workgroups have to match. Under Windows 2000, right-click on
My Computer and choose Properties. Under the Network Identification
tab, you will see a computer name and a workgroup. Make sure the
workgroup is set properly, and that all the other computers are using
the same workgroup.
> This means that the broadband connection obtains its IP address
automatically, but I have to give a fixed IP address 192.168.0.1 to
the LAN.
That's reasonable. The other computers on your LAN have IP addresses
of 192.168.0.something, right?
> I can still ping other computers.
Are you pinging by name, or by IP number?
With two network cards, you could be having some confusion as to where
Windows should broadcast info about where your files are and such. I
will have to investigate that.
Meanwhile, go to the device manager (properties of My Computer, select
the hardware tab, hit device manager) and uninstall your network
cards. Also unplug their cables. This should remove the protocols
associated with them as well, so take screenshots of the settings, or
write them down (IP numbers, netmasks, DNS servers, windows networking
options, etc.) first. Try my network places again.
If your computer does not lock up (I would expect an error message),
go back to the device manager, select the computer name, and hit
Action | Scan for hardware changes. This should get your network
cards back. Configure only the one for your LAN. Install the TCP/IP
protocol, and the file sharing protocol. Share your C drive or
something for testing purposes. Head back to my network places to see
what you get.
If this works, configure your other network card, the one for
broadband. Plug in the cable to your broadband box, and make sure
accessing the internet works. Try my network places again. Plug the
cable back in for the LAN and try it again. Then try accessing your
computer from the other machines on the network.
Let me know where in that chain of suggestions you start running into
trouble.
-Haversian
|
Request for Answer Clarification by
dickyp-ga
on
11 Dec 2002 06:05 PST
I have taken the decision to reinstall Windows 2000 completely again,
and it works perfectly.
However you mention that with two network cards, I could be having
some confusion as to where Windows should broadcast info about where
myfiles are. I would still be very interested if you had any
information on that.
Many thanks for all your help. Although you did not solve it, you
helped me come to the eventual decision I made.
|
Clarification of Answer by
haversian-ga
on
11 Dec 2002 09:26 PST
> I have taken the decision to reinstall Windows 2000 completely
again,
and it works perfectly.
I'm glad everything's working for you. You must have been desperate!
> However you mention that with two network cards, I could be having
some confusion as to where Windows should broadcast info about where
myfiles are. I would still be very interested if you had any
information on that.
I'm only familiar with routing under linux, but I presume the same
applies to Windows. You have two network cards, attached to two
networks. Until and unless Windows knows what IP numbers are on what
networks, how is it to decide where to go looking for a given IP
number? It is possible that Windows knows, for example, that
192.168.0.x is a Class C reserved network and will route all requests
for those IPs through the NIC that is bound to an address within that
range. If your other network card has a real IP address, you might
want to check to see if your machine is visible to the internet and
accepting SMB (server message block - Windows' filesharing mechanism)
connections. If your shares are password-protected and have good
passwords, you should be alright. Just be sure you aren't running all
sorts of services (FTP server, webserver, etc.) that Windows tends to
want to run for you, even if you don't need them and they just pose
massive security risks.
> Many thanks for all your help. Although you did not solve it, you
helped me come to the eventual decision I made.
I'm glad things are working for you. You didn't lose too much during
the reinstall, I hope.
|
