Can't share files on network

[Guest]

I have two computers both running XP SP2 and Zone Alarm (latest version). I
used the Network wizard to setup a home hetwork using "a residential
gateway". Neither computer can see the other.

I have browsed the message boards here and have tried the various links and
suggestions out there. I have tried careyholzman.com,
practicallynetworked.com, and also michna.com. None of these were of any
help to me.

From each computer I can ping the other just fine, but I can't see any
shared drives/files in My Network Places.

I am stumped!

 

[DLink Guru]

Have you tried setting Zonealarm to permit your trusted IPs access to your
computers? If you dont know how to do this i suggest uninstalling zonealarm,
not just disabling it. Alot of third party firewalls dont disable correctly
in XP. Why????? Have no idea.

Robert....

 

[Guest]

Yes, I have an IP range set as well as the actual IP address in Zone Alarm

 

[Blair]

I had a similar problem and uninstalled Zone Alarm and found that my network
worked OK
I found that I had not set the two IP addresses correctly in the Firewall
Zone settings.
Hope this helps
Blair

 

[DLink Guru]

Well, it couldnt hurt.......

Yes, I have an IP range set as well as the actual IP address in Zone Alarm
on both computers. I did install ZA before the network was created.
Would
unistalling ZA on both comps, re-doing the network, then reinstalling ZA
help?

 

[Steve Winograd [MVP]]

I have two computers both running XP SP2 and Zone Alarm (latest version). I
used the Network wizard to setup a home hetwork using "a residential
gateway". Neither computer can see the other.

I have browsed the message boards here and have tried the various links and
suggestions out there. I have tried careyholzman.com,
practicallynetworked.com, and also michna.com. None of these were of any
help to me.

From each computer I can ping the other just fine, but I can't see any
shared drives/files in My Network Places.

I am stumped!

I assume that you've actually shared some disks or folders on each
computer.

Try accessing the other computer by typing its name in the Start | Run
box in this format:

\\computer

If that succeeds (shows shared disks and folders), you can create
shortcuts to them by going to My Network Places and clicking "Add a
network place". If that fails, keep reading.

Since the computers can ping each other, I don't think that ZoneAlarm
is causing the problem. However, it wouldn't hurt to un-install
ZoneAlarm while troubleshooting. I assume that your residential
gateway is a typical home broadband router. Those routers act as
firewalls, preventing Internet hackers from accessing your computers.

You didn't say whether the computers can ping each other by IP
address, computer name, or both.

If they can ping each other by IP address but not by computer name,
there's a problem with NetBIOS name resolution. In that case, these
steps should help:

1. Use only one protocol for File and Printer Sharing. If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them. Details here:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

2. Make sure that NetBIOS over TCP/IP is enabled on each computer:

a. Open the Network Connections folder.
b. Right click the local area network connection.
c. Click Properties.
d. Double click Internet Protocol (TCP/IP).
e. Click Advanced.
f. Click WINS.
g. Click the Enable NetBIOS Over TCP/IP button.

3. Run "ipconfig /all" on each computer and look at the "Node Type" at
the beginning of the output. If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem. It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network, for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[ATK]

I assume that you've actually shared some disks or folders on each
computer.

Try accessing the other computer by typing its name in the Start | Run
box in this format:

\\computer

If that succeeds (shows shared disks and folders), you can create
shortcuts to them by going to My Network Places and clicking "Add a
network place". If that fails, keep reading.

Since the computers can ping each other, I don't think that ZoneAlarm
is causing the problem. However, it wouldn't hurt to un-install
ZoneAlarm while troubleshooting. I assume that your residential
gateway is a typical home broadband router. Those routers act as
firewalls, preventing Internet hackers from accessing your computers.

You didn't say whether the computers can ping each other by IP
address, computer name, or both.

If they can ping each other by IP address but not by computer name,
there's a problem with NetBIOS name resolution. In that case, these
steps should help:

1. Use only one protocol for File and Printer Sharing. If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them. Details here:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

2. Make sure that NetBIOS over TCP/IP is enabled on each computer:

a. Open the Network Connections folder.
b. Right click the local area network connection.
c. Click Properties.
d. Double click Internet Protocol (TCP/IP).
e. Click Advanced.
f. Click WINS.
g. Click the Enable NetBIOS Over TCP/IP button.

3. Run "ipconfig /all" on each computer and look at the "Node Type" at
the beginning of the output. If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem. It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network, for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053

If it helps I have just added the IP addresses of my LAN computers (and
printers) to the "trusted zone" within Zone Alarm: right-click
ZA/Restore..../Firewall/Zones/Add/IP Address/Trusted Zone......

 

[Guest]

I have not tried to ping by comp name yet, although I have double checked
that the names are compliant and even changed them.

I am pretty certain the IP's are inputed correctly in Zone Alarm. I have
triple checked that.

