Well, I'd try this first on both machines, then post the IPCONFIG /ALL results from both machines again.
BTW, if you follow my instructions for capturing the IPCONFIG results, you don't have to post graphics, you can simply paste the text of the IPCONFIG results here.
TCP/IP stack repair options for use with Windows XP with SP2.
Start,
Run,
CMD to open a command prompt:
Reset TCP/IP stack to installation defaults.
netsh int ip reset reset.log
Reset WINSOCK entries to installation defaults:
netsh winsock reset catalog
Reboot the machine.
Turn off any firewalls for debugging. If the firewall is the problem, you'll have to configure it to allow access to "trusted zone" addresses. Note that some firewalls must be completely uninstalled to stop them from affecting your networking.
Hold the
Windows key and press
R, then type
CMD to open a command prompt for the following commands:
PING each remote computer by IP address, and if successful, PING by name. Open a command prompt as described above and type.
PING <ip address>
or
PING <computer name>
Where:
<ip address> - is the x.x.x.x IP address
<computer name> - is the computer name
A failure to PING is almost always a firewall configuration issue. Any failure to PING needs to be corrected before you go any farther.
Note: You can obtain the IP address and computer name of a computer by opening a command prompt (DOS window) and typing IPCONFIG /ALL. This should work for any Windows version. The IPCONFIG /ALL display will provide a wealth of useful information for debugging your network connection.
Check your Services are Started on all PCs:
- Computer Browser
- DHCP Client
- DNS Client
- Network Connections
- Network Location Awareness
- Remote Procedure Call (RPC)
- Server
- TCP/IP Netbios helper
- Workstation
Note: You can check the services in Control Panel, Administrative Tools, Services.
All of these services should be started, and their startup type should be automatic (perhaps one or two manual, but that should be started).