Can not get 2 XP PC Connectivity

G

glamart

I'm using a DI-604 broadband router between a cable modem and 2
XP-sp1 PCs. Both PCs access their e-mail and the Internet with no
problem. However, I can not establish connectivity between the PCs
for file, print sharing, etc.

Trys: (I think all of Steve Winograd's std. Trys)
I have run the wizard to connect thru "residential gateway"
Workgroups are the same (MSHOME)
Sharing is enabled
Permissions are enabled
XP firewall disabled, Zone Alarm disabled
Binding to tcp/ip only
NetBios over TCP/IP is enabled
Reinstalled the NIC driver
Reset the tcp/ip stack (netsh)

I can NOT ping either computer from the other, I can ping the
router.

IPCONFIG /ALL:
Windows IP Config:

Host name: pro
Primary Dns Suffix: (Blank)
Node Type: Mixed (I set it with regedit)
IP Routing Enabled: No
WINS Proxy Enabled: No

Ethernet adapter Local Connection 2:
Connection-specific DNS Suffix Description: Intel Pro 1000 etc.
Physical Address: (MAC address of Router)
DHCP enabled: yes
Autoconfiguration Enabled: yes
IP Address: 192.168.0.101 (my pc)(other PC is 192.168.0.100)
Default Gateway:: 192.168.0.1 (the router)
DHCP Servers: 192.168.0.1
DNS Server: 192.168.0.1
Lease obtained: 15 Mar
Lease Expires: 15 Mar

Any ideas will be appreciated?
What about required Services?
I'‘m grasping for straws!
 
C

Chuck

I'm using a DI-604 broadband router between a cable modem and 2
XP-sp1 PCs. Both PCs access their e-mail and the Internet with no
problem. However, I can not establish connectivity between the PCs
for file, print sharing, etc.

Trys: (I think all of Steve Winograd's std. Trys)
I have run the wizard to connect thru "residential gateway"
Workgroups are the same (MSHOME)
Sharing is enabled
Permissions are enabled
XP firewall disabled, Zone Alarm disabled
Click to expand...

Un install ZA completely, following all procedures provided. ZA does not
disable properly for file sharing.

Or enable, and open the following ports (if this is ZA Pro and you can figure
out how to do this):
TCP 139, 445; UDP 137, 138, 445

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
G

glamart

Chuck said:
Un install ZA completely, following all procedures provided. ZA does not
disable properly for file sharing.

Or enable, and open the following ports (if this is ZA Pro and you can figure
out how to do this):
TCP 139, 445; UDP 137, 138, 445

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad
Click to expand...
thing.

Will give it a shot - thanks
--
Click to expand...
 
G

glamart

Chuck said:
Un install ZA completely, following all procedures provided. ZA does not
disable properly for file sharing.

Or enable, and open the following ports (if this is ZA Pro and you can figure
out how to do this):
TCP 139, 445; UDP 137, 138, 445

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad
Click to expand...
thing.

Didn't help - any other ideas?
Click to expand...
 
G

glamart

Chuck said:
Which did you try - un install ZA, or enable ZA, with the ports opened?

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad
Click to expand...
thing.

Uninstall - had to get rid of the service to be sure. Normally ZA
doesn't cause problems because it tells you when it does anything,
but you never know.
--
Click to expand...
Click to expand...
 
C

Chuck

Uninstall - had to get rid of the service to be sure. Normally ZA
doesn't cause problems because it tells you when it does anything,
but you never know.
Click to expand...

"Had to get rid of service to be sure". If you had to get rid of a service
after the un install, sounds like the un install didn't complete. This is NOT
an unknown experience with ZA.

1) Reboot.
2) Re install ZA.
3) Reboot.
4) Un install ZA carefully, following every ZA procedure.
5) Reboot.

If any component of ZA is left after #5 completed, the un install was not
conducted properly. You can't just "get rid of" a ZA component manually and
have a ZA computer work. ZA is known for not un installing completely, and,
since it embeds itself in the OS, something usually breaks during un install.

Diagnostic Procedure:
From Computer A:
1) Ping itself by name.
2) Ping itself by ip address.
3) Ping 127.0.0.1.
From Computer B:
4) Ping itself by name.
5) Ping itself by ip address.
6) Ping 127.0.0.1.
Report success / failure steps 1 - 6.

Is this ZA Free or Pro? Is it installed on Computer A or B? Name of Computer A
and B? Is there any firewall on the other computer?

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
G

glamart

Chuck said:
"Had to get rid of service to be sure". If you had to get rid of a service
after the un install, sounds like the un install didn't complete. This is NOT
an unknown experience with ZA.

1) Reboot.
2) Re install ZA.
3) Reboot.
4) Un install ZA carefully, following every ZA procedure.
5) Reboot.

If any component of ZA is left after #5 completed, the un install was not
conducted properly. You can't just "get rid of" a ZA component manually and
have a ZA computer work. ZA is known for not un installing completely, and,
since it embeds itself in the OS, something usually breaks during un install.

Diagnostic Procedure:
From Computer A:
1) Ping itself by name.
2) Ping itself by ip address.
3) Ping 127.0.0.1.
From Computer B:
4) Ping itself by name.
5) Ping itself by ip address.
6) Ping 127.0.0.1.
Report success / failure steps 1 - 6.

Is this ZA Free or Pro? Is it installed on Computer A or B? Name of Computer A
and B? Is there any firewall on the other computer?

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad
Click to expand...
thing.

The service was uninstalled with ZA uninstall - nothing left. Both
computers had ZA Pro.
No problem pinging each PC to itself by ip or name, or 127.0.0.1.
Can also ping the router and any web site. Each computer Just can't
ping the other by ip or name. Computer A's name is PRO, B's name is
BRO. The names don't seem to matter as long as they are alpha
characters.

I think that I am going to give up for the night, its after midnight
on the East coast - thanks for the thoughts!
Click to expand...
 
C

Chuck

Chuck said:
thing.

The service was uninstalled with ZA uninstall - nothing left. Both
computers had ZA Pro.
No problem pinging each PC to itself by ip or name, or 127.0.0.1.
Can also ping the router and any web site. Each computer Just can't
ping the other by ip or name. Computer A's name is PRO, B's name is
BRO. The names don't seem to matter as long as they are alpha
characters.

I think that I am going to give up for the night, its after midnight
on the East coast - thanks for the thoughts!
Click to expand...

Thanks for the update.

So did you un install ZA Pro from both Bro and Pro? Which computer can't ping
the other? By name or ip address?

What did you mean by "had to get rid of the service to be sure"? Was that on
Bro or Pro?

If this is ZA Pro, you can designate ports open. Re install ZA Pro on each,
define each (Bro and Pro) in the Local (Very Trusted) Zone on the other, and
open the following ports for Local Zone: TCP 139, 445; UDP 137, 138, 445.

If that doesn't help, swap network cable / router port between each.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Connectivity Issues 1
Cannot Access XP Pro PC from XP Home PC 4
Lost file sharing, XP pro 8
Networking third computer problem 3
wired and wireless network problems 3
'Set up a home... network' doesn't work 5
File / printer sharing 9
my computer will not respond to ping ; it is ivisible on the net 3

Top