"My Network's Not a Network" Fri Nov-12-04 12:54 AM by dbahn
I need some advice on how to troubleshoot this problem setting up a home network. Here's where I've done so far:
1. Set up a Linksys B router, connected to a cable modem. 2. Connected the DELL04, running XP Home (these capitals are the names used for the connection wizard)to the router. 3. Connected my old GATEWAY (W98) to the router via ethernet cable. 4. Set up the LAPTOP (WMe) using a wireless connection.
All internet connectivity is working fine, so then I've done the following:
5. I've since then used the Connection Wizard on the DELL04, using HOMENETWORK as the network name, and set up a floppy disc to use on the other two computers. 6. Used the floppy Network Setup on each of the other computers, making sure I used the same network name on all of the computers. 7. Followed all of the steps in the Network Wizards, checking the option that the computers are connected via a residential gateway and rebooting at the prompt.
It seems to me I've done all the right steps, but I'm unable to share files or to print on the network printers.
#1. "RE: My Network's Not a Network" In response to dbahn (Reply # 0)
Have you actually set up a shared folder? E.g. right click a folder and select sharing and security. Check the share this folder box. Then go to the other computer and browse My Network Places.
If you still can't access the other computers, check to see if you are running a firewall of some sort - like the firewall that comes with PC-Cillin.
Neil
============================================
In the computer world, there’s a right way, a wrong way, and the Mac way. The Mac way is essentially the same as the wrong way, except it’s much faster and on a much larger scale.
Yes, I've set up some shared folders to be able to test it.
When I go to My Network Places, on the LAPTOP, for instance, I get three options. 1. Add Network Place - when I browse on this I don't get the option of the other computers, just the Laptop 2. Home Networking Wizard - which I've done several times 3. Entire Network - clicking on this opens Homenetwork, but clicking on that only shows the Laptop, not the other computers.
I'm checking now to see what happens doing the same thing from the other computers.
As to firewalls, I'm using ZA and I believe the XP firewall is running since I installed SP2.
#3. "RE: My Network's Not a Network" In response to dbahn (Reply # 2)
The last time I had the same problem was when I inadvertantly setup my desktop after reinstalling WinXP Pro with a different workgroup name than I had before. Until I changed the workgroup name to be the same as that of the laptop I could not communicate. After that all was comfy. Don't know if that's your problem, but worth looking at.
#4. "RE: My Network's Not a Network" In response to scaison (Reply # 3) Fri Nov-12-04 12:58 AM by dbahn
I've double checked that, running the Wizard on all three computers and naming the network HOMENETWORK on all three, after it initially defaults to MSHOME.
EDIT: If I'm on the home computer and go to Run -> \\GATEWAY\ Porter House (Porter House was set up as a shared file on the Gateway) I get a prompt that the network path was not found.
#5. "RE: My Network's Not a Network" In response to dbahn (Reply # 4)
Two questions - have yo looked at the "connect to" in the start menu does it show a line that says "show all network connections" my network problem was after i looked at all network connections i found one was disabled so none of the other would work
after i manually enabled it all was fine - now anytime i turn it on it auto enables the network on that computer (I use wireless Dlink) which also has to be turned on each time
don't know if this will help but its the only shot i got LOL
#6. "RE: My Network's Not a Network" In response to dbahn (Reply # 2) Fri Nov-12-04 07:59 AM by jbmcmillan
Turn off the xp firewall it is redundant.You have to set up exceptions in the XP firewall anyway to let the others see it.EDIT:Have you set the other comps ip's as trusted in ZA?
Don't know about ZA but in Norton you have to let it know that the other PCs/Laptop are 'trusted'. I believe that Norton 'sees' other networked PCs as potential threats unless you identify them to it. This may be the same principle with ZA?
Andy.
Putting water in an empty gin bottle, doesn't make it gin.
The XP firewall is now off, but that didn't fix the problem.
I've set the ZA firewall to low in the trusted zone category (still high in internet zone), but the problem seems to be that the path from computer to computer is not shown. The host computer doesn't show on either of the remote computers and vice versa.
The trusted zone settings show on the GATEWAY computer shows: PPP 0.0.0.0/0.0.0.0 Adapter Subnet Internet Zone REaltek 8139 192.168.1.102/255.255.255.0 Adapter Subnet Internet
I presume that those are for the internet connections, which work fine.
Does that mean that all I have to do is add the IP's for each computer to the other computer's ZA settings? If so how do I do that?
... and then I just need a tip on specifically how to find the IP address for each computer. I've looked for it and would probably find it eventually, but if it's something you recall how to do, please tell me. Any saved step at this point is big benefit, as I seem to have gone around in quite a few circles already
And just out of curiosity. Does everyone setting up network have to do this manually, or did I goof up something on the set up process? All of the technique descriptions make it sound so much simpler than it has been.
You don't need to put the actual address of of the individual computer into ZA, just the address that the router assigns it. I haven't seen where you have gone into the router configuration. Have you? Go to "status" and try releasing and renewing the DHCP. Also look at the DHCP Client table. I've also found it sometimes necessary to hit the "apply" button in the router setup, even though nothing was added or changed in the setup.
I haven't done that, and will as soon as I get home to the computer. I presume I find "status" on the ZA menu (as opposed to something on the router software)?
In ZA open the firewall tab then add> Ip Range, put that as Trusted include your Router IP through the last IP range of your network EG.. 192.168.1.0-192.168.1.105 That should cover all of them. They change if you boot the computers at different times. I always use the O at the end of the router IP.
When I type "IPCONFIG" into the run command, the black screen appears then disappears, so I can't find the IP addresses that way. (This happens on both the host computer using XP and also on the Gateway pc using W98) I haven't been able to try it on the laptop yet.
#20. "RE: My Network's Not a Network" In response to Maggie (Reply # 19) Fri Nov-12-04 10:03 PM by dbahn
I found the IP address of each of the three computers and entered all three of them into the trusted zone of each computer on ZA. On rebooting now, the host computer (DELL using XP) doesn't get past the "loading personal settings" phase of the log on. The Gateway booted OK, and I haven't done the laptop yet, but will do so shortly.
I still am unable to share anything on the network, however.
Edit ON the third try the host computer booted OK, so that may not be a problem.
Now that I have the IP addresses entered into all ZA options on all of the computers, shouldn't each computer see all of the others when I click on the Network Places or Network Neighborhood icons on each computer?
Is there an essential step where I need to log on to the host computer as an administrator to set everything up? I don't think I've done that step anywhere in the process.
I guess I'll have to take a stab at that, although frankly I don't think I'm knowledgeable enough to do it successfully. I keep going around in circles. It's stuff like this that drives me crazy, from the links you gave me:
"Even if it tells you to do it, don't run Windows XP's Network Setup Wizard on the other networked computers. You want to make the Windows XP computer conform to the existing network. The Wizard wants to make the rest of the network conform to XP."
How does a casual user like myself ever know this early enough? It's all of these little steps and where to find the correct options that seem so simple to experienced computer users but make it miserable for an inexperienced user that drive me nuts. And sometimes it seems like the help menus are designed to drive me nuttier. End of rant. I'll try again and post back tomorrow sometime.
Thanks for the suggestions. I have a feeling I'm going to need some more of them.
You are using simple filesharing. Enable the Guest Account in XP.
Make sure you are using these protocols in each computer. Client for Microsoft Network Printer and Filesharing TCP/IP Same workgroup Go to the properties of tcp/ip into wins enable netbios over tcp/ip. Make sure you are in an Administrator Account in XP to configure the network Go to the network folder and check if your tcp/ip bindings are connected to printer and filesharing and client for microsoft network. If you are using the SP2 Firewall go to exceptions in the firewall and add printer and filesharing or put a check in front if it is listed. Reboot all the computers lots if you have to change things.
Thanks. That will be first on my list when I get to it in the morning.
One last question. What would happen if I deleted all of the network components? (For instance there are still some dial up adapters and duplicates of some of the TCP/IP items on the list in the configuration tab). I get the feeling that starting over might not be a bad option.
You should only have one each protocol. So get rid of duplicates. Or extras thaat aren't on every computer. Netbios over tcp/ip is in the properties of the TCP/IP protocol, advanced>under the wins tab.
As long as all the computers are connecting to the router I assume your obtaining the IP automatically ,good. Share something in each computer. Share a printer. Don't be concerned when it doesn't show up in Your Network.
XP might take forever to network compared to 98 and ME. Go to folder options in control panel and uncheck automatically search for files and network folders. Disable searching for scheduled tasks describes a bug in Windows 2000 Professional that might also exist in Windows XP. Disable searching for scheduled tasks by deleting this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\ CurrentVersion\Explorer\RemoteComputer\NameSpace\ {D6277990-4C6A-11CF-8D87-00AA0060F5BF}
#29. "RE: My Network's Not a Network" In response to Maggie (Reply # 28) Sun Nov-14-04 04:31 PM by dbahn
Thanks for sticking with me here, Maggie.
I am making progress. I now can share files between the host computer and the laptop, but not the Gateway PC, so I'm cleaning up the Gateway and will re try that.
I can't share the printers yet, so I'm going to try to install them one by one on the shared computers. Do the drivers for all printers need to be installed on all computers that would use them??
It turns out that NSW04 contains a Norton "personal firewall" that I didn't know was there (I bought the version without the firewall, or so I thought). Disabling that, in addition to XP's firewall and ZA may have been the key to getting this far, and I have a feeling I'll be able to sort out the other computer and the printers, at least sometime soon.
The printer drivers on the XP machine can be added in the printer share for the either machines. You only have to share the printers on the machines they are attached too. Don't try to put a share on the client machines. They will see that it is shared. The printers won't show up in My Network folder so you can't click to access them like you would for other share folders.
When you want to print just do it normally and the print properties will come up.
Firewalls are a bitch. Just go in and add the ip range for your network as trusted once you get it going. If you are using the SP2 firewall go to exceptions and enable printer and filesharing.
The LAPTOP now shares files with DELL04, the host computer, as well as GATEWAY.
The DELL04 is able to access files from the LAPTOP, but not the GATEWAY.
When trying to install the GATEWAY printer (which does print from the Gateway computer) on the LAPTOP, I get a message that the setup is unable to browse the network. I'm not sure what the path would be to manually add the printer.
I cannot print from the DELL04 to the GATEWAY printer either, although DELL04 will print to its own printer.
I keep shutting down firewalls and trying to connect the network, but it keeps preventing the GATEWAY from doing anything but being connected to the LAPTOP (but not the other way around, ie. when on the GATEWAY there is no access to the network).
I've confirmed that all three computers show the IP addresses of each computer in the trusted zones.
Did you look at this page? http://www.wown.com/articles_tutorials/wxpwin9x.html Go to the Gateway 98 machine and make sure all the bindings and protocols are installed properly. No network is showing at all on the 98 machine? Ping the ip addies of the other machines. If you get an error 65 usually means a firewall is blocking it After you can ping the other computer by IP address, ping the computer by computer name. To determine a computer's name, right-click My Computer on the desktop, click Properties, and the click the Computer Name tab. To ping a computer by name, type ping computername (where computername is the name of the remote computer), and then press ENTER. If you see successful replies from this command, you have basic connectivity and name resolution between the computers. After you have verified basic connectivity and that name resolution is working, you can troubleshoot connectivity for file and printer sharing. Or you could just forget that 98 machine
#33. "RE: My Network's Not a Network" In response to Maggie (Reply # 32) Sun Nov-14-04 09:37 PM by dbahn
I've thought about the W98 thing, but the photo printer and drivers are on that machine, and I don't think I can connect them to the host computer.
I can ping the laptop from the host computer by IP address but not by name, and cannot ping the GATEWAY by either IP address or by name. Should I be able to "ping myself", i.e. enter the IP address of the computer I'm on and get a reply. If so, that's not working either, as I get a time out for this computer by either IP address or by name.
I think I've done all of the steps from the link you gave me (some are only for XP Pro), but I'm still embarassed to say I'm lost on the "bindings and protocols" part, including the net bios over TCP/IP part. (Where do I find the "wins" tab?)
(EDIT): I can also successfully ping the host computer (DELL04) and the W98 computer (GATEWAY) from the laptop.
Edit (2); I can also ping the Gateway computer from the host if I shut off the GATEWAY's firewall.
Netbios over tcp/ip should be in the properties of TCP/IP under the wins configuration tab. When you get that on all the computers you can get there using the name. Nothing in there about XP Pro because you are using Home. So it is all simple filesharing. You can ping yourself by ping 127.0.0.1 if it doesn't work in the Gateway machine OOPS. You will only be able to share the printer drivers and the amount of pages to print. Look on the website for that printer it might not be able to share without special server software. Not all printers will share easily.
On the Gateway computer, the netbios over tcp/ip option is greyed out.
I was able to check that option on the host (DELL) computer, but then I could no longer connect to the internet. I had to use GoBack to revert in order to connect. (The other computers could connect during that time.)
This concept of "simple filesharing" is a misnomer for me .
Is it checked even though it is grayed out? Xp likes to use netbios over tcp/ip for networking it is the only reason I wanted you to do it. It is best that everything is set up the same on all the computers. I just don't know anything about networking 9X machines. I would have to look through the network folders in Control panel to find where the bindings and protocols live. All I have are those links. Those folders are really the most important places.
I guess it is using it then. I don't know if it is anything you can change. Hope it is using it. It seemed that your Gateway machine was the one that wasn't working so the other machines need to be left alone. They are seeing each other fine. You just have to dig in and find out why the 98 (Gateway) machine won't let the others in. It is still seeing the internet? The router is the DHCP Server? Still has Client for Microsoft, Printer and Filesharing and TCP/IP Open up your network neighborhood on the 98 machine and look at the Whole Network are they all listed?
#40. "RE: My Network's Not a Network" In response to Maggie (Reply # 39) Mon Nov-15-04 12:23 AM by dbahn
All of the settings you mention seem correct.
Now, I can connect from the Gateway and access files from the host computer. Interestingly enough, if I try to access files from the Laptop, it asks for a password. Neither the password used to logon to the laptop or the password to log onto this computer (the Gateway) is correct, and there is no password required to log on to the host computer. (Should there be, and would that make a difference).
I might be doing something right, finally, but I can't even figure out what that is!
EDIT: Another peculiarity. I tried to print an email on the Gateway using the host computer's printer. The printer makes the initial noise that printers make, but then it doesn't print.
How about the administrator password from XP. I had it happen once and that got me in. Hey you're making progress here!!! Make sure the spooler subsystem has permission in the firewall if there is a firewall on that computer. Lans need lots of permission on those software firewalls. So anything you are sharing needs to get through.
We are making progress, and I am very appreciative of your help.
I did just change the admin account to include a password (I've been meaning to do that anyway), so I'll keep plugging like this and maybe 6 or 7 reboots later it will work.
That spooler subsystem thing got me going to the glossary, though. How do I check that?
It will pop up in the firewall. Printer Spooler. It needs to be enabled on any machine that is going to print even if there is no printer attached to the machine but using the Lan.
Maybe!! I keep my software firewall in learning mode so all that stuff pops up when it is something new. Open up the firewall and look to see if it has asked and you denied it. You said it started to print though. Open the printer properties and see if there is page waiting to print. Or it got canceled but not deleted. I really hated windows 98. As soon as 2000 came out it was gone.
I think you're right in pointing to the W98 machine as the likely bottleneck. Of course it's also a 6 year old computer, although the printer is only about 3 years old.
My problem continues to be having the network find the Gateway printer, and from the laptop and Dell it just shows it as "offline", or if I try to print it says that "A communication error has occurred...blah...blah and to check the connections", which I've done several times.
It's a shame to say, but I almost get the feeling that if I continue going around in circles like this, it might just work one of these times. How's that for optimism?
#46. "RE: My Network's Not a Network" In response to Maggie (Reply # 45) Mon Nov-15-04 06:43 PM by dbahn
I think you're right in pointing to the W98 machine as the likely bottleneck. Of course it's also a 6 year old computer, although the printer is only about 3 years old.
My problem continues to be having the network find the Gateway printer, and from the laptop and Dell it just shows it as "offline", or if I try to print it says that "A communication error has occurred...blah...blah and to check the connections", which I've done several times.
It's a shame to say, but I almost get the feeling that if I continue going around in circles like this, it might just work one of these times. How's that for optimism?
EDIT: I don't know what this means. I entered all three IP addresses in the WINS configuration tab (instead of the automatic option) and on reboot got the message: "The system has detected a conflict for IP address 192.168.1.101 with the system having a hardware address 00:0C:41:C5:38:3A/ The interface has been disabled." (That IP address is for the host computer).
There is something you might not have tried. Put the printer on one of the other computers and see if it can be accessed. I have both my printers hooked to one machine. I used to have one hooked to a third machine but I ran out of room and needed to put a bed in the room,so I put the machine away. It is kind of a hassle because I only have 1 lpt port so I move the parallel cable to the other printer when I need the old Laser one. Both only use the Windows Default drivers. This would eliminate the printer as the network printer if it works.
OK. It's worth a try (although it sort of defeats the purpose a little bit).
BTW, when I got the error message on the Gateway, the laptop was also on and showed the same basic conflict message but with different hardware numbers (00:50:FC:CB:43:3E)
I've never put anything in the Wins. I only enable the netbios over tcp/ip if I'm networking my XP mchines. I leave lmhosts checked also. I wouldn't know what to do if I put the IP anything in there.
#50. "RE: My Network's Not a Network" In response to Maggie (Reply # 49) Mon Nov-15-04 09:09 PM by dbahn
You'd probably do what I did ----- change it right back to the way it was.
But I think my problem is still more than just a printer problem. I still can't find all of the computers on the network. I just tried to do that on the XP host machine ("View workgroup computers")and it pauses for about 15 or 20 seconds then flashes a message that Mshome is not accessible, that I might not have permission to access the network, to contact the administrator, and that the list of servers for this workgroup is unavaiable.
It still seems like there is some authentication missing somewhere in the setting of the network sharing, but I don't know how else to find it. I don't think contacting Dell is an option, because I don't think they support any of the network systems. I did contact Linksys just to be sure the router couldn't be the culprit, but they told me if the internet connection was working it wouldn't be the router, which sounds reasonable to me.
#51. "RE: My Network's Not a Network" In response to dbahn (Reply # 50) Mon Nov-15-04 11:48 PM by LilJoe
Dave,I don't know if this will help but I looked thru some old notes from when I had 5 98 machines networked and found this for an old Pentium Pro. Now all my units are xp so this is all I know. See the attached.
#55. "RE: My Network's Not a Network" In response to dbahn (Reply # 54) Tue Nov-16-04 02:24 AM by LilJoe
>I think I've got those same basic settings, LilJoe, with some >different IP addresses, but the same set up. > >Hey, how come I can read your handwriting but I can't read my >own? --------------------------------- Without me going back and rereading everything,have you installed Net Beui on the 98 unit? I suggest you remove all settings on the 98 unit-reboot and reinstall the settings.Give it a try. --------------------------------------------
Also type: http://192.168.1.1/ into the address bar of your default browser. Should take you to your router settings.
Right click Network Neighborhood-select Properties and click, Hard to remember on 98,in the area where to select protocols you should be able to select Net Beui.
I'm wondering why you keep calling the XP machine the host. I thought the Router was the DHCP Server. There are no host-client configurations for the machines. ipconfig /all what is the default gateway? It should be the Router IP.
>1. Set up a Linksys B router, connected to a cable modem. >2. Connected the DELL04, running XP Home (these capitals are the >names used for the connection wizard)to the router. >3. Connected my old GATEWAY (W98) to the router via ethernet cable. >4. Set up the LAPTOP (WMe) using a wireless connection.
Workgroup Same on all Guest Account enabled in XP Client for Microsoft Networks Printer and File Sharing TCP/IP
I thought it was a host because I thought that's how it had to be set up, but I now see how it's not, and never was. My problem arose when I bought a new computer, transitioned to XP, switched to broadband and set up a home network all at the same time, not really knowing what I'm doing in the first place. The attempt to set up file and printer sharing now is occurring several months later, and I don't remember much of the initial configuration. That's one of the reasons I wondered if I could just uninstall the whole works and start over again.
Is the default gateway that's listed in the properties the IP address of the router? Do I need to check that?
Make sure and point all the computers to the router. TCP/IP use Obtain an IP address automatically then the gateway will be the router. Yes if you have XP set up as Host then blow that and client computers away it is only good if you are using ICS and a crossover cables. Make sure the router is the DHCP Server. My Linksys WRT54G is 192.168.1.1 so all my stuff is naturally pointed to it by using automatic in TCP/IP
I'm on the laptop here same ip addies in the desktop
Good!! Then you aren't using ICS If you use the network wizard- attached to the router Tell the Wizard that the computers connect to the Internet "through a residential gateway" (router). Other options, like "directly to the Internet" or "through a network hub" will block file and printer sharing. Rightclick and share some folders and printers. Follow all the rules in the other threads. Reboot.
Actually, that's exactly how I've been doing it for the past 6 to 10 reboots. Initially I had incorrectly checked the option to connect through a hub, but then realized that was incorrect. Doesn't that get overwritten by the new entries in the network wizard?
I never used the wizard. As long as all your settings are OK and the bindings are correct you should be good to go. I've seen the wizard put a bridge on the wireless card when it was done wrong.
Well, maybe that's my problem then. I've tried to set it up manually and also tried the wizard (mulitple times each). I think I have the firewall situation correct, but right now the only "networking" I can do (besides internet sharing) is share files from the Gateway when I'm on the laptop.
I'd love to just start all over again with a clean slate, but not sure if that can be done. I might be able to get someone to physically walk me through all of these steps, but frankly I'm not sure what they would do other than what you've already suggested.
Here is a clear explanation for 98 http://www.windows-help.net/windows98/troub-331.shtml points you to the bindings tab In XP go to the network folder click on advanced(toolbar) then advanced settings Not sure in ME but it should be in one of those places. You know how to find the protocols and workgroup.
Well, Maggie, LilJoe (and anyone else), I'm really ready to start all over again, despite your valiant efforts to help save me, which I greatly appreciate. I've worked and re-worked all of these options too many times to think that doing it one more time is going to fix anything.
So my new questions are:
1. Can I "uninstall" all of the network settings on all of the computers that I've tried at this point? Do I need to change some registry entries to really get back to square one? Whatever the conflict is does not seem to be in the readily available settings options.
2. I set up connection sharing on the router many months ago. Do I need to go back that far and see if there is some conflict in settings (such as a password) that needs to be addressed? Or is even worrying about the router illogical, since the internet sharing is working just fine?
3. If I can start over, should I first work with the laptop using WMe, then add the W98 computer only if the first one works?
4. Do you have any other suggestions?
PS/ If this thread gets much longer, I may take the liberty of continuing it as a new post, with a reference to this one. OK?
Jeez I don't know what to say. The only way I figured it out was to be able to see the big picture. Little bits and pieces never worked for me in the past. This might be what you have to do. To me it is a matter of bindings and network protocols and workgroups, all pointing to each other. Not using ICS with a router. When I first started I didn't have anyone to ask so I made a networking page and copied all pertinent info on there. That way I wasn't bouncing around to different sites picking up bits here and there. My page only makes sense to me.
Well then, let me explore the bindings one more time. Your post suggests that I;
"In XP go to the network folder click on advanced(toolbar) then advanced settings."
I'm going to control panel>network connections>which when I double click opens up an icon for the Home network. I right click to the "properties" option, which opens up three tabs - General, Authentication, and Advanced. The Advanced tab of this only contains an option for the Windows firewall. The general tab has four items listed, all checked. The are Client for Microsoft Networks, File and Printer Sharing for MS networks, QOs packet scheduler, and Internet Protocol (TCP/IP). Only Client and Protocol highlight the "Properties" box, but in neither of those is there a bindings option, or any other option that looks like it would help. The Authentication tab has checked to enable IEEE 802.1x, etc.
Am I looking in the wrong place for the Network Folder? It's possible that I still haven't resolved the bindings issue.
>Well then, let me explore the bindings one more time. Your >post suggests that I; > >"In XP go to the network folder click on advanced(toolbar) >then advanced settings." > >I'm going to control panel>network connections>which when I >double click opens up an icon for the Home network. I right >click to the "properties" option, which opens up three tabs - >General, Authentication, and Advanced. The Advanced tab of >this only contains an option for the Windows firewall. The >general tab has four items listed, all checked. The are >Client for Microsoft Networks, File and Printer Sharing for MS >networks, QOs packet scheduler, and Internet Protocol >(TCP/IP). Only Client and Protocol highlight the "Properties" >box, but in neither of those is there a bindings option, or >any other option that looks like it would help. >The Authentication tab has checked to enable IEEE 802.1
Here is where the bindings are in the network connections folder
I think the problem was caused by a 3rd firewall that I didn't know was even there. This computer came with a 90 day trial of Norton Products, which I guess included a firewall that I thought I had long ago disabled. When I bought this computer I immediately purchased and installed NSW2004 specifically without the firewall, knowing that I would be using ZA. I think though, that every time I rebooted, the firewall came back on and I didn't realize it. I only figured it out by pinging amongst the computers and then turning the firewalls off and still finding that this computer could not be pinged successfully. It only then occurred to me that I had a Norton firewall at one point, which I found and (hopefully) now permanently disabled by using the configuration option. I must have just checked the "turn off" button before. One run of setting up the network and voila!, it works.
I also just found the bindings options you posted above.
Anyway, the network IS a network now, thanks to you. I even have the photo printer working on the network on the W98 computer, and everything else seems to be connected as well. I could not have begun to get to that point without all of the advice. Many, many thanks (and to LilJoe and the others). I certainly do appreciate your perserverance in all of this. It's a lot of work, but a huge relief to me.
