Windows Forum

Ask something
Discussion Locked

No ping reply

0 helpful
31 replies

by chirila

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I tried to put a Pentium I computer, with Ali Aladin IV+ (M1531&M1534) mainboard in a network.

The network card is ok, drivers installed, TCP/IP protocol installed, but I can't see the other computers in my network. I pinged myself and it worked,but I can't get a reply from another computer. I put the IP of another computer and I got the warning message that are 2 computers with the same IP.

I tried 'Find computer' from another computer, it was found but not accesible.

I tried different Network cards (ISA&PCI), different SO(Win95&Win98), I mapped IRQ's from BIOS (3,9,11...). Someone told me to enable USB and Plug'nplay from BIOS, i did it but no luck. He also told me to install the mainboard drivers, I did (none of this driversare related to IRQ, just IDE).

Can you help?

Thanks,
Daniel Chirila

31 replies

by walter_loh

Some where some how , you pc have lock the ip for it own used , i have face this proble with most of the acer (P1) pc , try reformat and do a fresh install .

I hope this help !!

Walter

by chirila

I already tried it, installed Windows w. the NIC or installed Windows and then the NIC. Thanks anyway.

by walter_loh

Some where some how , you pc have lock the ip for it own used , i have face this proble with most of the acer (P1) pc , try reformat and do a fresh install .

I hope this help !!

Walter

by saihib

We need a little more information. What kind of network is this? Peer-to Peer? Client/Server? Or something else? Are you running DHCP or static IP? Is your default gateway correctly configured? What OS are your server/s running? A little more info please.

by chirila

It's a peer-to-peer network. Just the computer in case and another one with Win98. I tried with a computer with Win2k and I have the same problem. What to check on the motherboard?

by borg7of9

Hi there, first of all you are focusing on hardware, when in fact it is most likely a config issue. So to be sure, step one, make sure that the card is ok. Right click on my computer, go to properties, device manager and make sure your network card has no yellow or red flags on it. If not then your card is ok. (If not correct this, by re-installing card and drivers on good irq, and yes make sure your bios in Pnp if possible)

Next,I dont know your network, so lets do a little test. Go to control panel>networks and lets make sure you have all the parts needed installed. Make sure you have microsoftnetworking installed, make sure you have the tcp/ip protocol installed, and also install netbeui protocol (you can always remove it later if you wish) Also enable file sharing on that computer. (printers if you wish too) NOw go to identification tab, and make sure that you have a common name for workgroup. For example, make sure all systems you want to commiunicate with have a name such as ADMIN. You will have to re-boot your system (and any system you renamed), and now see if you can see other systems (In network neighbourhood) If you can, it may be through netbeui and not tcp, but at least you know all physical comppnents are ok, andbasic set up is ok. Also at this point your internakl network can run. If after all this you still have a problem, email me or post a comment
Hope this helps

by curacao_dejavu

Need your email adress to send you a document how to solve this.
It's a software/os issue.

In the meantime. download and install the latest drivers.
Select file and printersharing and install the netbeui and ipx protocols also.

ake sure the subnetmask and the workgroup are the same. (no gateway needed in a peer to peer workgroup.)

Till later.

Leopold

by curacao_dejavu

When you attempt to connect a computer to itself using its Universal Naming Convention (UNC) name, you may receive the following error message:

Windows 98:
\\ is not accessible. Unknown Error 2114.
-OR-
Windows 95:
\\ is not accessible. An extended error has occurred.

CAUSE
This behavior can occur if the Microsoft Client for Microsoft Networks is installed without file and printer sharing.

RESOLUTION
To resolve this behavior, install file and printer sharing for Microsoft Networks. To do so, follow these steps:

Click Start, point to Settings, and then click Control Panel.

Double-click Network.

Click Add, click Service, and then click Add.

Click "File and printer sharing for Microsoft Networks," and then click OK.

Click OK, and then restart your computer when you are prompted to do so.

It could also mean that if file and printersharing is already installed, that is became corrupted. You need then to install it back again. amke sure you use a good cd and let the program replace the files.

Later.

by chirila

Already did all of this. There's no IRQ conflict, I tried netbeui and ipx. The cable is ok (i tried coaxial and crossover utp). I did all the testings with only one computer which is working very fine in a larger work. That computer has Win98, WinXP, Win2k. In the network properties in WinXP and Win2k I see is sending packets to the computer in problem but no reply.
I'll write down the settings on both computers:

