Re: Network not accessible on one machine
- From: Steven <Steven@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 26 Jan 2006 11:03:02 -0800
"Chuck" wrote:
> On Thu, 26 Jan 2006 08:04:01 -0000, "Steven Lyall" <steven.lyall@xxxxxxxxxxxxx>
> wrote:
>
> >
> >"Chuck" <none@xxxxxxxxxxx> wrote in message
> >news:o7hft1hgbr9d9pb6id455iottc1bfmuvr6@xxxxxxxxxx
> >> On Wed, 25 Jan 2006 13:22:49 -0000, "Steven Lyall"
> >> <steven.lyall@xxxxxxxxxxxxx>
> >> wrote:
> >>
> >>>"Chuck" <none@xxxxxxxxxxx> wrote in message
> >>>news:j49at11c0b5v5qks7p2cbo19orpb5l9l7r@xxxxxxxxxx
> >>>> On Mon, 23 Jan 2006 17:23:36 -0000, "Steven Lyall"
> >>>> <steven.lyall@xxxxxxxxxxxxx>
> >>>> wrote:
> >>>>
> >>>>>I have networked 2 WinXP Pro machines together via a D-Link router and
> >>>>>have
> >>>>>run the Network Setup Wizard on both.
> >>>>>
> >>>>>On one machine, when I 'view workgroup computers', I can see both
> >>>>>machines,
> >>>>>but when I double-click the icon for the other machine, I get a 'not
> >>>>>accessible' message.
> >>>>>
> >>>>>When I go to the other machine and try 'view workgroup computers', there
> >>>>>is
> >>>>>a delay and then it names the workgroup but tells me that I cannot
> >>>>>access
> >>>>>it.
> >>>>>
> >>>>>If anyone can advise, I'd appreciate it.
> >>>>>
> >>>>>Thanks,
> >>>>>
> >>>>>Steven
> >>>>
> >>>> Steven,
> >>>>
> >>>> What's the complete and exact text of the error messages?
> >>>> <http://nitecruzr.blogspot.com/2006/01/look-at-complete-detail-in-error.html>
> >>>> http://nitecruzr.blogspot.com/2006/01/look-at-complete-detail-in-error.html
> >>>>
> >>>> One of the most common causes of this problem would be a misconfigured
> >>>> or
> >>>> overlooked personal firewall, but there are other possibilities too.
> >>>> What
> >>>> antivirus products are you using?
> >>>> <http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
> >>>> http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html
> >>>>
> >>>> If no help yet, provide "browstat status" and "ipconfig /all" from each
> >>>> computer, so we can diagnose the problem. Read this article, and linked
> >>>> articles, and follow instructions precisely:
> >>>> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
> >>>> http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
> >>>>
> >>>> Please let us know if any of these suggestions are of any help. What
> >>>> you
> >>>> learn
> >>>> may help others in the future, and that's the purpose of these forums.
> >>
> >>>Many thanks.
> >>>
> >>>Here are all the additional details:
> >>>
> >>>Windows Firewall off on both machines.
> >>>Norton Antvirus prevented from loading on Machine 1, not present on
> >>>Machine
> >>>2
> >>>In 'View Network Computers', both machines can see the icon of the other.
> >>>Machine 1 can read from and write to Machine 2 perfectly.
> >>>On double-clicking the icon for Machine 1 from Machine 2, teh exact error
> >>>message is:
> >>>
> >>>'\\Machine 1 is not accessible. You might not have permission to use this
> >>>network resource. Contact eth administrator of teh server to find out if
> >>>you have access permissions. Access is denied.'
> >>>
> >>>Machine 2 CAN read from and write to a 3rd machine connected wirelessly to
> >>>teh network via teh same wireless router to which Machine 1 & Machine 2
> >>>are
> >>>connected by cable.
> >>>
> >>>All machines see teh internet perfectly.
> >>>
> >>>The ipconfig/all files are attached. Neither machine recognised the
> >>>'browstat' command.
> >>>
> >>>Much appreciated.
> >>>
> >>>Thanks,
> >>>
> >>>Steven
> >>
> >> There they are! Attachments! Never look for those!
> >> <http://nitecruzr.blogspot.com/2006/01/providing-diagnostic-data.html>
> >> http://nitecruzr.blogspot.com/2006/01/providing-diagnostic-data.html
> >>
> >> Steven, please post your replies after mine.
> >> <http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
> >> http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting
> >>
> >> How did you "prevent" Norton Antivirus from loading? Note that both NAV
> >> and NPF
> >> contain components that get installed into the network stack itself;
> >> disabling
> >> either product frequently causes problems like yours. You may have to un
> >> install NAV / NIS / NPF, following full instructions from Symantec.
> >> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
> >> http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
> >>
> >> Anyway, to get to the attachments, both bobby and tommy are running IPV6,
> >> aka
> >> Teredo Tunneling. Please remove that from both computers, restart both
> >> computers, and rerun all diagnostics.
> >> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
> >> http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
>
> >Chuck - I uninstalled the IPV6/Teredo on both machines. I also followed
> >Norton's instructions on adding the IP addresses of teh computers on teh
> >network to the General Rules for Internet Worm Protection. Firewalls are
> >still off.
> >
> >The new ipconfig files are attached. The symptoms are EXACTLT the same as
> >vefore.
> >
> >Next I'll try uninstalling Norton unless you can suggest something else.
>
> Steven,
>
> Let's first try and isolate the problem, and see which computer needs to be
> looked at.
>
> Take the following code (everything inside the "#####"). (Please verify computer
> names and ip addresses).
>
> 1. Open Notepad. Ensure that Format - Word Wrap is not checked. Highlight
> then Copy the code (Ctrl-C), precisely as it is presented, and Paste (Ctrl-V)
> into Notepad. Verify, and correct, names and addresses if necessary.
> 2. Save the Notepad file as "cdiag.cmd", as type "All Files", into the root
> folder "C:\".
> 3. Run it by Start - Run - "c:\cdiag".
> 4. Wait patiently.
> 5. 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 all computers, please, with all computers powered up and online.
>
> ##### Start CDiag Assembled Code
>
> @echo off
> set FullTarget1=bobby 192.168.0.2
> set FullTarget2=tommy 192.168.0.4
> set FullTarget3=
> set FullTarget4=
> set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
> set FullTargets=%FullTargets% 127.0.0.1
> set PingTargets=www.yahoo.com 66.94.230.32 192.168.0.1
> Set Version=V1.33
> @echo CDiagnosis %Version% >c:\cdiag.txt
> @echo Start diagnosis for %computername% >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> @echo Enumerate Shares >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> net share >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> @echo Adhoc Browser View >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> net view >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> @echo Full Targets %FullTargets% >>c:\cdiag.txt
> for %%a in (%FullTargets%) do (
> @echo. >>c:\cdiag.txt
> @echo Target %%a >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> @echo "%computername% ping %%a" >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> ping %%a >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> @echo "%computername% net view %%a" >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> net view %%a >>c:\cdiag.txt
> )
> @echo. >>c:\cdiag.txt
> @echo Ping Targets %PingTargets% >>c:\cdiag.txt
> for %%a in (%PingTargets%) do (
> @echo. >>c:\cdiag.txt
> @echo Target %%a >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> @echo "%computername% ping %%a" >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> ping %%a >>c:\cdiag.txt
> )
> @echo. >>c:\cdiag.txt
> @echo End diagnosis for %computername% >>c:\cdiag.txt
> notepad c:\cdiag.txt
> :EOF
>
> ##### End CDiag Assembled Code
>
> --
> Cheers,
> Chuck, MS-MVP [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My email is AT DOT
> actual address pchuck mvps org.
>
Chuck - again, many thanks for the help.
Here are the 2 data dumps - first the one generated by running cdiag.cmd on
bobby and then the one from tommy................
CDiagnosis V1.33
Start diagnosis for BOBBY
Enumerate Shares
Share name Resource Remark
-------------------------------------------------------------------------------
E$ E:\ Default share
IPC$ Remote IPC
D$ D:\ Default share
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
C$ C:\ Default share
ADMIN$ C:\WINDOWS Remote Admin
Desktop C:\Documents and Settings\Steven\Desktop
Shared Documents
D:\Shared Documents
Printer LPT1: Spooled Printer on BOBBY
Printer3 PrimoPort: Spooled PrimoPDF
The command completed successfully.
Adhoc Browser View
Server Name Remark
-------------------------------------------------------------------------------
\\BOBBY The Beast
\\TOMMY The Mean Machine
The command completed successfully.
Full Targets bobby 192.168.0.2 tommy 192.168.0.4 127.0.0.1
Target bobby
"BOBBY ping bobby"
Pinging bobby [192.168.0.2] with 32 bytes of data:Reply from 192.168.0.2:
bytes=32 time<1ms TTL=128Reply from 192.168.0.2: bytes=32 time<1ms
TTL=128Reply from 192.168.0.2: bytes=32 time<1ms TTL=128Reply from
192.168.0.2: bytes=32 time<1ms TTL=128Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"BOBBY net view bobby"
Shared resources at bobby
The Beast
Share name Type Used as Comment
-------------------------------------------------------------------------------
Desktop Disk
Printer Print Printer on BOBBY
Printer3 Print PrimoPDF
Shared Documents Disk
The command completed successfully.
Target 192.168.0.2
"BOBBY ping 192.168.0.2"
Pinging 192.168.0.2 with 32 bytes of data:Reply from 192.168.0.2: bytes=32
time<1ms TTL=128Reply from 192.168.0.2: bytes=32 time<1ms TTL=128Reply from
192.168.0.2: bytes=32 time<1ms TTL=128Reply from 192.168.0.2: bytes=32
time<1ms TTL=128Ping statistics for 192.168.0.2: Packets: Sent = 4,
Received = 4, Lost = 0 (0% loss),Approximate round trip times in
milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"BOBBY net view 192.168.0.2"
Shared resources at 192.168.0.2
The Beast
Share name Type Used as Comment
-------------------------------------------------------------------------------
Desktop Disk
Printer Print Printer on BOBBY
Printer3 Print PrimoPDF
Shared Documents Disk
The command completed successfully.
Target tommy
"BOBBY ping tommy"
Pinging tommy [192.168.0.4] with 32 bytes of data:Reply from 192.168.0.4:
bytes=32 time<1ms TTL=128Reply from 192.168.0.4: bytes=32 time<1ms
TTL=128Reply from 192.168.0.4: bytes=32 time<1ms TTL=128Reply from
192.168.0.4: bytes=32 time<1ms TTL=128Ping statistics for 192.168.0.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"BOBBY net view tommy"
Shared resources at tommy
The Mean Machine
Share name Type Used as Comment
-------------------------------------------------------------------------------
Desktop Disk
Keep Disk
SharedDocs Disk
The command completed successfully.
Target 192.168.0.4
"BOBBY ping 192.168.0.4"
Pinging 192.168.0.4 with 32 bytes of data:Reply from 192.168.0.4: bytes=32
time<1ms TTL=128Reply from 192.168.0.4: bytes=32 time<1ms TTL=128Reply from
192.168.0.4: bytes=32 time<1ms TTL=128Reply from 192.168.0.4: bytes=32
time<1ms TTL=128Ping statistics for 192.168.0.4: Packets: Sent = 4,
Received = 4, Lost = 0 (0% loss),Approximate round trip times in
milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"BOBBY net view 192.168.0.4"
Shared resources at 192.168.0.4
The Mean Machine
Share name Type Used as Comment
-------------------------------------------------------------------------------
Desktop Disk
Keep Disk
SharedDocs Disk
The command completed successfully.
Target 127.0.0.1
"BOBBY 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=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from
127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms
TTL=128Ping 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
"BOBBY net view 127.0.0.1"
Shared resources at 127.0.0.1
The Beast
Share name Type Used as Comment
-------------------------------------------------------------------------------
Desktop Disk
Printer Print Printer on BOBBY
Printer3 Print PrimoPDF
Shared Documents Disk
The command completed successfully.
Ping Targets www.yahoo.com 66.94.230.32 192.168.0.1
Target www.yahoo.com
"BOBBY ping www.yahoo.com"
Pinging www.yahoo.akadns.net [68.142.226.49] with 32 bytes of data:Reply
from 68.142.226.49: bytes=32 time=97ms TTL=46Reply from 68.142.226.49:
bytes=32 time=93ms TTL=47Reply from 68.142.226.49: bytes=32 time=94ms
TTL=46Reply from 68.142.226.49: bytes=32 time=96ms TTL=47Ping statistics for
68.142.226.49: Packets: Sent = 4, Received = 4, Lost = 0 (0%
loss),Approximate round trip times in milli-seconds: Minimum = 93ms,
Maximum = 97ms, Average = 95ms
Target 66.94.230.32
"BOBBY ping 66.94.230.32"
Pinging 66.94.230.32 with 32 bytes of data:Reply from 66.94.230.32: bytes=32
time=167ms TTL=44Reply from 66.94.230.32: bytes=32 time=167ms TTL=44Reply
from 66.94.230.32: bytes=32 time=168ms TTL=44Reply from 66.94.230.32:
bytes=32 time=171ms TTL=44Ping statistics for 66.94.230.32: Packets: Sent
= 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in
milli-seconds: Minimum = 167ms, Maximum = 171ms, Average = 168ms
Target 192.168.0.1
"BOBBY ping 192.168.0.1"
Pinging 192.168.0.1 with 32 bytes of data:Reply from 192.168.0.1: bytes=32
time=1ms TTL=30Reply from 192.168.0.1: bytes=32 time=1ms TTL=30Reply from
192.168.0.1: bytes=32 time=1ms TTL=30Reply from 192.168.0.1: bytes=32
time=1ms TTL=30Ping statistics for 192.168.0.1: Packets: Sent = 4,
Received = 4, Lost = 0 (0% loss),Approximate round trip times in
milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms
End diagnosis for BOBBY
.........................
CDiagnosis V1.33
Start diagnosis for TOMMY
Enumerate Shares
Share name Resource Remark
-------------------------------------------------------------------------------
D$ D:\ Default share
C$ C:\ Default share
ADMIN$ C:\WINDOWS Remote Admin
IPC$ Remote IPC
Desktop C:\Documents and Settings\Steven\Desktop
Keep D:\Keep
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS
The command completed successfully.
Adhoc Browser View
Full Targets bobby 192.168.0.2 tommy 192.168.0.4 127.0.0.1
Target bobby
"TOMMY ping bobby"
Pinging bobby [192.168.0.2] with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"TOMMY net view bobby"
Target 192.168.0.2
"TOMMY ping 192.168.0.2"
Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"TOMMY net view 192.168.0.2"
Target tommy
"TOMMY ping tommy"
Pinging tommy [192.168.0.4] with 32 bytes of data:
Reply from 192.168.0.4: bytes=32 time<1ms TTL=128
Reply from 192.168.0.4: bytes=32 time<1ms TTL=128
Reply from 192.168.0.4: bytes=32 time<1ms TTL=128
Reply from 192.168.0.4: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"TOMMY net view tommy"
Shared resources at tommy
The Mean Machine
Share name Type Used as Comment
-------------------------------------------------------------------------------
Desktop Disk
Keep Disk
SharedDocs Disk
The command completed successfully.
Target 192.168.0.4
"TOMMY ping 192.168.0.4"
Pinging 192.168.0.4 with 32 bytes of data:
Reply from 192.168.0.4: bytes=32 time<1ms TTL=128
Reply from 192.168.0.4: bytes=32 time<1ms TTL=128
Reply from 192.168.0.4: bytes=32 time<1ms TTL=128
Reply from 192.168.0.4: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
"TOMMY net view 192.168.0.4"
Shared resources at 192.168.0.4
The Mean Machine
Share name Type Used as Comment
-------------------------------------------------------------------------------
Desktop Disk
Keep Disk
SharedDocs Disk
The command completed successfully.
Target 127.0.0.1
"TOMMY 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
"TOMMY net view 127.0.0.1"
Shared resources at 127.0.0.1
The Mean Machine
Share name Type Used as Comment
-------------------------------------------------------------------------------
Desktop Disk
Keep Disk
SharedDocs Disk
The command completed successfully.
Ping Targets www.yahoo.com 66.94.230.32 192.168.0.1
Target www.yahoo.com
"TOMMY ping www.yahoo.com"
Pinging www.yahoo.akadns.net [68.142.226.47] with 32 bytes of data:
Reply from 68.142.226.47: bytes=32 time=95ms TTL=46
Reply from 68.142.226.47: bytes=32 time=95ms TTL=46
Reply from 68.142.226.47: bytes=32 time=96ms TTL=46
Reply from 68.142.226.47: bytes=32 time=95ms TTL=47
Ping statistics for 68.142.226.47:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 96ms, Average = 95ms
Target 66.94.230.32
"TOMMY ping 66.94.230.32"
Pinging 66.94.230.32 with 32 bytes of data:
Reply from 66.94.230.32: bytes=32 time=168ms TTL=44
Reply from 66.94.230.32: bytes=32 time=168ms TTL=44
Reply from 66.94.230.32: bytes=32 time=172ms TTL=44
Reply from 66.94.230.32: bytes=32 time=170ms TTL=44
Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 172ms, Average = 169ms
Target 192.168.0.1
"TOMMY ping 192.168.0.1"
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=30
Reply from 192.168.0.1: bytes=32 time=1ms TTL=30
Reply from 192.168.0.1: bytes=32 time=1ms TTL=30
Reply from 192.168.0.1: bytes=32 time=1ms TTL=30
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
End diagnosis for TOMMY
.
- Follow-Ups:
- Re: Network not accessible on one machine
- From: Chuck
- Re: Network not accessible on one machine
- References:
- Network not accessible on one machine
- From: Steven Lyall
- Re: Network not accessible on one machine
- From: Chuck
- Re: Network not accessible on one machine
- From: Steven Lyall
- Re: Network not accessible on one machine
- From: Chuck
- Re: Network not accessible on one machine
- From: Steven Lyall
- Re: Network not accessible on one machine
- From: Chuck
- Network not accessible on one machine
- Prev by Date: A whole host 'O userenv and other errors
- Next by Date: Re: Network Neighborhood computer asking for username/password
- Previous by thread: Re: Network not accessible on one machine
- Next by thread: Re: Network not accessible on one machine
- Index(es):
Relevant Pages
|
