Ad Hoc Wireless

well, you've probably tried this but i would run the Network Setup Wizard on all of them. and turn *off* the firewalls (norton's and XP's) while you are getting it working...it is probably still the firewalls...

to resolve the access is denied message, you have to create identical accounts (name + password) on all machines to be able to connect to the shares.

on the laptop , I would update the drivers and disable to all firewall to check the browsing issue.

Leopold

I'm afraid I have no intention of running the network wizard!

My network runs great on all other machines. I was thinking it may be a conflict with drivers on the laptop card?

Not all my PCs have identical accounts on them, yet they browse successfullly. I will try adding accounts, though.

Many thanks for your help so far. I'll be sure to let you know how I get on.

Good advice on both parts. Ensure Norton's firewall is setup for your network to allow the NetBIOS traffic. Also you didn't mention if you were using home edition or pro of XP, but don't forget that XP comes with it's own firewall, called ICF on home edition. Make sure you turn that off or configure it if it's enabled through the network settings.

I agree with the above that the access denied is likely account setup.

Still no further on, in fact things have taken a retrograde step - one of my desktop PC's has disappeared from Show Workgroup Computers. I have no explanation! It can still be reached if I type the path into explorer. I am baffled, and will revert to wired networking as a temp measure to ensure the TCP/IP & Workgroup sides of things is configured correctly.

1.Client for Microsoft Networking, File and Printer Sharing installed, all machines
2.All machines have identical Workgroup names, and different machine names
3.TCP/IP properties:
.All machines obtain an IP address automaticly.
.Advanced button, DNS tab, "Enable Netbios over TCP/IP" disable use LMHOSTS.
4.Make all users of Comp A users of Comp B & C and similarly for all machines repeat process.
5.Share something:folder,something on computers.All comps then will have same list of username and passwords.
6.Remove firewalls,mainly native XP ICS firewall.
7.Every user logs on with a username and password.No blank or empty passwords.

Firewalls and networking is relatively easy to solve in theory,sometimes hard to implement.The following ports are associated with file sharing and server message block (SMB) communications.
Microsoft file sharing SMB:
-User Datagram Protocol (UDP) ports from 135 through 139, Transmission Control Protocol (TCP) ports from 135-139.
-Direct-hosted SMB traffic without network basic input/output system (NetBIOS) uses port 445 (TCP and UPD).
1.Using the native XP firewall to open the preceding ports:Click Start,Connect To,right-click the network connection thats firewall protected, click Properties.
On Advanced tab, click Settings then Add in the Service Tab area.Enter a description for the connection and use the loopback address (127.0.0.1) for the required (IP) number.Do this 12 times.The description can be anything you like,'LAN UDP 135' for port labels.Enter both a port number and type for each port (the external and internal port numbers should be identical). The port ranges may not be specified.Repeat 12 times so that you have UDP 135, 136, 137, 138, 139 and 445. TCP 135, 136, 137, 138, 139 and 445.Click OK to exit each window.
2. Other Firewalls
How they are configured can be generalized.
1. Zone-based Firewalls. This includes the Norton Firewall.You designate your LAN as "Trusted Zone", permit all traffic on IP range used by your network.Example,network has IP addresses like 192.168.0.x, enter as your Trusted Zone all traffic from all adapters for 192.168.0.0 -- 192.168.0.255.
2. Any Firewall Netbios aware.Often firewalls know all about local area networks, and you need only enable all traffic on your "Network Neighborhood" to occur.Best source of config info about the firewall and your Windows LAN is the web site of the firewall manufacturer.

Solved! The problem was shared internet access on the main PC. I had used the built-in firewall (ICF) as well as Norton IS 2003 firewall to protect the PC(s), and had selected the WLAN as the local connector for other PCs. As soon as I turned off the ICF, everything was resolved. On disrespect to MS, but it seems to me that ICF is more trouble than it is worth - I certainly wouldn't trust it on it's own to protect my network.

Many, many thanks to you all for your answers. They all helped, so I have accepted them all. I don't know if you will each receive 1000 points (big points bill for me) or if you will all share the 1000. Thanks a lot anyway, I hope to be able to return the compliment sometime!

Simon.

This question was closed by the author