cannot connect two win2k computers

  • Thread starter Thread starter Herb Martin
  • Start date Start date
H

Herb Martin

wendeebee said:
Computer B has just been reformatted. Previously, it was shared with
Computer A.
Computer B sees the router signal and is able to connect to the shared
internet connection.

Computer A is the base station and no settings have changed on it. It has a
modem and a wireless router. It can see Comp B's icon in Computers Near Me,
but the network path is not found.

Default Gateway, Subnet masks and Workgroup names match.

Can anybody tell me how to open the path again?
Click to expand...


Can you ping? By name? By address?

Open a command prompt. Find the address on B
(you can always type "ipconfig" to do that.)

Ping it and the name from A. Tell us which works,
or what happens (exactly).

If you cannot ping by number, do this (on each of A/B):

ipconfig /all >a.txt

ipconfig /all >b.txt

Paste the files into the BODY of a message as TEXT
and send it here so we can look.

Can you reach the Internet with both of these?
 
Computer B has just been reformatted. Previously, it was shared with
Computer A.
Computer B sees the router signal and is able to connect to the shared
internet connection.

Computer A is the base station and no settings have changed on it. It has a
modem and a wireless router. It can see Comp B's icon in Computers Near Me,
but the network path is not found.

Default Gateway, Subnet masks and Workgroup names match.

Can anybody tell me how to open the path again?

TIA,
Wendy
 
Herb Martin said:
has


Can you ping? By name? By address?

Open a command prompt. Find the address on B
(you can always type "ipconfig" to do that.)

Ping it and the name from A. Tell us which works,
or what happens (exactly).

If you cannot ping by number, do this (on each of A/B):

ipconfig /all >a.txt

ipconfig /all >b.txt

Paste the files into the BODY of a message as TEXT
and send it here so we can look.

Can you reach the Internet with both of these?
Click to expand...


Yes, both computers can connect to the Internet.

Pinging from Computer A(base station) to Computer B:

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),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

------------------------

Pinging from Computer B to Computer A:

C:\>ping 192.168.1.100

Pinging 192.168.1.100 with 32 bytes of data:

Reply from 192.168.1.100: bytes=32 time<10ms TTL=128
Reply from 192.168.1.100: bytes=32 time<10ms TTL=128
Reply from 192.168.1.100: bytes=32 time<10ms TTL=128
Reply from 192.168.1.100: bytes=32 time<10ms 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


Any thoughts? Thanks so much for responding!
 
Ping it and the name from A. Tell us which works,
Yes, both computers can connect to the Internet.
Click to expand...

Ok, then IP is basically working.
Pinging from Computer A(base station) to Computer B:
Pinging 192.168.1.101 with 32 bytes of data:
Request timed out.
Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

------------------------
Pinging from Computer B to Computer A:
C:\>ping 192.168.1.100
Pinging 192.168.1.100 with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time<10ms TTL=128
Click to expand...

Ok, A->B failure would point to IP problems execpt that
B->A works so the most likely is the FIRWALL settings
on A (if this is XP, especially SP2 or you have an extra
firewall installed.)

Check any firealls and either fix or let us know what you
see.
Any thoughts? Thanks so much for responding!
Click to expand...

Well, one would be to go on with the whole set of tests
like pinging by Name from the one that works: B->A?

And especially, the IPCONFIG /ALL output from each
in order to save you several (days of) turnarounds on
messages.

If you cannot ping by number, do this (on each of A/B):

ipconfig /all >a.txt

ipconfig /all >b.txt

Paste the files into the BODY of a message as TEXT
and send it here so we can look.

What is shared from each? Do the follow ON EACH:

Net share >Ashares.txt
Net share >Bshares.txt

(Something has to be shared for the machine to appear
in the other machines browse list.)
 
First off, both machines are Win2k Prof Edition. I'm just a novice, so I'm
not sure how to do some of the stuff you mentioned.
Click to expand...

That won't be a big issue if you just ask.

Open a comman prompt (aka command line, even "DOS prompt")
and perform the exact commands I gave you:

Open the text files in notepad, copy & paste the results to the
message you post here. Pretty much the same as what you did
for Ping will work just fine.
We have a LinkSys
wireless router --is that where I should be checking for a firewall?
Click to expand...

Possibly (probably not though), some of the newer ones
have them, but more likely such problems will be on the
XP machines, in the NIC properties.

This is especially true if the XP is Service Pack 2 which
turned on the firewall BY DEFAULT.

The LinkSys would more likely be the culprit if you couldn't
reach the Internet (through it).
Other
than that, I don't own any commercial firewall products.
Click to expand...

