Creating a home network with a COLLEGE Based Network system

[Guest]

Hi There:
I am living on a college campus that has network access in a living areas.
My wife and I are using a network hub, because they only give us one ethernet
connection. Is there anyway that we could see the two computers? I have had
alot of troubles trying to do this. I can see others in the college network,
but not my wife's. I also have a Tivo that I plan to hook up to the hub. Can
anyone help me? Thanks

 

[Chuck]

Hi There:
I am living on a college campus that has network access in a living areas.
My wife and I are using a network hub, because they only give us one ethernet
connection. Is there anyway that we could see the two computers? I have had
alot of troubles trying to do this. I can see others in the college network,
but not my wife's. I also have a Tivo that I plan to hook up to the hub. Can
anyone help me? Thanks

Phillip,

If you have only one Ethernet connection, are you limited to a single ip address
too? If so, you may need to replace the hub with a NAT router. You'll be safer
doing that, though your ability to see the other computers in the college
network may be hampered somewhat.

Please provide ipconfig information for your, and your wife's, computers, so we
can see what your problem is.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste entire contents into your next post. Identify
operating system (by name, version, and SP level) with each ipconfig listing.

 

[Guest]

Chuck,
My pc info it:
Windows IP Configuration



Host Name . . . . . . . . . . . . : phillip-a46zabo

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : village.olemiss.edu



Ethernet adapter Local Area Connection 3:



Connection-specific DNS Suffix . : village.olemiss.edu

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-D0-68-00-BB-B1

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 130.74.137.120

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 130.74.137.1

DHCP Server . . . . . . . . . . . : 130.74.128.4

DNS Servers . . . . . . . . . . . : 130.74.128.4

130.74.1.75

Lease Obtained. . . . . . . . . . : Monday, January 03, 2005 9:49:19
PM

Lease Expires . . . . . . . . . . : Thursday, January 06, 2005
9:49:19 PM

My Wifes is:
Host Name:..........Carlaspc122
Primary DNS Suffix.......................
Node Type: Unknown
IP Routing enabled: ......... No
WINS Proxy Enabled:..............No
DNS Suffix Search List:............ village.olemiss.edu

Ethernet Adapter Local Area Connection
Connection-Specific DNS Suffix:........... village.olemiss.edu
Description:...... Realtek RTL 8139/810 Family Fast Ethernet NIC
Physical Address:......00-40-CA-57-63-E8
Dhcp Enabled:.....yes
Auto configuration Enabled:..........yes
IP Address:........130.74.137.127
Subnet Mask:.........255.255.255.0
Default Gateway:......130.74.137.1
DCHP Server:......130.74.128.4
DNS Servers:........130.74.128.4
130.74.1.75
Lease Obtained: Monday, January 03,2005 9:34:03 P.M.
Lease Expires: Thursday, January, 06, 2005 9:34:03 P.M.

I hope this help you. Thank you so much.
Phillip

 

[Guest]

Oh yea,
we both run: Windows XP Home Edition, SP 2

 

[Chuck]

Chuck,
My pc info it:

I hope this help you. Thank you so much.
Phillip

Phillip,

OK, that's a start.

Both computers are receiving legal, technically correct configs
(130.74.137.0/24) from the campus DHCP server 130.74.128.4. Both computers are
Node Type = Unknown.
http://support.microsoft.com/?id=160177

No problem so far.

Now let's try and get a picture of what is happening.

Take the following code (everything inside the "#####"). (Did I get the names
and ip addresses right)?

Copy the code, precisely as it is keyed, into Notepad. Ensure that Format -
Word Wrap is not checked.
Save the file as "cdiag.cmd", as type "All Files", into the root folder "C:\".
Run it by Start - Run - "c:\cdiag".
Wait patiently.
When Notepad opens up displaying c:\cdiag.txt, first check Format and ensure
that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A Ctrl-C)
and paste (Ctrl-V) into your next post.

Do this from both computers, please.

#####

