1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

MCSE 70-290 Lab on VMware Workstation 7???

Discussion in 'Virtual Computing' started by srijish, Jan 23, 2010.

  1. srijish

    srijish New Member

    6
    0
    18
    MCSE 70-290 Lab on VMware Workstation 7???

    =====================================
    Host Machine (Laptop):

    Processor : AMD Turion64 x2 (2.1 GHz)
    Memory : 4 GB
    OS : Windows Vista Home Premium (64-bit)
    HDD : 250 GB
    Virtual Machine environment : VMware Workstation 7
    =====================================
    Two Virtual Machines created with same specifications:
    • Windows Server 2003 Enterprise M1
    • Windows Server 2003 Enterprise M2

    Processor : 1
    Memory : 256 MB
    Hard Disk : 16 GB (SCSI)
    Network Adapter : Custom (VMnet2)
    OS : Windows Server 2003 Enterprise
    =====================================
    Details of the custom virtual network adapter "vmnet2" below:

    Network : vmnet2
    Subnet IP : 192.168.0.0
    Subnet Mask : 255.255.255.0

    Start IP : 192.168.0.1
    End IP : 192.168.255.254
    Broadcast IP : 192.168.255.255

    Use local DHCP service to distribute IP address to VMs : option disabled

    Connect a host virtual adapter to this network : option disabled
    Host virtual adapter name: VMware Network Adapter VMnet2
    ***comment: if I enable the above option it interferes with my wireless network at home which is also set on 192.168.0.0/24
    =====================================
    Server01 details:
    Role : DC, DNS, DHCP
    IP: 192.168.150.1
    DNS: 127.0.0.1

    Server02 details:
    Role : DC
    IP: 192.168.150.2
    DNS: 192.168.150.1
    =====================================

    Here are my questions:

    Q1. In the Microsoft Training Kit, in Chapter 2 it is asked to create another server "Server02" and make it a member server in the same "contoso.com" domain. Not knowing how to set it up as a member server, I ended up assigning it a DC, DNS and DHCP role similar to the "Server01". Eventually I unassigned the DNS and DHCP role, however I was not able to unassign the DC role. Could someone guide me on how to assign "Server02" as member server.

    Q2. From the "Server01" 192.168.150.1 I can ping "Server02" 192.168.150.2, but vice-versa does not work. Any suggestions.


    Thanks
     
    Last edited: Jan 24, 2010
    Certifications: CCENT, CCNA
    WIP: MCSA
  2. DC Pr0Mo

    DC Pr0Mo Kilobyte Poster

    265
    6
    41
    1. Demote the server by running DCpromo. This will make it a member server.

    2. Check the dns settings of server2, it may be pointing to your router.
     
    Certifications: MCDST | BSc Network Computing
    WIP: 70-291 | 70-293 | 70-294 | 70-297
  3. Bluerinse
    Honorary Member

    Bluerinse Exabyte Poster

    8,871
    167
    256
    He is pinging the IP address not the host name or FQDN, so it's not a DNS issue.

    I would suspect that ICMP packets are being blocked by a software firewall.
     
    Certifications: C&G Electronics - MCSA (W2K) MCSE (W2K)
  4. srijish

    srijish New Member

    6
    0
    18
    The DNS on "Server02" points to the DNS set on "Server01" 192.168.150.1

    Just for some more information below is a brief idea about my home n/w:

    I have a DSL connection at home:

    Wireless Network Adapter (laptop)
    IP : 192.148.0.100
    Subnet : 255.255.255.0
    DNS : 192.168.0.1

    Wireless Router (LAN)
    IP : 192.168.0.1
    Subnet Mask : 255.255.255.0
    DHCP Server : Enabled

    Wireless Router (WAN)
    IP : 192.168.1.64
    Subnet Mask : 255.255.255.0
    DNS : 192.168.1.254 (points to DSL modem)
    Default Gateway : 192.168.1.254 (points to DSL modem)
    DHCP Server : Enabled
     
    Certifications: CCENT, CCNA
    WIP: MCSA
  5. DC Pr0Mo

    DC Pr0Mo Kilobyte Poster

    265
    6
    41
    Are you ping the ipaddress or name of server02?

    I take it the above ip address are ment to be 192.168.150.1 and 192.168.150.2
     
    Last edited: Jan 23, 2010
    Certifications: MCDST | BSc Network Computing
    WIP: 70-291 | 70-293 | 70-294 | 70-297
  6. srijish

    srijish New Member

    6
    0
    18
    Thank you DC Promo and BlueRinse for all your assistance.
    I am sorry, I should have mentioned a few changes that I made to the IP address of Server01 and Server02

    Server01 details:
    Role : DC, DNS, DHCP
    IP: 192.168.0.1
    DNS: 127.0.0.1

    Server02 details:
    Role : DC
    IP: 192.168.0.2
    DNS: 192.168.0.1

    Also I've created a Microsoft Visio Diagram (if it is of any help)
    http://i48.tinypic.com/28up7vo.jpg

    As I said before, I can ping from Server01-->Server02 using the ipaddress.
    See output below:

    From Server01
    C:\Documents and Settings\Administrator>ping 192.168.0.2

    Pinging 192.168.0.2 with 32 bytes of data:

    Reply from 192.168.0.2: bytes=32 time=7ms TTL=128
    Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.2: bytes=32 time<1ms TTL=128

    Ping statistics for 192.168.0.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 7ms, Average = 1ms


    C:\Documents and Settings\Administrator>tracert 192.168.0.2

    Tracing route to SERVER02 [192.168.0.2]
    over a maximum of 30 hops:
    1 <1 ms <1 ms <1 ms SERVER02 [192.168.0.2]
    Trace complete.


    From Server02
    C:\Documents and Settings\Administrator>ping 192.168.0.1

    Pinging 192.168.0.1 with 32 bytes of data:

    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)


    C:\Documents and Settings\Administrator>tracert 192.168.0.1

    Tracing route to 192.168.0.1 over a maximum of 30 hops
    1 * * * Request timed out.
    2 * * * Request timed out.
    3 * * * Request timed out.
    4 * * * Request timed out.


    Q. Please let me know where I am going wrong.

    Q. Also, I was thinking of having vmnet2 adapter on a totally new subnet (192.168.2.0/24). This way it would not interfere with the 0.0/24 and 1.0/24 subnets. If so, I'll have to reassign new IP address and DNS in the new subnet. Is this a good idea?
     
    Last edited: Jan 24, 2010
    Certifications: CCENT, CCNA
    WIP: MCSA
  7. srijish

    srijish New Member

    6
    0
    18
    Ok. Latest update is now I can successfully ping between both the servers.

    What has changed since the last post:
    • Server02 was updated to SP2
    • Enabled Windows Firewall
    • On the "Advanced" in Windows Firewall the Setting for ICMP was enabled to "Allow incoming echo request"

    Previously I could only ping from Server01 --> Server02 (see the ping and tracert o/p in previous post)
    Now I can successfully ping from Server02 --> Server01 (o/p below)

    C:\Documents and Settings\Administrator>ping 192.168.0.1

    Pinging 192.168.0.1 with 32 bytes of data:

    Reply from 192.168.0.1: bytes=32 time=13ms TTL=128
    Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.1: bytes=32 time<1ms TTL=128

    Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 13ms, Average = 3ms

    C:\Documents and Settings\Administrator>tracert 192.168.0.1

    Tracing route to 192.168.0.1 over a maximum of 30 hops
    1 <1 ms <1 ms <1 ms 192.168.0.1
    Trace complete.


    Thank you DC Promo & Bluerinse for your advices and suggestions. As I move forward with the labs, I might have many more questions for you all. :thumbleft
     
    Certifications: CCENT, CCNA
    WIP: MCSA

Share This Page

Loading...