XP Professional Networking Problem

[Guest]

Chuck -

I ran out of time today but will do what you asked tomorrow. Thank you so
much for the response.

Rhonda

I have been having the same problem. I just got a second computer, and both
desktops are running XP Pro, SP2, and I have a router. My newest computer
can see the other computer but when I try to access it it tells me that
'...may not be accessible, check with admin, may not have permissions for
this network resource...'
I have tried everything I can think of to remedy this, including turning off
firewalls on both computers. I also checked the system log and found that
the ip address of the new computer was denied by the network. I tried
releasing and renew all ip addresses (I am running them on obtain an IP
automatically) and the router is the DHCP software. I know that the IP
addresses are unique on each computer, but when I ran the troubleshooter it
said that one or more computer may have the same ip address. I am at a
complete standstill and am lost! Can someone please help???
Thank you so much -
Rhonda

Rhonda,

That's a very common problem, and can have various causes.

Could you please start a new thread, so it's easier to find? The above
statement, plus a set of IPConfigs for the two computers, is a good start.

Provide ipconfig information for each computer.
Start - Run - "cmd" - Type "ipconfig /all >c:\ipconfig.txt" into the command
window. Open Notepad, make sure that Format - Word Wrap is NOT checked!, open
file c:\ipconfig.txt, copy and paste entire contents into your next post.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

 

[Chuck]

Chuck -

I ran out of time today but will do what you asked tomorrow. Thank you so
much for the response.

Rhonda

Thanks for the update, Rhonda.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

 

[Guest]

Okay, here is it is:



Windows IP Configuration



Host Name . . . . . . . . . . . . : png1

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

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

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

DNS Suffix Search List. . . . . . : hsd1.pa.comcast.net.



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : hsd1.pa.comcast.net.

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection

Physical Address. . . . . . . . . : 00-11-11-C5-64-78

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

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.100

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

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 68.87.64.196

68.87.66.196

Lease Obtained. . . . . . . . . . : Friday, March 11, 2005 7:57:01 AM

Lease Expires . . . . . . . . . . : Saturday, March 12, 2005 7:57:01
AM

Any suggestions? Thanks again for your help.

Rhonda

 

[Chuck]

Okay, here is it is:

Any suggestions? Thanks again for your help.

Rhonda

Rhonda,

We really need IPConfig from each computer, to do any good.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

 

[Guest]

Oops - my mistake - sorry. Here is the other computer's configuration:



Windows IP Configuration



Host Name . . . . . . . . . . . . : PNG2

Primary Dns Suffix . . . . . . . :

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

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

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

DNS Suffix Search List. . . . . . : hsd1.pa.comcast.net.



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : hsd1.pa.comcast.net.

Description . . . . . . . . . . . : SMC EZ Card 10/100 PCI (SMC1211
Series)

Physical Address. . . . . . . . . : 00-10-B5-70-24-AE

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

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.101

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

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 68.87.64.196

68.87.66.196

Lease Obtained. . . . . . . . . . : Friday, March 11, 2005 8:29:50 AM

Lease Expires . . . . . . . . . . : Saturday, March 12, 2005 8:29:50
AM

Thank you again -
Rhonda

 

[Chuck]

Oops - my mistake - sorry. Here is the other computer's configuration:

Thank you again -
Rhonda

OK, Rhonda. No problems there. Both computers are on the same subnet. Node
types Hybrid and Unknown are compatible.

Let's enumerate your problems, so we can diagnose them.

Take the following code (everything inside the "#####"). (Please verify
computer names and ip addresses).

Open Notepad. Ensure that Format - Word Wrap is not checked. Highlight then
Copy the code (Ctrl-C), precisely as it is keyed, and Paste (Ctrl-V) into
Notepad. Verify, and correct, names and addresses if necessary.
Save the Notepad 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 all computers, please, with all computers powered up and online.

#####

@echo off
set FullTarget1=png1 192.168.1.100
set FullTarget2=PNG2 192.168.1.101
set FullTarget3=
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set PingTargets=127.0.0.1 192.168.1.1
Set Version=V1.07
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% (Targets %FullTargets%) >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "ping www.yahoo.com" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping www.yahoo.com >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "ping 66.94.230.32" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping 66.94.230.32 >>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

#####

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

 

[Guest]

Here is PNG1:

CDiagnosis V1.07
Start diagnosis for PNG1 (Targets png1 192.168.1.100 PNG2 192.168.1.101 )

"ping www.yahoo.com"



Pinging www.yahoo.akadns.net [68.142.226.39] with 32 bytes of data:



Reply from 68.142.226.39: bytes=32 time=29ms TTL=49

Reply from 68.142.226.39: bytes=32 time=23ms TTL=49

Reply from 68.142.226.39: bytes=32 time=22ms TTL=49

Reply from 68.142.226.39: bytes=32 time=39ms TTL=49



Ping statistics for 68.142.226.39:

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