@echo off
set FullTargets=phillip-a46zabo 130.74.137.120 Carlaspc122 130.74.137.127
set PingTargets=127.0.0.1
Set Version=V1.05
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% (Targets %FullTargets%) >>c:\cdiag.txt
for %%a in (%FullTargets% %PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "net view %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

#####

 

[Guest]

Chuck,
I did exactly whtat you told me, and i checked the ip and names, and i get
this message:
System error 53 Has occured
The network path was not found.
Did I do something wrong?

Phillip

 

[Guest]

Chuck,
Disregard the previous post, here is the information you wanted:
My pc:
CDiagnosis V1.05
Start diagnosis for PHILLIP-A46ZABO (Targets phillip-a46zabo 130.74.137.120
Carlaspc122 130.74.137.127)

Target phillip-a46zabo

"ping phillip-a46zabo"



Pinging phillip-a46zabo [130.74.137.120] with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view phillip-a46zabo"

Shared resources at phillip-a46zabo

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 130.74.137.120

"ping 130.74.137.120"



Pinging 130.74.137.120 with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 130.74.137.120"

Shared resources at 130.74.137.120

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target Carlaspc122

"ping Carlaspc122"

Ping request could not find host Carlaspc122. Please check the name and try
again.


"net view Carlaspc122"


Target 130.74.137.127

"ping 130.74.137.127"



Pinging 130.74.137.127 with 32 bytes of data:



Request timed out.



Ping statistics for 130.74.137.127:

Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),

Control-C


"net view 130.74.137.127"


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 127.0.0.1"

End diagnosis for PHILLIP-A46ZABO

 

[Chuck]

Chuck,
I did exactly whtat you told me, and i checked the ip and names, and i get
this message:
System error 53 Has occured
The network path was not found.
Did I do something wrong?

Phillip

Phillip,

You might see that error, but did you get anything else too? The System 53 is
unavoidable, with the current (V1.05) CDiag. But it should produce a report
C:\CDiag.txt, which is what is needed, from both computers.

 

[Chuck]

Chuck,
Disregard the previous post, here is the information you wanted:

<SNIP>

Phillip,

So far, it looks like Carlaspc122 is simply not online. Let's see what the
CDiag log from Carlaspc122 shows.

 

[Guest]

Chuck,
Here is my wife's pc information:
CDiagnosis V1.05
Start diagnosis for CARLASPC122 (Targets phillip-a46zabo 130.74.137.120
Carlaspc122 130.74.137.127)

Target phillip-a46zabo

"ping phillip-a46zabo"



Pinging phillip-a46zabo [130.74.137.120] with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time=12ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 12ms, Average = 3ms


"net view phillip-a46zabo"

Shared resources at phillip-a46zabo

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 130.74.137.120

"ping 130.74.137.120"



Pinging 130.74.137.120 with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 130.74.137.120"

Shared resources at 130.74.137.120

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target Carlaspc122

"ping Carlaspc122"



Pinging Carlaspc122 [130.74.137.127] with 32 bytes of data:



Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.127:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view Carlaspc122"

Shared resources at Carlaspc122

second pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 130.74.137.127

"ping 130.74.137.127"



Pinging 130.74.137.127 with 32 bytes of data:



Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.127:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 130.74.137.127"

Shared resources at 130.74.137.127

second pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 127.0.0.1"

End diagnosis for CARLASPC122

Chuck,
Disregard the previous post, here is the information you wanted:
My pc:
CDiagnosis V1.05
Start diagnosis for PHILLIP-A46ZABO (Targets phillip-a46zabo 130.74.137.120
Carlaspc122 130.74.137.127)

Target phillip-a46zabo

"ping phillip-a46zabo"



Pinging phillip-a46zabo [130.74.137.120] with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view phillip-a46zabo"

Shared resources at phillip-a46zabo

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 130.74.137.120

"ping 130.74.137.120"



Pinging 130.74.137.120 with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 130.74.137.120"

Shared resources at 130.74.137.120

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target Carlaspc122

"ping Carlaspc122"

Ping request could not find host Carlaspc122. Please check the name and try
again.


"net view Carlaspc122"


Target 130.74.137.127

"ping 130.74.137.127"



Pinging 130.74.137.127 with 32 bytes of data:



Request timed out.



Ping statistics for 130.74.137.127:

Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),

Control-C


"net view 130.74.137.127"


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 127.0.0.1"

End diagnosis for PHILLIP-A46ZABO

Oh yea,
we both run: Windows XP Home Edition, SP 2

 

[Chuck]

Chuck,
Here is my wife's pc information:

<SNIP>

Phillip,

OK, neither computer has any problem with itself. And Carlaspc122 has no
problem accessing phillip-a46zabo. But phillip-a46zabo can't see, or access
Carlaspc122 in any way.

