70-215 QOTD 07/05/2004

Discussion in 'Windows Server 2003 / 2008 / 2012 / 2016' started by AJ, May 7, 2004.

  1. AJ

    AJ 01000001 01100100 01101101 01101001 01101110 Administrator

    6,897
    182
    221
    Your network contains several NetWare Servers. You have successfully installed Client Service for NetWare on Windows 2000 Professional computers, and Gateway Service for NetWare on Windows 2000 Server Computers. You recently added a new Windows 2000 Server computer to the network and installed Gateway Service for NetWare on it. For every server and client to communicate in a FDDI environment, which of the following frame types should be used (Choose all that apply)?

    A) 802.2

    B) 802.3

    C) 802.4

    D) 802.5

    Answer tomorrow
     
    Certifications: MCSE, MCSA (messaging), ITIL Foundation v3
    WIP: Breathing in and out, but not out and in, that's just wrong
  2. nugget
    Honorary Member

    nugget Junior toady

    7,796
    71
    224
    A and B. :roll:
     
    Certifications: A+ | Network+ | Security+ | MCP (270,271,272,290,620) | MCDST | MCTS:Vista
    WIP: MCSA, 70-622,680,685
  3. Phoenix
    Honorary Member

    Phoenix 53656e696f7220 4d6f64

    5,749
    200
    246
    id say A C and D

    C is Token Bus, if i recall correctly FDDI can use this
    D is Token Ring, which FDDI uses

    If i recall correctly FDDI can use C or D to communicate depending on the environment it was set up for, im not concrete on that, its been a wee while since i played with FDDI

    A is LLC and unless its required by default, i dont think its needed in this situation
    B is Ethernet, and doesnt seem to be listed as a requirement
     
    Certifications: MCSE, MCITP, VCP
    WIP: > 0
  4. tripwire45
    Honorary Member

    tripwire45 Zettabyte Poster

    13,493
    180
    287
    Does the version of Netware matter? The current version runs TCP/IP natively but earlier versions only ran SPX/IPX.
     
    Certifications: A+ and Network+
  5. Phoenix
    Honorary Member

    Phoenix 53656e696f7220 4d6f64

    5,749
    200
    246
    it shouldnt do
    IPX is a Layer 3 protocol
    we're dealing with Frame types wich are Layer 2 and should be independent of the above protocol,

    For instance we could run IPX over FDDI

    which would still use an 802.4/5 Frame
    or IPX over Ethernet, which would use an 802.3 Frame
     
    Certifications: MCSE, MCITP, VCP
    WIP: > 0
  6. tripwire45
    Honorary Member

    tripwire45 Zettabyte Poster

    13,493
    180
    287
    My opinion is just have the whole network use Ethernet and call it good. However, that's not what the QOTD is asking for. My best guess (and it is a guess) would be ABD. You'll need the Data Link layer, the Ethernet standard and 802.5 Token Ring. There's a little voice in the back of my head that tells me I'm missing something, but I haven't studied FDDI in awhile. If I've goofed, I'm fully prepared to eat a hearty portion of humble pie.
     
    Certifications: A+ and Network+
  7. Phoenix
    Honorary Member

    Phoenix 53656e696f7220 4d6f64

    5,749
    200
    246
    im not sure why we would need the Ethernet frame, nothing in the question says its an ethernet network
     
    Certifications: MCSE, MCITP, VCP
    WIP: > 0
  8. AJ

    AJ 01000001 01100100 01101101 01101001 01101110 Administrator

    6,897
    182
    221
    Correct answer is: AB

    Explanation:

    According to The MS Training Kit:
    The following table lists the topologies and frame types supported by NWLink.

    Ethernet Ethernet II, 802.3, 802.2, and Sub Network Access Protocol (SNAP), which defaults to 802.2

    Token ring 802.5 and SNAP

    Fiber Distributed Data Interface (FDDI) 802.2 and 802.3

    Here's a link to Microsoft
     
    Certifications: MCSE, MCSA (messaging), ITIL Foundation v3
    WIP: Breathing in and out, but not out and in, that's just wrong
  9. AJ

    AJ 01000001 01100100 01101101 01101001 01101110 Administrator

    6,897
    182
    221
    Note - I've had a couple of problems with the link, just keep refreshing and it will show the page. :D
     
    Certifications: MCSE, MCSA (messaging), ITIL Foundation v3
    WIP: Breathing in and out, but not out and in, that's just wrong
  10. tripwire45
    Honorary Member

    tripwire45 Zettabyte Poster

    13,493
    180
    287
    Well, one big helping of humble pie coming up. <yum> :wink:
     
    Certifications: A+ and Network+
  11. Phoenix
    Honorary Member

    Phoenix 53656e696f7220 4d6f64

    5,749
    200
    246
    yup ill have a serving of that too please
    totally forgot about the limitations of the protocol hehe :)
     
    Certifications: MCSE, MCITP, VCP
    WIP: > 0

Share This Page

Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.