Approximate round trip times in milli-seconds:

Minimum = 22ms, Maximum = 39ms, Average = 28ms


"ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=94ms TTL=47

Reply from 66.94.230.32: bytes=32 time=89ms TTL=47

Reply from 66.94.230.32: bytes=32 time=89ms TTL=47

Reply from 66.94.230.32: bytes=32 time=91ms TTL=47



Ping statistics for 66.94.230.32:

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

Approximate round trip times in milli-seconds:

Minimum = 89ms, Maximum = 94ms, Average = 90ms


Target png1

"ping png1"



Pinging png1 [192.168.1.100] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.1.100:

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

Approximate round trip times in milli-seconds:

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


"net view png1"

Shared resources at png1

Main computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
Printer3 Print Microsoft Office Document Image Writer
Printer4 Print hp deskjet 5550 series
SharedDocs Disk
The command completed successfully.


Target 192.168.1.100

"ping 192.168.1.100"



Pinging 192.168.1.100 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.1.100:

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

Approximate round trip times in milli-seconds:

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


"net view 192.168.1.100"

Shared resources at 192.168.1.100

Main computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
Printer3 Print Microsoft Office Document Image Writer
Printer4 Print hp deskjet 5550 series
SharedDocs Disk
The command completed successfully.

***********************************************************
End PNG1 - start PNG2
***********************************************************

Target PNG2

"ping PNG2"



Pinging PNG2 [192.168.1.101] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.101:

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


"net view PNG2"


Target 192.168.1.101

"ping 192.168.1.101"



Pinging 192.168.1.101 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.101:

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


"net view 192.168.1.101"


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"

Shared resources at 127.0.0.1

Main computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
Printer3 Print Microsoft Office Document Image Writer
Printer4 Print hp deskjet 5550 series
SharedDocs Disk
The command completed successfully.


Target 192.168.1.1

"ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time<1ms TTL=150

Reply from 192.168.1.1: bytes=32 time<1ms TTL=150

Reply from 192.168.1.1: bytes=32 time<1ms TTL=150

Reply from 192.168.1.1: bytes=32 time<1ms TTL=150



Ping statistics for 192.168.1.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 192.168.1.1"

End diagnosis for PNG1

And here is PNG2:

CDiagnosis V1.07
Start diagnosis for PNG2 (Targets png1 192.168.1.100 PNG2 192.168.1.101 )

"ping www.yahoo.com"



Pinging www.yahoo.akadns.net [216.109.118.74] with 32 bytes of data:



PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.



Ping statistics for 216.109.118.74:

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


"ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.



Ping statistics for 66.94.230.32:

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


Target png1

"ping png1"



Pinging png1 [192.168.1.100] with 32 bytes of data:



PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.



Ping statistics for 192.168.1.100:

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


"net view png1"


Target 192.168.1.100

"ping 192.168.1.100"



Pinging 192.168.1.100 with 32 bytes of data:



PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.



Ping statistics for 192.168.1.100:

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


"net view 192.168.1.100"


Target PNG2

"ping PNG2"



Pinging PNG2 [192.168.1.101] with 32 bytes of data:



PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.



Ping statistics for 192.168.1.101:

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


"net view PNG2"

Shared resources at PNG2

Back computer

Share name Type Used as Comment


-------------------------------------------------------------------------------
C Disk

**OWNER NAME DELETED** Disk

hpdeskje Print hp deskjet 5550 series (Copy 1)

My Documents Disk

Printer Print Print to this device to send a photo quality
fax.
Printer2 Print Print to this device to send a fax.

Printer9 Print Creates Adobe PDF

SharedDocs Disk

The command completed successfully.


Target 192.168.1.101

"ping 192.168.1.101"



Pinging 192.168.1.101 with 32 bytes of data:



PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.



Ping statistics for 192.168.1.101:

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


"net view 192.168.1.101"

Shared resources at 192.168.1.101

Back computer

Share name Type Used as Comment


-------------------------------------------------------------------------------
C Disk

**OWNER NAME DELETED** Disk

hpdeskje Print hp deskjet 5550 series (Copy 1)

My Documents Disk

Printer Print Print to this device to send a photo quality
fax.
Printer2 Print Print to this device to send a fax.

Printer9 Print Creates Adobe PDF

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"

Shared resources at 127.0.0.1

Back computer

Share name Type Used as Comment


-------------------------------------------------------------------------------
C Disk

**OWNER NAME DELETED** Disk

hpdeskje Print hp deskjet 5550 series (Copy 1)

My Documents Disk

Printer Print Print to this device to send a photo quality
fax.
Printer2 Print Print to this device to send a fax.

Printer9 Print Creates Adobe PDF

SharedDocs Disk

The command completed successfully.


Target 192.168.1.1

"ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.

PING: transmit failed, error code 65.



Ping statistics for 192.168.1.1:

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


"net view 192.168.1.1"

