OK, with both IPX/SPX and TCP/IP it works. I don't know if it's important, but it's a little different than with IPX/SPX alone. When I click on Network Neighborhood On systems 1 and 2, both systems 1 and 2 show up. I have to click on Entire Network and then Network to see system #3. And it's vice versa from system #3. I see System #3 when I click on Network Neighborhood and have to click on Entire Network and then Network to see systems 1 and 2. For what it;s worth systems 1 and 2 are Win98SE and system 3 is Win98FE.

0

I'm glad to see you're making progress.

0

GIS_tech I can't use Netbui, I need to use TCP/IP for the shutdown program that I would like to run. Pinging and system from any other system get Unknown Host and no packets are sent. I am using straight through CAT5 cables. The LAN is working fine with IPX/SPX and with both IPX/SPX and TPC/IP.

0

Kevin... Well I don't think running both is going to help me out. I need to get the LAN running on TPC/IP alone so I can use the shutdown program.

0

If someone knows a shutdown program that doesn't require TPC/IP that would be great.

0

But if i had my druthers, I'd druther get TPC/IP working. :-)

0

ipx is a protocol for compatiblity with novell networking, it has it's own version of netbuie, which is why you can "see" shares with it. with only tcp/ip you will also have to have netbuie and netbios over tcp/ip installed and enabled to "see" shares on win9x boxes. with static ip addressing and all on the same subnet, ie; 192.168.1.x and a common subnet mask, ie; 255.255.255.0 you should be able to ping each box on the subnet. the fact that is does not indicates an error either with the nics, the hub or win9x and it's flavor of tcp/ip. pinging the local host, ie; 127.0.0.1 with good result usually indicates a good install of tcp/ip on that box, so i'd look at changing out the hub. just double check the ip's, the subnet mask, and workgroup. just to make sure you didn't type-o or such.

0

Hi Rick In the TPC/IP properties page/ Netbios tab it has a check by 'I want to use Netbios ...', but it's greyed out. Is that ok? I'll go add Netbeui on all the systems and post back. On another note. I skipped right over GIS_tech's request that I do an ipconfig. Sorry about that. I did it and here's what I got. System #2 looks kinda funny. System #1 0 Ethernet adapter IP address 0,0,0,0 subnet mask 0,0,0,0 Default Gateway: 1 Ethernet adapter IP address 192,168,1,1 subnet mask 255,255,255,0 Default Gateway: System #2 0 Ethernet adapter IP address 67,227,25,23 subnet mask 255,0,0,0 Default Gateway: 67,227,25,23 1 Ethernet adapter IP address 192,168,1,2 subnet mask 255,255,255,0 Default Gateway: System #3 0 Ethernet adapter IP address 0,0,0,0 subnet mask 0,0,0,0 Default Gateway: 1 Ethernet adapter IP address 192,168,1,3 subnet mask 255,255,255,0 Default Gateway: I'll be back in a few.

0

Ok, with Netbeui added everyone sees everyone else. I'll have to try the shutdown program to see if it works. I'll post back, one way or the other. Thanks very much Rick, Kevin and GIS_tech !!!

0

Folks you all missed the point of the exercise. It was to get him on IP only. The question wasn't to get him networked or deal with authenication or shares. He already had done that. By adding protocols you muddied the water. This did nothing to solve the issue of being on ip only. Adding a nonrouting protocol is only useful to determine if you have connectivity issues. It is not a solution for the lack of IP working. Netware does not have its "own" kind of netbeui [nor does MS have its kind of ipx/spx] and you will see the same shares running only IPX as you would if you were running IP only. Netbeui, not to be confused with Netbios which both ipx and ip encapsulate for transport, would also show the same shares if it was the only protocol. Getting back to the main issue of creating a IP only network [and everyone should be able to do this] would be to start with your ip properties. You have a ip address and subnet mask on each which is fine. Leave gateway, dns and wins entries blank. Reboot all pcs and see if you can ping by ip address. Ping by lookback tests the binding to the nic and you have already successfully conpleted that. What was not completed was ping between machines. I would agree the ping issue is firewall related. After all the firewall doesn't block ipx. No firewall on each pc or configure the firewall to have a trusted zone of 192.168.1.x which is your ip range. This should take care of the ping unsuccessful issue. Post back when you can ping sucessfully between all machines. After that you should be able to remove all other protocols without issue.