Ok, then only the built-in XP firewall is likely, and only
likely to be TURNED ON if you have Service Pack 2.
Both computers have folders with sharing enabled on them.
Click to expand...

Ok, so if you type (on each separate) the:

net share >ashares.txt
net share >bshares.txt

....and send the results, then I should see that too.
I am assuming the instructions you gave me are all command prompts, correct?

Correct.

When you say 'pinging by name' do you mean the name of the system? ....My
Computer>Properties>Network Identification and the name found there?
Click to expand...

Right. The name of the "other" machine when pinging
from one of them.

The same as you did for addresses (one worked and one
failed.) The one that failed is not going to work by name
but we can see if the other one works by name SINCE
pinging by address worked.
I don't know what 'ping by number' means.
Click to expand...

IP address, something like:

ping 192.168.100.1

(Like you did before.)
When you say 'ipconfig /all>b.txt' does what does the '>b.txt' refer to
specifically? Do I include the '.txt' suffix?
Click to expand...

Sends it to a text file so it is easy to open with notepad.
You should just be able to type:

notepad b.txt

....after that and have notepad open the file.
Sorry for my ignorance, but I just want to be specific before I go poking
around in everything.
Click to expand...

Ók, and all you have to do is ask when you don't understand.

You cannot hurt anything significant with Ping, IPConfig,
nslookup (we aren't using that right now), tracert, or even
Notepad as long as with the latter you don't edit any existing
files AND save them.


Thanks again for your time Herb :)
--Wendy
Click to expand...

Sure.
 
Ok, then IP is basically working.
Ok, A->B failure would point to IP problems execpt that
B->A works so the most likely is the FIRWALL settings
on A (if this is XP, especially SP2 or you have an extra
firewall installed.)

Check any firealls and either fix or let us know what you
see.


Well, one would be to go on with the whole set of tests
like pinging by Name from the one that works: B->A?

And especially, the IPCONFIG /ALL output from each
in order to save you several (days of) turnarounds on
messages.

If you cannot ping by number, do this (on each of A/B):

ipconfig /all >a.txt

ipconfig /all >b.txt

Paste the files into the BODY of a message as TEXT
and send it here so we can look.

What is shared from each? Do the follow ON EACH:

Net share >Ashares.txt
Net share >Bshares.txt

(Something has to be shared for the machine to appear
in the other machines browse list.) --
Herb Martin
Click to expand...



First off, both machines are Win2k Prof Edition. I'm just a novice, so I'm
not sure how to do some of the stuff you mentioned. We have a LinkSys
wireless router --is that where I should be checking for a firewall? Other
than that, I don't own any commercial firewall products.

Both computers have folders with sharing enabled on them.

I am assuming the instructions you gave me are all command prompts, correct?

When you say 'pinging by name' do you mean the name of the system? ....My
Computer>Properties>Network Identification and the name found there?

I don't know what 'ping by number' means.
When you say 'ipconfig /all>b.txt' does what does the '>b.txt' refer to
specifically? Do I include the '.txt' suffix?

Sorry for my ignorance, but I just want to be specific before I go poking
around in everything.
Thanks again for your time Herb :)
--Wendy
 
B (system-41b46a6e) ->A (Wendy-zmud8nvrn)

First those (NetBIOS) names are suspicious but seem to be legal.

