28 replies
by timwalsh
Multiple protocols are probably part of your problem. You need TCP/IP if you are going to access the Internet. NetBEUI comes in handy in a Win9X network. You don't need IPX/SPX unless you are running Novell or a specific application requires it.
I'm assuming you are pinging IP addresses and not computer names. What type of replies are you receiving - "destination host unknown" or "request timed out"? Will none of the computers successfully ping the others or does only one computer have this problem?
If you are able to share files and printers, it isn't a connectivity issue. Therefore, moving NICs and reinstalling frivers won/t resolve your problem. Remove IPX/SPX and try pinging.
by meafixall
by meafixall
by meafixall
by meafixall
by meafixall
by greybeard770
Sparta makes a very good point. More protocols is not always better. Start out simple. If you can share files by computer name, you don't see the whole name resolution process. It sounds like you are talking about Internet Connection Sharing. Try letting the other computers get their IP address from the modem sharing computer.
And first chance you get, get broadband and a NAT router.
by acattr
by meafixall
by meafixall
by meafixall
by meafixall
by meafixall
by mikemunnelly
Your network has to many protocols. The network is using either the IPX or NetBeui to share the files and printers. Right now, the TCP/IP is not working at all. Remove the IPX and Netbuei from all machines. Make sure that all machines have microsoft client services, TCP/IP as a protocol, and the ethernet card. Reboot each system in the network one at a time. When you have rebooted, check to make sure that the tab marked "default protocol" in the network configuration is checked (or grayedout, and checked). To simplify things, make sure the workgroup names are the same for all machines and that each machine has a distinct computer name.
The other problems you may be having could be related to the winsock.dll or winsck32.dll drivers you are using. Sometimes the "stack" gets corrupted, and the files need to be overwritten. Pulling off the driver and then reinstalling it, saying yes to all the "are you sure you wish to overwrite these files" will fix any common stack problems. I have seen cases where all the files have to be deleted and then the TCP/IP networking components reinstalled.
by acattr
by 2nickles
by meafixall
by acattr
by meafixall
by mbatty
SOunds like you have tried most of the usual fixes. Tme to go back to basics. Before connecting to the Internet you need to get to a stage where all your machines on you rhome netowrk can talk to each other. As stated in previous answers, Firewall software will junk ping packets as default, so switch it off on all machines.
I assume that you are using 192.168.0.xx for the LAN cards on all machines. I cannot tell if you are using a DHCP server, so for testing purposes configure a static address in each machine. i.e make Internet PC 192.168.0.1, PC(A) 192.168.0.2, etc, using the TCP/IP properties in network neighbourhood for the LAN adapter.
This should give you basic IP connectivity on your LAN and a ping to the IP addrees should work. IPCONFIG is a good command for looking at the running IP settings,also NETSTAT -RN will show you the IP routing table in your machine. Try these out to debug your problem.
by meafixall
by 2nickles
Now this is a fun one. All the previous answers should have isolated the problem, but as of yet haven?t. Your last comment you said that you were going to get a new NIC, from what I seen I don?t think that you NIC is bad, but there might be a compatibility issue. You have three computers that can all see each other through the NETBEUI protocol, but cannot ping via TCP/IP, correct?
Lets get some more information:
PC(A) ? What operating system; what type of NIC; IP Address 192.168.0.1PC(B) ? What operating system; what type of NIC; IP Address 192.168.0.2
PC(C) ? What operating system; what type of NIC; IP Address 192.168.0.3
When loading the drivers, are you using the drivers provided by the NIC manufacturer or the Windowsprovided drivers?
If you do not already have one pickup a crossover cable for testing purposes. Make sure it is a crossover (pin 1 to pin 3, pin 2 to pin 6) cable and not a rollover cable (pins 1-8, 2-7, 3-6, 4-5).
With this cable you can hook up two computers from your network, back to back. Thus eliminating several variables, the switch, the other computer, the patch cables. I really don?t think that this is a physical layer problem, but it will be easier to isolate with only two computers in the scenario.
by meafixall
by jennchye
Did you check if the address resolution protocol, ARP is able to resolve your IP address to the MAC address of your NIC?
Do a arp -a on any machine after a ping test. The resolved MAC address shown have to be the same as the destination machine'sNIC.
by meafixall
After pinging and getting the message: Request timed out? I then did the arp/a and received the following text on one machine
Interface 192.168.0.2 on Interface 0x1000002
Internet address physical address type
192.168.0.1 00-04-5a-62-82-02 Dynamic
On the other computer
Interface 192.168.0.1 on Interface 0x2000003
Internet address physical address type
192.168.0.2 00-04-5a-72-3f-6a Dynamic
Now what doesthis tell you about my system?
by wlbowers
Dump everything on the networking except tcp/ip. Now go buy a SMC7004ABR Router Gateway. www.smc.com
The Barricade? is an ideal all-in-one networking solution for home and small business users. This platform independent multi-functional broadbandrouter combines a 4-port 10/100 Mbps dual-speed switch, a built-in print server, an RS232 COM port for fail-over dial-up or modem connections, an Internet firewall for security against hackers and other unauthorized users, and simultaneous Internet access for up to 253 users.
The RS232 port is the kicker. It allows you to network connect to a desktop modem or IDSN.
Good Luck Lee
by meafixall
by meafixall
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending