| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 810.1 | Disable TCP/IP on one of the cards... | MBSVAX::SLOAN | Just Another Manic Monday | Fri May 16 1997 04:20 | 11 |
| >How can I setup private and corporate network in Wolfpack B2?
You have to disable TCP/IP on one of the network cards - run NetBEUI
only on this car. The other card you can run TCP/IP and NetBEUI on as
normal.
Hth,
/Shaun
|
| 810.2 | Admin Guide says use TCP/IP | MSE1::MASTRANGELO | | Fri May 16 1997 07:18 | 10 |
|
re -.1
Is this right? According to the Administrator's Guide that I got with
Beta 2, Wolfpack uses UDP for node-to-node communication. This implies
that TCP/IP is a requirement for the private (and public) networks.
On page 58 of the guide it actually states "Before you install the
Wolfpack software, you must configure both nodesto use the TCP/IP
protocol over all interconnects."
|
| 810.3 | Wolfpack doesn't use NETBEUI | DECWET::CAPPELLOF | My other brain is a polymer | Fri May 16 1997 10:09 | 3 |
| I'd agree with .2. Wolfpack does not use NETBEUI at all. I'll ask the
Wolfpack experts at Microsoft why B2 SETUP doesn't ask about network
card.
|
| 810.4 | Try different subnets | SUBSYS::HOPEWELL | StorageWorks for PC Lans | Thu May 22 1997 07:35 | 9 |
| The Admin Guide on page 58 talks about private network addressing. I have 2
NIC's in each system. The private NIC i assigned an IP address in a different
subnet that the public NIC and it works just fine. TCP is enable on both NICS.
The tricky part is when you install Wolfpack to know which board is public
and which is private if you have all the same type of NICS. Use the IPCONFIG
command to show you your setup setup.
Mark
|