renaming restores connectivity
Posted 02 May 2005 - 05:42 AM
Posted 02 May 2005 - 01:14 PM
Posted 02 May 2005 - 04:58 PM
I am new to networking. I want to make sure I do this right. I run ipconfig with no switches, right? Then look for the IP Address of the computer and the Default Gateway to see if there is communication between the computers and the router?
Posted 02 May 2005 - 05:57 PM
Click "Start", "Run" and type \\computername\C$
C$ is an Administrative share that you should be able to access on each computer from each computer as long as you enter the username Administrator and the Administrator's password for each machine. It also works if you have the same account on each machine with Administrator priveledges. That is how I test my network connectivity most of the time.
Posted 02 May 2005 - 10:33 PM
Connection-specific DNS Suffix . : domain_not-set.invalid
IP Address ..................... : 192.168.1.101 (.102, .103, etc)
Subnet Mask .................... : 255.255.255.0
Default Gateway ................ : 192.168.1.1
Secondly, \\computername\C$ produced very strange results:
sometimes it would bring up a given "computername's" files/folders, sometimes not, with one error message or the other, even when all computers were communicating.
Thirdly, I sought to reproduce the difficulty by installing uninstalling the freeware firewall. The same conditions were produced when I loaded Win 2k on one computer. I thought it easier to produce the problem with the firewall install-uninstall rather than reload a whole operating system--which I can do but I figured easiest things first. I reproduced the difficulty to some extent !!! only, some computers are still networked together, others refuse to cooperate. Anyway, it looks like the same basic trouble was introduced into the system by installing and uninstalling the firewall.
The wierd thing is that though the connectivity between computers changed, the above tests came out no different. I believe that means that all computers are still talking to the router despite having lost some connectivity with each other. The wierd behavior of the C$ command from the beginning makes no sense to me.
Any thoughts will be much appreciated.
Posted 02 May 2005 - 11:15 PM
Posted 03 May 2005 - 10:16 AM
Another wierdness: computernameA may recognize and share with computernameB but computernameB may not recognize and share with computernameA. Still another wierdness. The problem will start out with one computer acting up between another computer on the network and then this behavior will spread to its becoming inaccesible to other computers and then other computers slowly becoming inaccessible to still others. This led me to think there was a virus involved. But I have three different brands of virus protection installed on respective computers, Norton, PCCillin, Antivir Freeware. All are uptodate and none detect a virus. And as I mentioned the problematic behavior starts only under certain conditions.
The Win Xp computer is the only one I have firewalled. Normally I only have the other computers share files with it--as my backup system. Normally I never read or write files from or to the other computers so I didn't firewall them. For this testing I have enabled fire sharing on all computers and I tried the system with the Win Xp firewall active and not active ... no difference. I thought maybe there was something wrong with the Win 2k that caused the problem, so I reloaded another Win 2k. That did not cause the problem but the install and uninstall of the freeware firewall did even with that Win 2k load, once again. I include these details if they are of any use.
I naturally could avoid the concrete problem by avoiding the conditions that start it, but I'd still like to know what is going on, and the problem could creep up later under different circumstances; so I appreciate your help in figuring this out.
Thanks again for your time.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users