Asymmetrical access problems like this are almost always caused by a misbehaving
or misconfigured firewall, in this case, on Carlaspc122. A very minor
possibility is the hardware, so swap cable and hub port between the two and
retest. Then look at the firewall setup on Carlaspc122.

 

[Guest]

Chuck,
Here is the retest information for my wifes pc:
CDiagnosis V1.05
Start diagnosis for CARLASPC122 (Targets phillip-a46zabo 130.74.137.120
Carlaspc122 130.74.137.127)

Target phillip-a46zabo

"ping phillip-a46zabo"



Pinging phillip-a46zabo [130.74.137.120] with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view phillip-a46zabo"

Shared resources at phillip-a46zabo

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 130.74.137.120

"ping 130.74.137.120"



Pinging 130.74.137.120 with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 130.74.137.120"

Shared resources at 130.74.137.120

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target Carlaspc122

"ping Carlaspc122"



Pinging Carlaspc122 [130.74.137.127] with 32 bytes of data:



Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.127:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view Carlaspc122"

Shared resources at Carlaspc122

second pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 130.74.137.127

"ping 130.74.137.127"



Pinging 130.74.137.127 with 32 bytes of data:



Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.127:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 130.74.137.127"

Shared resources at 130.74.137.127

second pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 127.0.0.1"

End diagnosis for CARLASPC122

 

[Guest]

Chuck,
Here is the retest information for my pc:
CDiagnosis V1.05
Start diagnosis for PHILLIP-A46ZABO (Targets phillip-a46zabo 130.74.137.120
Carlaspc122 130.74.137.127)

Target phillip-a46zabo

"ping phillip-a46zabo"



Pinging phillip-a46zabo [130.74.137.120] with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view phillip-a46zabo"

Shared resources at phillip-a46zabo

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 130.74.137.120

"ping 130.74.137.120"



Pinging 130.74.137.120 with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 130.74.137.120"

Shared resources at 130.74.137.120

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target Carlaspc122

"ping Carlaspc122"



Pinging Carlaspc122 [130.74.137.127] with 32 bytes of data:



Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.127:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view Carlaspc122"

Shared resources at Carlaspc122

second pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 130.74.137.127

"ping 130.74.137.127"



Pinging 130.74.137.127 with 32 bytes of data:



Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.127:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 130.74.137.127"

Shared resources at 130.74.137.127

second pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 127.0.0.1"

End diagnosis for PHILLIP-A46ZABO

Chuck,
Here is the retest information for my wifes pc:
CDiagnosis V1.05
Start diagnosis for CARLASPC122 (Targets phillip-a46zabo 130.74.137.120
Carlaspc122 130.74.137.127)

Target phillip-a46zabo

"ping phillip-a46zabo"



Pinging phillip-a46zabo [130.74.137.120] with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view phillip-a46zabo"

Shared resources at phillip-a46zabo

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 130.74.137.120

"ping 130.74.137.120"



Pinging 130.74.137.120 with 32 bytes of data:



Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128

Reply from 130.74.137.120: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 130.74.137.120"

Shared resources at 130.74.137.120

Main pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target Carlaspc122

"ping Carlaspc122"



Pinging Carlaspc122 [130.74.137.127] with 32 bytes of data:



Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128

Reply from 130.74.137.127: bytes=32 time<1ms TTL=128



Ping statistics for 130.74.137.127:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view Carlaspc122"

Shared resources at Carlaspc122

second pc

Share name Type Used as Comment

-------------------------------------------------------------------------------
SharedDocs Disk
The command completed successfully.


Target 130.74.137.127

"ping 130.74.137.127"



Pinging 130.74.137.127 with 32 bytes of data:

 

[Chuck]

Chuck,
Here is the retest information for my pc:

Phillip,

What change did you make? CDiag logs now show no problem.

Are we maybe looking at a browser problem (I'm not talking about Internet
Explorer here) from another angle? The Microsoft Browstat program will show us
what browsers are on your LAN.
http://support.microsoft.com/?id=188305

You can download Browstat from either:
<http://www.dynawell.com/reskit/microsoft/win2000/browstat.zip>
<http://rescomp.stanford.edu/staff/manual/rcc/tools/browstat.zip>

Browstat is very small (40K), and needs no install. Just unzip the downloaded
file, copy browstat.exe to any folder in the Path, and run it from a command
window, by "browstat status". Make sure all computers give the same result.

For more information about the browser subsystem (very intricate), see:
http://support.microsoft.com/?id=188001
http://support.microsoft.com/?id=188305
<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>