Steve Winograd said:
[snip]
Thank you all for jumping in with some solutions. I tried Chuck's wizard
approach first. I thought it might have been the choice I made back when the
whole netowrk actually worked. This time, it didn't. "My Network Places" was
empty, neither computer could see or ping the other. I am trying to make sure
that I have a good physical connection before trying another setup. I also
reset TCP/IP and ran a fix for winsock corruption. My ongoing concern is
that I've had to try so many fixes (including a Windows reinstall) that I
need to clean up after each attempt as much as I can. I'll report back on
trying to set it up manually and testing for NIC and cable problems.
You're welcome. Browsing through My Network Places is unreliable, as
you can see from the large number of messages about it in this news
group. Try accessing the other computer directly, without browsing,
by typing its name in the Start | Run box in this format:
\\computer
If that doesn't work, here are some tests to help find the problem.
on each computer, open a command prompt window and enter these
commands. Each one should get four replies:
ping <this computer's IP address>
ping <other computer's IP address>
ping <this computer's name>
ping <other computer's name>
For example:
ping 192.168.0.1
ping 192.168.0.2
ping desktop
ping laptop
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
LATEST RESULTS:
Follwoing the instructions in Microsoft's 8-part series on setting up a
network, I did the following:
1. Installed Client for MS Networks, QOS Packet Sheduling, File & Print
Sharing and configured TCP/IP for fixed IP address of 192.168.0.1 and
192.168.0.2 for FRED and WILMA respectively.
2. I turned off the firewall on the local network connections.
3. I enabled NetBIOS over TCP/IP
4. I configured one folder on each computer to be shared but not the root
drive of either computer.
Now I could se My Netowrk Places, but each comp can only see the folder it
is ahring not the shared folder on the other comp. In Workgroup Computers,
FRED has icons for both; WILMA has icons for only WILMA. Clicking on the
WILMA icon on FRED yields a error message that access isn't possible and "The
Network path was not found."
Neither comp can ping the other by name or address.
The details I gathered are:
Status for domain STUDYNET on transport
\Device\NetBT_Tcpip_{05C875A5-F2E0-4B56-933B-2503982D3011}
Browsing is active on domain.
Master browser name is: FRED
Master browser is running build 2600
1 backup servers retrieved from master FRED
\\FRED
There are 2 servers in domain STUDYNET on transport
\Device\NetBT_Tcpip_{05C875A5-F2E0-4B56-933B-2503982D3011}
There are 1 domains in domain STUDYNET on transport
\Device\NetBT_Tcpip_{05C875A5-F2E0-4B56-933B-2503982D3011}
Windows IP Configuration
Host Name . . . . . . . . . . . . : FRED
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Studynet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-EE-4A-E6
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ping: Ping request could not find host wilma. Please check the name and try
again.
Status for domain STUDYNET on transport
\Device\NetBT_Tcpip_{62A406F1-67DE-4422-AC60-A7157B099486}
Browsing is active on domain.
Master browser name is: WILMA
Master browser is running build 2600
1 backup servers retrieved from master WILMA
\\WILMA
There are 1 servers in domain STUDYNET on transport
\Device\NetBT_Tcpip_{62A406F1-67DE-4422-AC60-A7157B099486}
There are 1 domains in domain STUDYNET on transport
\Device\NetBT_Tcpip_{62A406F1-67DE-4422-AC60-A7157B099486}
Windows IP Configuration
Host Name . . . . . . . . . . . . : Wilma
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Studynet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-EF-6D-04
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ping: Ping request could not find host fred. Please check the name and try
again.
I'm assuming that the fact that WILMA sees other computers in browstat means
that I do have a physical connection. I don't understand what DHCP is not
enabled when I checked the box to do that. I also see that this mnring
(different from last night) both comps are trying to be master browsers.
Last night it was only WILMA and browsing was not active on FRED.
Trying to connect using the RUN command didn't work. Also, I did not try to
use any tool to repair the winsock on WILMA. Please let me know if that's
recommended.
Thanks again for your suggestions.