Good computer:
SO: WinXp, Win2K, Win98 (different partitions)
IP: 192.168.0.1, Subnet:255.255.255.0
Name: Server, Workgroup: 35Net
No gateway, no dns, no dhcp, no wins
NIC: Realtek 8029AS PCI, IRQ 11, no conflicts

Bad computer:
SO: Win95 or Win98
IP: 192.168.0.2 subnet 255.255.255.0
Name: Stupid, Workgroup: 35Net
No gateway, no dns, no dhcp, no wins
NIC: Realtek 8029AS PCI, IRQ 11, no conflicts or D-link 250 ISA (NE2000 compatible), IRQ (3 or 9 or 11), no conflicts

by maz1980

Try using another IP address. If more than one computer using same address, all will be disabled. Also try using most recent driver and enabling PNP on BIOS setting.

by drew_lgca

How are these PC connected ? Hub ? Can the good PC ping the bad PC ??
Do you have anything shared on the good PC ? Share a Drive or folder. and then see if you can see it. Try ping 127.0.0.1 this is the internal address for the network card.

by xanderoth

Guess what. Realtek network cards are the horror of the NIC industry. Replace them. Believe it or not, your problem is related to your Network Card. If you have tried other network cards, then there is a problem with all of your network cards, or the ports you plugged them into. Dont just replace the card, remove the adapter and all protocols BEFORE shutting down to replace them. If you are replacing them with other Realteks, throw them away! (HA! sorry but I hate REALTEK!) Make sure the adapter installs correctly without ANY errors. If you get errors...
FDisk, Format and Forget it. Then try again.

by asjwm2

Well.....
Perhaps it has to do with dynamically assigned IP addresses. Perhaps when you ping it dynamically assigns the address of the pinger to the pingee. I think the computer in question must be configured to ping a static rather than a dynamic IP address, but you seem to be quite knowledgable about it, and I am not very.
But, I guess you could check start, settings, Ctrl Panel, and then do a few more clicks to find out if a network connection has the "server automatically assigns IPaddress."A bit out of my league, I'm afraid.
Good Luck !!!!!!

by rogerndgreen

Dan
You haven't mentioned what client you have bound the IP protocol to.
Obviously you have got one PC that is fine, so we'll check the other one.
Have you installed the Client for MS networks (network neighbourhood, Properties)?
What is your primary logon? Have you configured the MS client to logon to domain (which you obviously don't want)?
Now look at the TCP/IP properties. Check the bindings tab. Have you selected the MS client?
Now let's look at the Network card properties. Have you got frame type and link speed settings on the card? (network neighbourhood, properties, select adapter, properties, Advanced) Are they set to Auto-detect? If they are, turn them off, and start by using the following settings; 10meg Halfduplex,10meg Full duplex, 100meg half duplex, 100meg full duplex. The settings on the card for BOTH PCs must be the same, and I do NOT trust auto-detect to work at all times. You should find that 10meg HD is fine for simple use (in a 2-PC setup).
Incidentally, if you have used co-ax cable, then you must be using 10meg cards, but did you connect a terminator to bothe ends of the co-ax?
Also are you sure that the UTP cable is in fact a x-over one? Check with someone else, if you're not sure.
Sooryif some of this sounds patronising, but I don't know how much experience you have in networking.

Roger

by nadhir

from the way you configure your pcs, guess you should start hunting to networking books before jumping to creating your own "LAN".

so to speak,you need to configure your IP in the same family. eg
1st pc ip is 10.1.1.1
2nd pc ip is 10.1.1.2
3rdand so on 10.1.1.XXX
both on the same subnet mask

this will allow you to ping each other.By your explaination you are going to peer-to-peer network.so connect your RJ45 cable to the pc.

It's ridiculous of you giving 2 pcs with the same ip.therational of you giving an ip to a pc to create a unique id in a family of other ids.

by chirila

Are you for REAL or am I only dreaming? When I first setup a LAN u probably started to learn Solitaire.
Please read all the words in the question all the comments! As u probably don't know 192.168.x.x is not a public ip address and the pcs in question have the following ip addresses: 192.168.0.1, respectively 192.168.0.2. So please go and answer to questions on the http://www.solitaire-for-beginners.com.

This discussion is closed to new replies.