T.R | Title | User | Personal Name | Date | Lines |
---|
3785.1 | | NPSS::RAUHALA | | Tue Aug 13 1996 13:37 | 2 |
| It sounds to me like you need to enter the source and destination,
including multicast destination addresses.
|
3785.2 | | NPSS::WADE | Network Systems Support | Tue Aug 13 1996 15:53 | 15 |
|
Being that the PC is on port 1 there is no need to allow the PC address
to be seen on port 2. Adding a filter entry for the MAC address of the
PC to be allowed on port 1 is all you need on that end.
My guess is that the IP services module is not the DECswitch and it is
connected through port 2 of the DECswitch. So you need to add a filter
entry for the MAC of the IP services module to be allowed on port 2.
Just a guess.....
Bill
|
3785.3 | MAC addresses | BELFST::belcoo.bvo.dec.com::HOUSTON | Peace at last | Fri Aug 16 1996 08:02 | 22 |
| Hello again.
Thanks for the help so far. I now have it working.
My problem was not appreciating the real difference between the physical address and the
MAC address.
Also reply 2 was quite correct. I needed to enter a filter specifying the MAC address of
the IP services module on port 2. Once this was done I regained my SNMP path to the
services module and Hubwatch management of the Portswitch !
For filters to work correctly then the proper MAC address has to be entered for the
workstation in question. Some protocols like Decnet use a modified MAC address while
others like IP use the physical address. A station with IP and Decnet returns the
modified MAC address because modifying protocol takes priority ? Am I correct in saying
this ?
Does anyone know whether NETBEUI modifies the MAC address ?
Best regards,
Colin
|
3785.4 | <-- RE: NetBEUI protocol... | NETCAD::BATTERSBY | | Fri Aug 16 1996 10:27 | 12 |
|
>> Does anyone know whether NetBEUI modifies the MAC address ?
Well, NetBEUI being a non-routable protocol will be missing
information in the frame header that provides routing information
to identify separate logical LANs. I'd have to go out to the lab
and look at a NetBEUI packet to verify that source & destination
MAC addresses are intact, but I suspect that they are not altered
by the NetBEUI protocol.
If I may ask, what prompted you to ask this question?
Bob
|
3785.5 | Netbeui problem | BELFST::belcoo.bvo.dec.com::HOUSTON | Peace at last | Thu Aug 29 1996 11:34 | 15 |
| Hello.
The reason for the NETBEUI question is that I have created a filter on port 1 to allow an NT
workstation. On port 2 I have created a filter to allow a VMS Pathworks server. The default for
unspecified addresses is "do not allow".
Subsequently the workstation has IP connections to the PAthworks server but no NETBEUI
connections ?
I have also not set up any protocol filtering so I cannot understand why the workstation cannot
browse the Pathworks shares as before.
Any ideas ?
Colin
|
3785.6 | Netbeui multicast needed ? | BELFST::belcoo.bvo.dec.com::HOUSTON | Peace at last | Fri Aug 30 1996 08:47 | 19 |
| Hello.
With respect to reply 5 and the Netbeui problem I have noticed the following
behaviour.
With address filters set up to enable , one for the NT workstation, and one for
the Pathworks server I only seem to have IP access to the Server. Netbeui browsing
facility does not work.
Remove unspecfiied filter defaults and the Netbeui browing facility works between
the workstation and the server.
Then re apply the unspecified default filtering, having previously established a
network drive connection to the server, from the client. It still works !
Why does the Netbeui appear to show this different behaviour as compared to IP ?
Perhaps it is a multicast but does anyone know what it is ?
Colin
|