Discussion Locked

Attach TCP/IP to Adapter in Win 95

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We're running NT Server, with mostly Win 98 workstations, which automatically attaches TCP/IP to the adapter. I'm attempting to set up two Win 95 machines the same way, but TCP/IP is not attaching itself to the adapter. In the adapter properties, bindings tab, TCP/IP is checked. On the Win 98 machines, the network properties window shows the "TCP?IP protocol of xxx adapter", while the win 95 machines only report TCP/IP, not of any particular adapter. This is the only inconsistancy I've found.

6 replies

by tba02

Your problem isn't really a problem. WIN95 machines will work just fine in the scenario you describe. If you really want to have the 95 systems show TCP/IP properties foe XXXXX, just add DUN to the system. The 95 machine, having only one networking "device" installed has no reason to ID/differentiate the NIC.

by 3dad

Thank You for your response. It answered my question, I know that is not the root cause.

by tschandw

If the only adapter in the machine is the network adapter that is al it will show. If you have installed two "adapters" (e.g. dial-up networking) then the two adapters will show in the properties screen and individual bindings to the adapters will show (eg TCP/IP on Realtek NIC, TCP/IP on dia-up adapter).

In other words this is normal.

by 3dad

Thank You for your response. It answered my question, I know that is not the root cause.

by 3dad

I accidentally closed this question without awarding the techpoints. Both questions were rejected, which was not my intention. How do I award them now that the question has been closed?

Please Respond.

kpescetto@iprinc.net
kpescetto@aol.com

This discussion is closed to new replies.