I have not been able to do ANYTHING between the two computers (execpt ping).
No sharing or viewing. I do have a router. It's a Linksys BEFW11S4
Wireless, altough I have the computers wired.

I will try Steve's and ATK's suggestions. Thanks for all the feedback!

 

[Interrogative]

I have two computers both running XP SP2 and Zone Alarm (latest version).
I
used the Network wizard to setup a home hetwork using "a residential
gateway". Neither computer can see the other.

I assume yur ZA, as you didnt say one way or the other, is the free version.
If so, out of the box, it doesnt support LANs. Only the PRO version, out of
the box, does. You can make ZA free edition work with it but the simple
answer to see if that is your only problem is to turn it off, before
attempting any changes. If it solves the problem then go add the network to
"trusted".

You also need to remember to actually share things on each computer on the
network or you are not going to see anything too useful, either.

 

[Interrogative]

If you are a D-Link guru, any experience with the DWL-120+ at all? Wondering
why it has an open network as default which is actually the same device
along with whatever you set to your own network needs. Mine constantly shows
that and it is from my own D-Link device. As it is wi-fi, though that SSID
isn't used, it continually makes me wonder if the damned thing is a possible
point of future trouble. So far, no problem.

Oh and you would think D-Link would know why wouldn't you?

 

[DLink Guru]

Im sorry, I have read your post over and over, but dont understand what you
are wanting. I cant think of any wireless device I have ever installed that
is not open or automatic by default. Shared, in mt experience, is not used
that often in a home enviroment.

Yes I have used the 120+ USB client before, although I dont us 802.11b much
anymore, more because dlink support on WPA variations is not strong on older
devices, although it uses 256-BIT WEP.

 

[Guest]

Yes I am using the free version. I have not had any problems in the past
using the free version on a nework. I have done it in the past.

I have fixed my problem, but am not sure exactly what did it. I completely
uninstalled ZA on both comps. Restarted. Ran the network wizard again on
both comps (changed all the names). Reinstalled ZA. Set trusted zones
accordingly.

Works just fine now. Thanks to all for the input!

 

[DLink Guru]

I told you. For some reason some third parties need to be completely
uninstalled then installed after the network is setup.

Robert...

 

[Interrogative]

Im sorry, I have read your post over and over, but dont understand what
you are wanting. I cant think of any wireless device I have ever installed
that is not open or automatic by default. Shared, in mt experience, is not
used that often in a home enviroment.

If I use an SSID of "123" with Wep etc and use that one I set up, I then
have, with the DWL-120+ two SSIDs, one called "123" and one called
"wireless" where "wireless" is open and infrastructure even if my own chosen
SSID is set up as ad hoc. So, my idea is that though I am protecting myself,
the DWL-120+ is also leaving me open by another route. That is what I meant
to say. Have you any experience with that?

Yes I have used the 120+ USB client before, although I dont us 802.11b
much anymore, more because dlink support on WPA variations is not strong
on older devices, although it uses 256-BIT WEP.

Yeah but that's the point. Why use WEP and do the right thing when the
device sets up another SSID open to anyone and you cant get rid of it?

 

[DLink Guru]

Were are you saying you are getting the second SSID from? The 120+ is a
client and has no place to set up a broadcasted SSID as you would in a AP.
If you are saying you see a second SSID on your wireless networks list, I
would say you are just seeing a neighbors unprotected network braodcasting.

Robert...

 

[Interrogative]

Were are you saying you are getting the second SSID from?

Again, if I set up an SSID "123" with WEP and ad hoc for example, the moment
it is ready, the 120 gives me access to "123" and "wireless" but "wireless"
is completely unprotected.

The 120+ is a client and has no place to set up a broadcasted SSID as you
would in a AP.

Yes it does. You set them up ad hoc if all you want to link is 2 computers.

If you are saying you see a second SSID on your wireless networks list, I
would say you are just seeing a neighbors unprotected network
braodcasting.

No, I am not. Both SSIDs come from the 120. That is why I am saying that no
matter how you set it up, it always leaves you open.

 

[DLink Guru]

A 120 cannot broadcast more then 1 SSID. It is impossible.

 

[Interrogative]

No, it isn't. I have 2 of them and with both on or just 1 on, it sends out
"wireless" and whatever you set up.

 

[DLink Guru]

No they dont, I dont know what your seeing, I still say its another network,
but these clients can only be setup for 1 SSID. If you set each to broadcast
a SSID 123 then thats all they broadcast, period.

 

[Interrogative]

Yes it darned IS sending both out. I know you THINK there is another network
and so did I at first. I even attempted to connect to it to see what it was
and when I connected, it showed ONLY my own data. "wireless" is set up as
open and an AP on channel 1 and my own SSID is ad hoc on channel 2 with WEP.