0

Thanks for your input Wanderer. I'm working on getting the shutdown program going and having some problems. However the program is recognizing all 3 systems. I think it `might' work if I can fix this unrelated problem. I'll post again when I learn anything.

0

I am not having any luck with the shutdown program. I'm gonna put it aside for a while. Wanderer, The Gateway and Wins panels are blank. But notice in Response #14, #2 shows a Gateway. I shut down everything except Explorer and Systray on all 3 systems. I did pings to the IP addresses of each from each. 1 gets timeouts from 2 and 3 2 gets timeouts from 1 but 3 works fine ??? 3 gets timeouts from 1 and 2

0

I'm gonna call it a day. I'll check back in the morning.

0

Have you ever worked with lmhosts or host files on these systems? Your "no gateway entry" but showing a gateway would lead me to think there are configuration files like lmhosts or host files coming into play. Looking at your system ipconfig posts you are right #2 looks like the modem was dialed into the internet? As a suggestion I would disable the modems on all three machines in Device manager. You can always turn them back on later. Just want to make sure the systems aren't getting confusued due to the ras port/modem dialin. One of the issues that come up with multiple protocols is binding order. You really have no control in 9x but in NT/W2K/XP you can sort the binding order. Of course if you are only IP this is not a issue. As a last resort you can make a lmhosts file by editing and saving the lmhosts.sam [sample file]. By putting in the machine name and ip address in the lmhosts file you hard code the ip to machine name associations. This file is read into memory at each boot. You would put the same file on all three machines.

0

OK, Thanks very much Wanderer! I `did' enter the stuff in the hosts.sam file at one point to see if that would help. I'm going to do what you suggest and I'll check back when I'm done.

0

Ok Wanderer, mucho progress thanks to you! I did the following: Disabled the modem Dis-associated the dialup adapter from TCP/IP I removed an entry in the hosts.sam file '127,0,0,1 Local host' At that point I was able to `sometimes' ping every system from every other system and `sometimes' they would even show up in Network Neighborhood. System #2 seemed to fail the most and I finally discovered that if I powered it down, systems 1 and 3 worked fine. I have tried restoring a couple of backups to sys #2 but it doesn't help. I'm going to try another NIC and if that doesn't help I will probably try a format and clean install. I will post back when I learn anything. Thanks very much Wanderer, you are my hero. :-)

0

Here's what happened Wanderer. I replaced the NIC and it didn't help. I formatted and did a clean install of system #2. With a minimum system running now the Lan is working great on all systems using TCP/IP. I have re-eneabled the modem and added TCP/IP back to the dialup adapter. The only small problem I have left is that I have to shutdown ZoneAlarm to use the LAN. If you have a fix for that off the top of your head, that would be nice. But I'll start digging for a solution anyway. I sure do want to thank you a whole bunch for helping me out. You sure do know your stuff!

0

Something interesting happened. To solve the problem of ZoneAlarm(free) interferring with the LAN, I decided to install ZoneAlarm Pro. That was a mistake because system #2 started acting the same as it did before I did the clean install. Luckily uninstalling ZoneAlarm restored the system to full functionality. Anyway, it looks to me like ZoneAlarm was part of the problem.

0

exactly right. In ZA you can create a "trusted zone" you put your ip range [198.168.x.x] and you do this on each pcs za. You can do this with pro also. You want to put back the hosts entry 127.0.0.1 local host. This is normal. Also you would have to save the hosts.sam file as hosts [no extension] for the system to read it. Looks like ZA and perhaps a faulty install of 95 on #3 was the issue. Just configure ZA and you are done.

0

Ok great Wanderer, I'll do those things. And a great big thanks again!!!!!, for bailing me out.

0