End diagnosis for PNG2
********************************************************
This is strange cause PNG2 also can contact the internet.

And again - thanks so much.

Rhonda

********************************************************
********************************************************

 

[Chuck]

********************************************************
This is strange cause PNG2 also can contact the internet.

And again - thanks so much.

Rhonda

********************************************************
********************************************************

Rhonda,

Obviously the problem starts with PNG2.

See if this article is relevant:
http://support.microsoft.com/default.aspx?scid=kb;en-us;316414

If this is a personal firewall problem (ZoneAlarm or another), remember that
disabling a firewall isn't always the right procedure. Some personal firewalls
like ZA are known to cause problems when disabled. You must either:
1) Enable and properly configure.
2) Un install carefully per instructions of vendor.

If that's not it, we'll dig deeper.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

 

[Guest]

I checked the link, but it didn't seem to pertain to my situation. I am not
running Zone Alarm. I do have Norton Anti-Virus on one PNG2 and McAfee
Security Center on PNG1. I've tried disabling the firewalls, but it didn't
help.

Thanks again -
Rhonda

 

[Chuck]

I checked the link, but it didn't seem to pertain to my situation. I am not
running Zone Alarm. I do have Norton Anti-Virus on one PNG2 and McAfee
Security Center on PNG1. I've tried disabling the firewalls, but it didn't
help.

Thanks again -
Rhonda

Rhonda,

PNG2 has multiple problems - from connecting outward (pinging internet sites or
PNG1), to being connected to by PNG1. Is PNG2 running just NAV, or is it Norton
Internet Security (which includes Norton Personal Firewall)?

Personal firewalls, like NIS / NPF, or MPF / MSC, are known in this forum for
causing problems even AFTER being disabled. Sometimes, there are only 2
solutions:
1) Enable than un install, carefully following all instructions from vendor.
2) Enable then configure properly to allow file sharing.

If PNG2 has NPF, try un installing NIS completely. This may require un
installing NAV, from reports by other folks with your problems. Follow
instructions from Symantec completely - NAV / NPF makes a lot of hooks in the
operating system, and may explain all of your symptoms.

Also, let's check for LSP / Winsock corruption, whether or not NAV / NIS / NPF
is involved.
http://support.microsoft.com/?id=318584
http://support.microsoft.com/?id=811259

If XP RTM or Service Pack 1:
1. Backup and delete the following registry keys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
2. Reboot.
3. Open the network connections folder, right click your network connection, and
click Properties.
4. Click Install | Protocol | Add.
5. Click "Have Disk...", type "\windows\inf" in the box, and click OK.
6. Click "Internet Protocol (TCP/IP)", then click OK.
7. Reboot.

If XP SP2:
1. Start - Run - "cmd".
2. Type "netsh winsock reset catalog" into the command window.

Give LSP-Fix <http://www.cexx.org/lspfix.htm>, WinsockFix
<http://www.tacktech.com/display.cfm?ttid=257>, or WinsockXPFix
<http://www.spychecker.com/program/winsockxpfix.html> a shot.

If no help yet, reset TCP/IP.
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the command
window.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

 

[Guest]

PNG2 is running NAV only, no firewall and PNG1 is running McAfee's Security
Center with firewall. I will check for corruptions tomorrow, as I again ran
out of time today. And once again - thank you so much for your help and
input. I'm hoping to get to the bottom of this mess so that I can work on my
new wireless mess at home!!!

Rhonda

***********************************************************

 

[Guest]

Okay, I PNG2 is not running any firewall protection at all. PNG1 is running
McAfee Security Center, and I made PNG2's IP address a trusted address. I
did checked the winsock and had the spychecker utility fix any winsock
registry problems. But I still am having the same problems with PNG2 and the
network. I'll be bald by the time I figure this one out cause I'm pulling
all of my hair OUT!!!

Again, thank you -
Rhonda
***********************************************************

 

[Chuck]

Okay, I PNG2 is not running any firewall protection at all. PNG1 is running
McAfee Security Center, and I made PNG2's IP address a trusted address. I
did checked the winsock and had the spychecker utility fix any winsock
registry problems. But I still am having the same problems with PNG2 and the
network. I'll be bald by the time I figure this one out cause I'm pulling
all of my hair OUT!!!

Again, thank you -
Rhonda

Rhonda,

Did you reset TCP/IP? That's the final step, and is not a terribly complex
procedure.
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the command
window.

All of your posts say that PNG2 can access the internet. Apparently it can, at
least it resolves names.
CDiagnosis V1.07
Start diagnosis for PNG2 (Targets png1 192.168.1.100 PNG2 192.168.1.101 )
"ping www.yahoo.com"
Pinging www.yahoo.akadns.net [216.109.118.74] with 32 bytes of data:
PING: transmit failed, error code 65.

If all else fails, keep reading. The answer is out there somewhere.
http://support.microsoft.com/?id=298100

p.s. I'm way ahead of you on the hair issue.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.