They are LESS than 16 characters (I prefer less than 15 but this
shouldn't matter here), and the "-" is technically legal, although
again, I would only use INITIAL alphabetic, followed by up to
13 alphanumerics. They are however legal.

Broadcast name resolution should work if the machines can
ping and are on the same subnet (as the addresses sugget.)

Such tends to argue for switch/hub issues, maybe cable.

What are the plugged into? You need to give me a clear
description of how each is physically connected (to what
device etc.)

Ping by name:
c:\ping Wendy-zmud8nvrn
Unknown host Wendy-zmud8nvrn.
Click to expand...

Ok, name resolution fails -- the address is never tried,
and in the next, we see IP work so this implies your
network is basically working (hardware, IP addresses)
and leads us back to name resolution. (So I spent a
long time looking at those machine names to make sure
they were legal.)
_______________________
Ping by Number:
Pinging 192.168.1.100 with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Click to expand...

IP worked B->A but fails the other direction.
This almost never happens EXCEPT when B (the
one that fails) is running a Firewall and has thereby
disabled responding to pings.

This means we really should check the Firewall on the
NIC of machine B.
__________________________
Net Share:
Share name Resource Remark
-------------------------------------------------------------------------- --
Share E:\Share
The command completed successfully.
Click to expand...

Ok, they both have something NON-HIDDEN shared:
i.e., that share named SHARE.
From Computer B:
IPconfig all:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : system-41b46a6e
Primary DNS Suffix . . . . . . . :
Click to expand...

This shouldn't matter since you are using the short
or NetBIOS name in each attempt to connect.
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wireless PCI Adapter MN-730
Physical Address. . . . . . . . . : 00-0D-3A-6D-B9-DA
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 . . . . . . . . . . . : 206.47.244.113
206.47.244.52
Lease Obtained. . . . . . . . . . : Sunday, January 16, 2005 12:46:01 PM
Lease Expires . . . . . . . . . . : Monday, January 17, 2005 12:46:01 PM

Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Cable Disconnected
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0C-6E-4F-25-56
Click to expand...

Ok, I don't know what the above NIC is doing but it doesn't
seem to be in use -- did you perhaps have a NIC
in your computer and the cable company added another?
Shouldn't hurt anything.
++++++++++++++++++++++++++++++++++++++++++
From Computer A:
Ipconfig /all:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : wendy-zmud8nvrn
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 3:
Media State . . . . . . . . . . . : Cable Disconnected
Description . . . . . . . . . . . : Efficient Networks Enternet P.P.P.o.E
Physical Address. . . . . . . . . : 44-45-53-54-77-77
Ethernet adapter Local Area Connection:
Click to expand...

One must wonder what this is? Did they perhaps install
PPOE on your first machine (computer A) and it is
acting a a virtual NIC (not a real one) and in some way
taking over the real NIC?

Someone else here may know the answer but I am suspicious
of this as maybe being involved in the problem.
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI For
Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-04-75-8B-03-95
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : No
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 . . . . . . . . . . . : 206.47.244.113
206.47.244.52
Lease Obtained. . . . . . . . . . : Sunday, January 16, 2005 4:42:50 AM
Lease Expires . . . . . . . . . . : Monday, January 17, 2005 4:42:50 AM
_____________________________
Ping by name:
Unknown host System-41b46a6e.
_____________________________________
Ping by number:
Pinging 192.168.1.101 with 32 bytes of data:
Request timed out.
Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
_____________________________________________
Net Share:
Share name Resource Remark
-------------------------------------------------------------------------- --
IPC$ Remote IPC
Shared E:\Shared
The command completed successfully.
Click to expand...

What sort of machine is this? It doesn't seem to
be NT-class (Win2000, XP etc) since it isn't automatically
sharing it's C drive?
This is the current info from both machines.
Thank you,
Wendy
Click to expand...

I don't see it -- I am suspicious of the PPOE stuff,
or perhaps the firewall on B.

Otherwise it makes no sense that ping by number
works only one direction.

That must be fixed FIRST, then we move on to
Name, then to seeing shares in Network Neighborhood.

Otherwise you hardware devices are somehow
suppressing the name broadcasts that must work (here)
for name resolution.

Again, I need you to describe precisely how this
stuff is plugged together.


--
Herb Martin


 
Herb Martin said:
That won't be a big issue if you just ask.

Open a comman prompt (aka command line, even "DOS prompt")
and perform the exact commands I gave you:

Open the text files in notepad, copy & paste the results to the
message you post here. Pretty much the same as what you did
for Ping will work just fine.


Possibly (probably not though), some of the newer ones
have them, but more likely such problems will be on the
XP machines, in the NIC properties.

This is especially true if the XP is Service Pack 2 which
turned on the firewall BY DEFAULT.

The LinkSys would more likely be the culprit if you couldn't
reach the Internet (through it).


Ok, then only the built-in XP firewall is likely, and only
likely to be TURNED ON if you have Service Pack 2.


Ok, so if you type (on each separate) the:

net share >ashares.txt
net share >bshares.txt

...and send the results, then I should see that too.


Right. The name of the "other" machine when pinging
from one of them.

The same as you did for addresses (one worked and one
failed.) The one that failed is not going to work by name
but we can see if the other one works by name SINCE
pinging by address worked.


IP address, something like:

ping 192.168.100.1

(Like you did before.)


Sends it to a text file so it is easy to open with notepad.
You should just be able to type:

notepad b.txt

...after that and have notepad open the file.


Ók, and all you have to do is ask when you don't understand.

You cannot hurt anything significant with Ping, IPConfig,
nslookup (we aren't using that right now), tracert, or even
Notepad as long as with the latter you don't edit any existing
files AND save them.




Sure.
Click to expand...




From Computer B:
____________________
IPconfig all:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : system-41b46a6e
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast

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

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


Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wireless PCI Adapter MN-730
Physical Address. . . . . . . . . : 00-0D-3A-6D-B9-DA

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 . . . . . . . . . . . : 206.47.244.113
206.47.244.52
Lease Obtained. . . . . . . . . . : Sunday, January 16, 2005 12:46:01 PM

Lease Expires . . . . . . . . . . : Monday, January 17, 2005 12:46:01 PM


Ethernet adapter Local Area Connection:



Media State . . . . . . . . . . . : Cable Disconnected

Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0C-6E-4F-25-56

______________

Ping by name:


c:\ping Wendy-zmud8nvrn
Unknown host Wendy-zmud8nvrn.



_______________________
Ping by Number:


Pinging 192.168.1.100 with 32 bytes of data:



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

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

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

Reply from 192.168.1.100: bytes=32 time<10ms 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 Share:



Share name Resource Remark


----------------------------------------------------------------------------
---
IPC$ Remote IPC
D$ D:\ Default share
C$ C:\ Default share
ADMIN$ C:\WINNT Remote Admin
H$ H:\ Default share
E$ E:\ Default share
Share E:\Share
The command completed successfully.



++++++++++++++++++++++++++++++++++++++++++



From Computer A:
Ipconfig /all:



Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : wendy-zmud8nvrn
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid

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

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


Ethernet adapter Local Area Connection 3:



Media State . . . . . . . . . . . : Cable Disconnected

Description . . . . . . . . . . . : Efficient Networks Enternet P.P.P.o.E
Adapter
Physical Address. . . . . . . . . : 44-45-53-54-77-77


Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI For
Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-04-75-8B-03-95

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : No

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 . . . . . . . . . . . : 206.47.244.113
206.47.244.52
Lease Obtained. . . . . . . . . . : Sunday, January 16, 2005 4:42:50 AM

Lease Expires . . . . . . . . . . : Monday, January 17, 2005 4:42:50 AM

_____________________________
Ping by name:


Unknown host System-41b46a6e.

_____________________________________

Ping by number:




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),

Approximate round trip times in milli-seconds:

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

_____________________________________________

Net Share:


Share name Resource Remark


----------------------------------------------------------------------------
---
IPC$ Remote IPC
Shared E:\Shared
The command completed successfully.



This is the current info from both machines.
Thank you,
Wendy
 
IP worked B->A but fails the other direction.
This almost never happens EXCEPT when B (the
one that fails) is running a Firewall and has thereby
disabled responding to pings.

This means we really should check the Firewall on the
NIC of machine B.
Click to expand...

Howdy,

I hesitated to comment because few know less about this than
I, but...

Recently, I had difficulties that seemed similar to those
described in this thread. I had ZoneAlarm installed on one
machine but it was definitely turned OFF. Because it was OFF
I incorrectly assumed that it could not be contributing to
my difficulties.

When I removed it, my difficulties vanished.

All the best,
 
HERB!!! Thank you SO MUCH for your time and effort. You pointed me in the
right direction, and that was firewall interference. There was a secondary
application running under Norton (2 icons running in the sys tray, I didn't
realize the other one was Norton as well), and I found the firewall settings
and told it to let Computer A (Wendy-zmud8nvrn) in. A ping here, a ping
there and we have communication.
Click to expand...

Cool. It did seem to be a Computer B firewall
issue. Glad I kept saying that.
In the meantime, I learned about Cmd prompt files, and that neat little
trick about getting them to write directly to a .txt file, and a whole lot
about communication.
Click to expand...

I love helping those who appreciate the command
line. Keep learning.

I've been trying to figure this out since last Tuesday, so it is such a
relief to get it solved.
Click to expand...

I can only imagine.
Again, thanks a million for your time and expertise. I couldn't have done it
without you, and I'm saving all your emails to my geeky win2000 archives.
Click to expand...

Ok. Let me know if I can help you more.

As you can tell, the primary means to troubleshoot
a problem are these:

1) Simplify (get away from the GUI, use simple tools etc.)
2) Be very explicit -- force youreself to name each problem
exactly avoid "pronouns" (instead saying WHAT is giving
an error or not working), seek specific verbs and other
words (substitute what is actually happening for things
like "not working".)
3) Divide and conquer -- this is similar to #1 and related to
#3 by not only being specific by trying to isolate the
individual component or tool so that it is clear not only
what is not working and how, but which element is
causing the problem.

