PDA

View Full Version : 98 can't peer to peer (All)


n8diggity
03-03-2003, 07:41 AM
Ok,
I am using a crossover cable to connect a 98 to a W2K machine. I know the cable is good (it works when connecting an XP machine directly to a W2K machine) The activity lights show connectivity on both the 98 and w2k machines.

I have tried both assigning static ip addresses and using the autodetection option (obviously not at the same time). Autodetection assigns addresses on the same network segment using the same subnet mask, but the machines don't see each other. Same with statically assigned ips. They can't even ping eachother!

The protocols being used look good to me : TCP/IP, Client for MS Networks, Family logon, file and printer sharing.

I have 2 nics in the 98 machine, both work when connecting to the internet.

Any ideas, wise WinGuides?

Ranger32746
03-04-2003, 04:04 AM
All of the computers should have the same setting for "Workgroup."
All computer should have the same protocol, clients, and services installed (e.g. TCP/IP, File and Printer Sharing for Microsoft Networks, and Client for Microsoft Networks). Note that these protocols you have slightly different names in different versions of Windows. If you're using Internet Connection Sharing, the NetBEUI protocol should not be used; otherwise, you may need NetBEUI in order to access other computers on your network.
No two computers should have the same computer name.
Some computer names supported by Windows 2000 and Windows XP are not compatible with Windows 9x/Me, such as names with spaces. Simplify all your computer names and try again.

Alan
Webmaster
http://24hourcertification.us

homeflash
03-04-2003, 01:42 PM
First of all, I don't agree on All of the computer should the same setting for Workgroup.

Network computers do not have to be in the same workgroup as long as they are using TCP/IP with the same subnet mask.

I think that the case you are not able to ping is because

1. the network card was not properly inserted.
You may want to open the case and unplug and plug back in.

2. Remove all the driver information, and reinstall protocol.

It happened to me also. When I go to my network setting. It said "The network is not complete". That gave me an idea that it wasn't installed properly eventhough I can go to internet. (I wasn't able to ping or connect to pc)

In my suggestion, remove all the procotol, driver info first, and reinstall. The rest should stay similar to your other computer. like the internal ip and subnet mask.



*** Sometimes Helping is a way of Learning! ***

n8diggity
03-10-2003, 04:30 PM
well, I couldn't get it to work... everything looked good to me... so, I updated to W2K and the problem is solved. Thanks for all the input.