Solved

binding and pinging W95

Posted on 1998-08-13
8
145 Views
Last Modified: 2013-12-16
null
0
Comment
Question by:dovedove
  • 5
  • 2
8 Comments
 
LVL 1

Author Comment

by:dovedove
ID: 1757619
Please help!!
0
 
LVL 1

Expert Comment

by:fmismetti
ID: 1757620
dovedove:
I understood that you are unable to ping Machine A from Machine B and vice-versa. If this is true your TCP/IP setup is totally wrong, at least for the network cards. Do you have TCP/IP installed for the net cards? If yes, what are the settings?  Which IP you are using for the network card (look in Control Panel, Network, TCP/IP->network adapter)?
Need more details to help you.


0
 
LVL 2

Expert Comment

by:czamudio
ID: 1757621
in the network control panel, press add button
then select protocol
then in the left panel select microsoft, then select tcpip

this procedure must install and bind the tcp/ip to your network card.

and in my personal experience, it's better to use linux + IP Masquerading.

other solution wil be too expensive.
0
 
LVL 1

Author Comment

by:dovedove
ID: 1757622
Thankyou for the answer czamudio, however I have already elected TCP/IP etc......
Also I think that linux is a separate OS. If so we do not have linux.
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 1

Author Comment

by:dovedove
ID: 1757623
Thankyou for the answer czamudio, however I have already elected TCP/IP etc......
Also I think that linux is a separate OS. If so we do not have linux.
0
 
LVL 1

Author Comment

by:dovedove
ID: 1757624
Thankyou for the answer czamudio, however I have already elected TCP/IP etc......
Also I think that linux is a separate OS. If so we do not have linux.
0
 
LVL 1

Accepted Solution

by:
fmismetti earned 50 total points
ID: 1757625
Let's see if I can help you. You have two equipments, one with network adapter (let's call MachineA) only and the other with net adapter and modem (MachineB).

Configuring the MachineA

Open Control Panel, NetWork, you need to have in the configuration tab: Client for microsoft networks (service), Your network card (adapter), Netbeui (protocol), TCP/IP (protocol), File and Printing sharing for MS networks (service).
If you don't have all these item, add. Click on TCP/IP protocol, properties and make the configuration: on tab TCP/IP address, put specify and IP address and enter a public IP address, like "10.1.1.1", netmask "255.0.0.0". Disable DNS, WINS and remove any gateway at this time; on tab bindings, turn on both items.

Reboot the machine. Open a DOS box and enter the following command:

PING 10.1.1.1

You are pinging the local machine but using the net card. You need to receive an answer similar to:

#begin of screen capture
Pinging 10.1.1.1 with 32 bytes of data:

Reply from 10.1.1.1: bytes=32 time<10ms TTL=128
Reply from 10.1.1.1: bytes=32 time<10ms TTL=128
Reply from 10.1.1.1: bytes=32 time<10ms TTL=128
Reply from 10.1.1.1: bytes=32 time<10ms TTL=128

Ping statistics for 10.1.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum =  0ms, Average =  0ms
#end of screen capture

If you receive an error, something is wrong. Don't proceed and review the settings.

Configuring the MachineB

Configuring MachineB is almost the same. But MachineB has a modem, then in the control panel you have NetWork Card Adapter and DialUp Adapter. Then you need to have the following protocols: NetWorkCard->TCP/IP, NetWorkCard->Netbeui, DialUpAdapter->TCP/IP. If no, add this protocols.

Click on NetWorkCard->TCP/IP, Properties, and repeat the configuration, but use IP "10.1.1.2", same netmask. Note that in
DialUpAdapter->TCP/IP you need to leave as "Obtain an IP address automaticaly" because this IP is given by your ISP at connection time. Reboot MachineB. Try to execute: Ping 10.1.1.2. If this is wrong, review your settings.

At this point, try, from MachineA, Ping 10.1.1.2 (machineb) and vice-versa. If this is OK, you have you TCP/IP network running between you 2 PCs.

The main difference is that, when connected to the Net, MachineB will have two IPs: here you will have to deal with gateways, proxy and so on.

The idea is simple: you need to tell MachineA that it needs to go to external Internet using the gateway MachineB (that is connected by modem). With plain Windows 95 this is impossible. You will need a proxy server, and the configuration varies from each brand. But this is another phase, and the documentation of you proxy server should tell you how to do.

Hope this could help you.
0
 
LVL 1

Author Comment

by:dovedove
ID: 1757626
Thankyou very much fmismetti. Your answer to my question was given with extensive detail, in general the details were similar to my machines. However, a few small variations which I would assume apply to the W95 version.. I have removed the TCP/IP on the client station and reinstalled. I then set up the two computers following your suggestions. The client station is now able to ping itself, also pinging between computers is successful. Furthermore, I am able to dial out from the client, through the computer with the modem connected. It works fantastically! I am really pleased with the results. I owe you one fmismetti. Also thankyou to Experts Exchange for this service. How small the world has come as a result of the Internet!
0

Featured Post

Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

Join & Write a Comment

Our Group Policy work started with Small Business Server in 2000. Microsoft gave us an excellent OU and GPO model in subsequent SBS editions that utilized WMI filters, OU linking, and VBS scripts. These are some of experiences plus our spending a lo…
If you get continual lockouts after changing your Active Directory password, there are several possible reasons.  Two of the most common are using other devices to access your email and stored passwords in the credential manager of windows.
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now