It can also be useful to capture or write down the key results,
especially while you are still a beginner.
 
Herb Martin said:
First those (NetBIOS) names are suspicious but seem to be legal.

They are LESS than 16 characters (I prefer less than 15 but this
shouldn't matter here), and the "-" is technically legal, although
again, I would only use INITIAL alphabetic, followed by up to
13 alphanumerics. They are however legal.

Broadcast name resolution should work if the machines can
ping and are on the same subnet (as the addresses sugget.)

Such tends to argue for switch/hub issues, maybe cable.

What are the plugged into? You need to give me a clear
description of how each is physically connected (to what
device etc.)



Ok, name resolution fails -- the address is never tried,
and in the next, we see IP work so this implies your
network is basically working (hardware, IP addresses)
and leads us back to name resolution. (So I spent a
long time looking at those machine names to make sure
they were legal.)


IP worked B->A but fails the other direction.
This almost never happens EXCEPT when B (the
one that fails) is running a Firewall and has thereby
disabled responding to pings.

This means we really should check the Firewall on the
NIC of machine B.


Ok, they both have something NON-HIDDEN shared:
i.e., that share named SHARE.


This shouldn't matter since you are using the short
or NetBIOS name in each attempt to connect.


Ok, I don't know what the above NIC is doing but it doesn't
seem to be in use -- did you perhaps have a NIC
in your computer and the cable company added another?
Shouldn't hurt anything.


One must wonder what this is? Did they perhaps install
PPOE on your first machine (computer A) and it is
acting a a virtual NIC (not a real one) and in some way
taking over the real NIC?

Someone else here may know the answer but I am suspicious
of this as maybe being involved in the problem.


What sort of machine is this? It doesn't seem to
be NT-class (Win2000, XP etc) since it isn't automatically
sharing it's C drive?


I don't see it -- I am suspicious of the PPOE stuff,
or perhaps the firewall on B.

Otherwise it makes no sense that ping by number
works only one direction.

That must be fixed FIRST, then we move on to
Name, then to seeing shares in Network Neighborhood.

Otherwise you hardware devices are somehow
suppressing the name broadcasts that must work (here)
for name resolution.

Again, I need you to describe precisely how this
stuff is plugged together.
Click to expand...

HERB!!! Thank you SO MUCH for your time and effort. You pointed me in the
right direction, and that was firewall interference. There was a secondary
application running under Norton (2 icons running in the sys tray, I didn't
realize the other one was Norton as well), and I found the firewall settings
and told it to let Computer A (Wendy-zmud8nvrn) in. A ping here, a ping
there and we have communication.

In the meantime, I learned about Cmd prompt files, and that neat little
trick about getting them to write directly to a .txt file, and a whole lot
about communication.

I've been trying to figure this out since last Tuesday, so it is such a
relief to get it solved.
Again, thanks a million for your time and expertise. I couldn't have done it
without you, and I'm saving all your emails to my geeky win2000 archives.

Have a great night!
--Wendy
 
Kenneth said:
Howdy,

I hesitated to comment because few know less about this than
I, but...

Recently, I had difficulties that seemed similar to those
described in this thread. I had ZoneAlarm installed on one
machine but it was definitely turned OFF. Because it was OFF
I incorrectly assumed that it could not be contributing to
my difficulties.

When I removed it, my difficulties vanished.

All the best,
Click to expand...


Thank you Kenneth. As it turned out, you were definitely on the right track,
as the culprit was a 'personal firewall' built into Norton 2004. I finally
found the config menu, and entered Computer A's IP into it to tell it to
permit access. How quickly the frustration fades when the 'eureka' moment
occurs. Thanks very much for your input, every little bit helps!
--Wendy
 
Thank you Kenneth. As it turned out, you were definitely on the right track,
as the culprit was a 'personal firewall' built into Norton 2004. I finally
found the config menu, and entered Computer A's IP into it to tell it to
permit access. How quickly the frustration fades when the 'eureka' moment
occurs. Thanks very much for your input, every little bit helps!
--Wendy
Click to expand...

Hi Wendy,

My specific issue was also incredibly frustrating.

I had installed V2i Protector (now Ghost) on our machines
and could not get them to put images on any remote machine.

The folks at PowerQuest were incredibly patient, and
helpful, but we could not get the thing to work over the
network.

Early in our efforts they asked "Do you have a firewall
running" and in good faith I answered "No" because I had
turned ZoneAlarm off.

It did not occur to any of us at the time that the mere fact
that ZA was on the machines could be causing the problem.

I discovered it accidentally months later.

Ah, the sweet relief...!

All the best,
 
Back
Top