FSMT: Problem with DFS Root consolidation wizard

Discussion in 'Server Migration' started by Franz Schenk, Feb 28, 2006.

  1. Franz Schenk

    Franz Schenk Guest

    Have a very strange problem with the DFS Root consolidation wizard (part of
    the file server migration toolkit)

    - Have the DFS Roots on an enterprise windows 2003 server "dfssrv" on
    location A
    - Have the retired fileserver "filesrv-ret" on location B

    - have DNS records of "filesrv-ret" pointing to the IP address of
    "filesrv-ret"
    - have DNS records of "filesrv" (Original Name) pointing to the IP address
    of "dfssrv"
    - have the same entries in WINS

    - Have a share called "VPHome"

    - From location A, sucessfull access to the share is possible either by
    \\filesrv\vphome or by the FQDN \\filesrv.domain.com\vphome

    - From location B, successfull access to the share is ONLY possible by
    \\filesrv.domain.com\vphome and does NOT work with \\filesrv\vphome. I'm
    getting the error message "the network path was not found".

    I'm absolutely sure that it is not a NetBIOS name resolution problem. A
    network monitor trace shows the NBT Query Request for "filesrv" and the WINS
    Server instantly answers with the correct IP address of the dfs root server.
    The problem is that a lot of users have offline files to \\filesrv\vphome
    (and a lot on other shared ressources) and it's therefore not possible to
    replace all references to filesrv with the FQDN.

    Any idea where to start to search for the problem? Thank you all in advance
    for any help!
    Franz
     
    Franz Schenk, Feb 28, 2006
    #1
    1. Advertisements

  2. Franz Schenk

    Jason Tan Guest

    Hello,

    Thanks for posting!

    From your description please help to confirm the following information
    first.

    1. Can I assume that the issue occured when you input server name in "DFS
    root Server" blank colume in the DFS Root Consolidation Wizard.

    2.
    | - From location A, sucessfull access to the share is possible either by
    | \\filesrv\vphome or by the FQDN \\filesrv.domain.com\vphome
    |
    | - From location B, successfull access to the share is ONLY possible by
    | \\filesrv.domain.com\vphome and does NOT work with \\filesrv\vphome. I'm
    | getting the error message "the network path was not found".

    Please confirm if above issue occured when accessing the VPhome share by
    UNC in Run..

    Based on my research I suggest you verify if the Remote Registry Service is
    enabled on the server.

    If there is anything that is unclear, please feel free to let me know.

    Best Regards,

    Jason Tan

    Microsoft Online Partner Support
    Get Secure! - www.microsoft.com/security

    =====================================================

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.

    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.





    --------------------
    | From: "Franz Schenk" <[email protected]_SPAM.ch>
    | Subject: FSMT: Problem with DFS Root consolidation wizard
    | Date: Tue, 28 Feb 2006 14:27:35 +0100
    | Lines: 34
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
    | X-RFC2646: Format=Flowed; Original
    | Message-ID: <e9wN#>
    | Newsgroups: microsoft.public.windows.server.migration
    | NNTP-Posting-Host: host11.sig-group.com 217.193.134.11
    | Path: TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    | Xref: TK2MSFTNGXA03.phx.gbl
    microsoft.public.windows.server.migration:22658
    | X-Tomcat-NG: microsoft.public.windows.server.migration
    |
    | Have a very strange problem with the DFS Root consolidation wizard (part
    of
    | the file server migration toolkit)
    |
    | - Have the DFS Roots on an enterprise windows 2003 server "dfssrv" on
    | location A
    | - Have the retired fileserver "filesrv-ret" on location B
    |
    | - have DNS records of "filesrv-ret" pointing to the IP address of
    | "filesrv-ret"
    | - have DNS records of "filesrv" (Original Name) pointing to the IP
    address
    | of "dfssrv"
    | - have the same entries in WINS
    |
    | - Have a share called "VPHome"
    |
    | - From location A, sucessfull access to the share is possible either by
    | \\filesrv\vphome or by the FQDN \\filesrv.domain.com\vphome
    |
    | - From location B, successfull access to the share is ONLY possible by
    | \\filesrv.domain.com\vphome and does NOT work with \\filesrv\vphome. I'm
    | getting the error message "the network path was not found".
    |
    | I'm absolutely sure that it is not a NetBIOS name resolution problem. A
    | network monitor trace shows the NBT Query Request for "filesrv" and the
    WINS
    | Server instantly answers with the correct IP address of the dfs root
    server.
    | The problem is that a lot of users have offline files to \\filesrv\vphome
    | (and a lot on other shared ressources) and it's therefore not possible to
    | replace all references to filesrv with the FQDN.
    |
    | Any idea where to start to search for the problem? Thank you all in
    advance
    | for any help!
    | Franz
    |
    |
    |
     
    Jason Tan, Mar 1, 2006
    #2
    1. Advertisements

  3. Franz Schenk

    Franz Schenk Guest

    Hello

    Thank you for your feedback!

    - Question 1: If I understand your question (my English is not so good) you
    are right, when starting the DFS root consolidation wizard, I had to enter
    the server holding the DFS Roots manually in the field "DFS root server"

    - Question 2: I performed the test exactly as you described: Enter the UNC's
    into the run field from the start menu.

    - The remote registry service is running on the DFS Root cosolidation
    server.

    But after spending a few hours to track down the problem, we had to go on
    and as a "workaround", we upgraded a Windows 2003 Server Standard Edition on
    Location B to Windows Server 2003 Enterprise Edition and configured the DFS
    Roots on this server on location B.

    What we have found during troubleshooting was that the DFS root server sent
    a data frame, Ptotocol NBT with a description "negative session response -
    called name not present" to the client requesting the ressources from the
    old fileserver from the DFS root consolidation server. This data frame was
    not present when requesting the same ressource from a client from location
    A.

    If you are intersted in the Network capture, I can send it to you. But fur
    us, the problem is solved for the moment.

    best reagrds,
    Franz
     
    Franz Schenk, Mar 2, 2006
    #3
  4. Franz Schenk

    Jason Tan Guest

    Hello,

    Thank you for your reply and the detailed additional feedback on how you
    were successful in resolving this issue. I would like to provide you with
    more information for your reference:

    244380 How to configure DFS to use fully qualified domain names in referrals
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;244380

    If you have any other questions or concerns, please do not hesitate to
    contact us. It is always our pleasure to be of assistance.

    Best Regards,

    Jason Tan

    Microsoft Online Partner Support
    Get Secure! - www.microsoft.com/security

    =====================================================

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.

    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.



    --------------------
    | From: "Franz Schenk" <[email protected]_SPAM.ch>
    | References: <e9wN#>
    <>
    | Subject: Re: FSMT: Problem with DFS Root consolidation wizard
    | Date: Thu, 2 Mar 2006 09:28:37 +0100
    | Lines: 148
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
    | X-RFC2646: Format=Flowed; Original
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
    | Message-ID: <>
    | Newsgroups: microsoft.public.windows.server.migration
    | NNTP-Posting-Host: host11.sig-group.com 217.193.134.11
    | Path: TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
    | Xref: TK2MSFTNGXA03.phx.gbl
    microsoft.public.windows.server.migration:22688
    | X-Tomcat-NG: microsoft.public.windows.server.migration
    |
    | Hello
    |
    | Thank you for your feedback!
    |
    | - Question 1: If I understand your question (my English is not so good)
    you
    | are right, when starting the DFS root consolidation wizard, I had to
    enter
    | the server holding the DFS Roots manually in the field "DFS root server"
    |
    | - Question 2: I performed the test exactly as you described: Enter the
    UNC's
    | into the run field from the start menu.
    |
    | - The remote registry service is running on the DFS Root cosolidation
    | server.
    |
    | But after spending a few hours to track down the problem, we had to go on
    | and as a "workaround", we upgraded a Windows 2003 Server Standard Edition
    on
    | Location B to Windows Server 2003 Enterprise Edition and configured the
    DFS
    | Roots on this server on location B.
    |
    | What we have found during troubleshooting was that the DFS root server
    sent
    | a data frame, Ptotocol NBT with a description "negative session response
    -
    | called name not present" to the client requesting the ressources from the
    | old fileserver from the DFS root consolidation server. This data frame
    was
    | not present when requesting the same ressource from a client from
    location
    | A.
    |
    | If you are intersted in the Network capture, I can send it to you. But
    fur
    | us, the problem is solved for the moment.
    |
    | best reagrds,
    | Franz
    |
    |
    |
    |
    |
    | | > Hello,
    | >
    | > Thanks for posting!
    | >
    | > From your description please help to confirm the following information
    | > first.
    | >
    | > 1. Can I assume that the issue occured when you input server name in
    "DFS
    | > root Server" blank colume in the DFS Root Consolidation Wizard.
    | >
    | > 2.
    | > | - From location A, sucessfull access to the share is possible either
    by
    | > | \\filesrv\vphome or by the FQDN \\filesrv.domain.com\vphome
    | > |
    | > | - From location B, successfull access to the share is ONLY possible by
    | > | \\filesrv.domain.com\vphome and does NOT work with \\filesrv\vphome.
    I'm
    | > | getting the error message "the network path was not found".
    | >
    | > Please confirm if above issue occured when accessing the VPhome share by
    | > UNC in Run..
    | >
    | > Based on my research I suggest you verify if the Remote Registry
    Service
    | > is
    | > enabled on the server.
    | >
    | > If there is anything that is unclear, please feel free to let me know.
    | >
    | > Best Regards,
    | >
    | > Jason Tan
    | >
    | > Microsoft Online Partner Support
    | > Get Secure! - www.microsoft.com/security
    | >
    | > =====================================================
    | >
    | > When responding to posts, please "Reply to Group" via your newsreader so
    | > that others may learn and benefit from your issue.
    | >
    | > =====================================================
    | > This posting is provided "AS IS" with no warranties, and confers no
    | > rights.
    | >
    | >
    | >
    | >
    | >
    | > --------------------
    | > | From: "Franz Schenk" <[email protected]_SPAM.ch>
    | > | Subject: FSMT: Problem with DFS Root consolidation wizard
    | > | Date: Tue, 28 Feb 2006 14:27:35 +0100
    | > | Lines: 34
    | > | X-Priority: 3
    | > | X-MSMail-Priority: Normal
    | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
    | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
    | > | X-RFC2646: Format=Flowed; Original
    | > | Message-ID: <e9wN#>
    | > | Newsgroups: microsoft.public.windows.server.migration
    | > | NNTP-Posting-Host: host11.sig-group.com 217.193.134.11
    | > | Path: TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    | > | Xref: TK2MSFTNGXA03.phx.gbl
    | > microsoft.public.windows.server.migration:22658
    | > | X-Tomcat-NG: microsoft.public.windows.server.migration
    | > |
    | > | Have a very strange problem with the DFS Root consolidation wizard
    (part
    | > of
    | > | the file server migration toolkit)
    | > |
    | > | - Have the DFS Roots on an enterprise windows 2003 server "dfssrv" on
    | > | location A
    | > | - Have the retired fileserver "filesrv-ret" on location B
    | > |
    | > | - have DNS records of "filesrv-ret" pointing to the IP address of
    | > | "filesrv-ret"
    | > | - have DNS records of "filesrv" (Original Name) pointing to the IP
    | > address
    | > | of "dfssrv"
    | > | - have the same entries in WINS
    | > |
    | > | - Have a share called "VPHome"
    | > |
    | > | - From location A, sucessfull access to the share is possible either
    by
    | > | \\filesrv\vphome or by the FQDN \\filesrv.domain.com\vphome
    | > |
    | > | - From location B, successfull access to the share is ONLY possible by
    | > | \\filesrv.domain.com\vphome and does NOT work with \\filesrv\vphome.
    I'm
    | > | getting the error message "the network path was not found".
    | > |
    | > | I'm absolutely sure that it is not a NetBIOS name resolution problem.
    A
    | > | network monitor trace shows the NBT Query Request for "filesrv" and
    the
    | > WINS
    | > | Server instantly answers with the correct IP address of the dfs root
    | > server.
    | > | The problem is that a lot of users have offline files to
    | > \\filesrv\vphome
    | > | (and a lot on other shared ressources) and it's therefore not
    possible
    | > to
    | > | replace all references to filesrv with the FQDN.
    | > |
    | > | Any idea where to start to search for the problem? Thank you all in
    | > advance
    | > | for any help!
    | > | Franz
    | > |
    | > |
    | > |
    | >
    |
    |
    |
     
    Jason Tan, Mar 3, 2006
    #4
  5. Franz Schenk

    Franz Schenk Guest

    Hello

    Thank you for the interesting KB article! When reading this, I suppose that
    in practice it is much easier to setup and mainatin a DFS infrastructure
    when WINS is in place and NetBIOS over TCP/IP is not disabled.

    Franz
     
    Franz Schenk, Mar 3, 2006
    #5
  6. Franz Schenk

    Jason Tan Guest

    Hello,

    I appreciate your update and response, and I am glad to hear that the
    information helped. If you have any other questions or concerns, please do
    not hesitate to contact us. It is always our pleasure to be of assistance.

    Best Regards,

    Jason Tan

    Microsoft Online Partner Support
    Get Secure! - www.microsoft.com/security

    =====================================================

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.

    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.




    --------------------
    | From: "Franz Schenk" <[email protected]_SPAM.ch>
    | References: <e9wN#>
    <>
    <>
    <>
    | Subject: Re: FSMT: Problem with DFS Root consolidation wizard
    | Date: Fri, 3 Mar 2006 16:09:41 +0100
    | Lines: 246
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
    | X-RFC2646: Format=Flowed; Original
    | Message-ID: <#>
    | Newsgroups: microsoft.public.windows.server.migration
    | NNTP-Posting-Host: host11.sig-group.com 217.193.134.11
    | Path: TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
    | Xref: TK2MSFTNGXA03.phx.gbl
    microsoft.public.windows.server.migration:22710
    | X-Tomcat-NG: microsoft.public.windows.server.migration
    |
    | Hello
    |
    | Thank you for the interesting KB article! When reading this, I suppose
    that
    | in practice it is much easier to setup and mainatin a DFS infrastructure
    | when WINS is in place and NetBIOS over TCP/IP is not disabled.
    |
    | Franz
    |
    | | > Hello,
    | >
    | > Thank you for your reply and the detailed additional feedback on how you
    | > were successful in resolving this issue. I would like to provide you
    with
    | > more information for your reference:
    | >
    | > 244380 How to configure DFS to use fully qualified domain names in
    | > referrals
    | > http://support.microsoft.com/default.aspx?scid=kb;EN-US;244380
    | >
    | > If you have any other questions or concerns, please do not hesitate to
    | > contact us. It is always our pleasure to be of assistance.
    | >
    | > Best Regards,
    | >
    | > Jason Tan
    | >
    | > Microsoft Online Partner Support
    | > Get Secure! - www.microsoft.com/security
    | >
    | > =====================================================
    | >
    | > When responding to posts, please "Reply to Group" via your newsreader so
    | > that others may learn and benefit from your issue.
    | >
    | > =====================================================
    | > This posting is provided "AS IS" with no warranties, and confers no
    | > rights.
    | >
    | >
    | >
    | > --------------------
    | > | From: "Franz Schenk" <[email protected]_SPAM.ch>
    | > | References: <e9wN#>
    | > <>
    | > | Subject: Re: FSMT: Problem with DFS Root consolidation wizard
    | > | Date: Thu, 2 Mar 2006 09:28:37 +0100
    | > | Lines: 148
    | > | X-Priority: 3
    | > | X-MSMail-Priority: Normal
    | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
    | > | X-RFC2646: Format=Flowed; Original
    | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
    | > | Message-ID: <>
    | > | Newsgroups: microsoft.public.windows.server.migration
    | > | NNTP-Posting-Host: host11.sig-group.com 217.193.134.11
    | > | Path: TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
    | > | Xref: TK2MSFTNGXA03.phx.gbl
    | > microsoft.public.windows.server.migration:22688
    | > | X-Tomcat-NG: microsoft.public.windows.server.migration
    | > |
    | > | Hello
    | > |
    | > | Thank you for your feedback!
    | > |
    | > | - Question 1: If I understand your question (my English is not so
    good)
    | > you
    | > | are right, when starting the DFS root consolidation wizard, I had to
    | > enter
    | > | the server holding the DFS Roots manually in the field "DFS root
    server"
    | > |
    | > | - Question 2: I performed the test exactly as you described: Enter the
    | > UNC's
    | > | into the run field from the start menu.
    | > |
    | > | - The remote registry service is running on the DFS Root cosolidation
    | > | server.
    | > |
    | > | But after spending a few hours to track down the problem, we had to
    go
    | > on
    | > | and as a "workaround", we upgraded a Windows 2003 Server Standard
    | > Edition
    | > on
    | > | Location B to Windows Server 2003 Enterprise Edition and configured
    the
    | > DFS
    | > | Roots on this server on location B.
    | > |
    | > | What we have found during troubleshooting was that the DFS root server
    | > sent
    | > | a data frame, Ptotocol NBT with a description "negative session
    response
    | > -
    | > | called name not present" to the client requesting the ressources from
    | > the
    | > | old fileserver from the DFS root consolidation server. This data frame
    | > was
    | > | not present when requesting the same ressource from a client from
    | > location
    | > | A.
    | > |
    | > | If you are intersted in the Network capture, I can send it to you. But
    | > fur
    | > | us, the problem is solved for the moment.
    | > |
    | > | best reagrds,
    | > | Franz
    | > |
    | > |
    | > |
    | > |
    | > |
    | > Newsbeitrag
    | > | | > | > Hello,
    | > | >
    | > | > Thanks for posting!
    | > | >
    | > | > From your description please help to confirm the following
    information
    | > | > first.
    | > | >
    | > | > 1. Can I assume that the issue occured when you input server name in
    | > "DFS
    | > | > root Server" blank colume in the DFS Root Consolidation Wizard.
    | > | >
    | > | > 2.
    | > | > | - From location A, sucessfull access to the share is possible
    | > either
    | > by
    | > | > | \\filesrv\vphome or by the FQDN \\filesrv.domain.com\vphome
    | > | > |
    | > | > | - From location B, successfull access to the share is ONLY
    possible
    | > by
    | > | > | \\filesrv.domain.com\vphome and does NOT work with
    \\filesrv\vphome.
    | > I'm
    | > | > | getting the error message "the network path was not found".
    | > | >
    | > | > Please confirm if above issue occured when accessing the VPhome
    share
    | > by
    | > | > UNC in Run..
    | > | >
    | > | > Based on my research I suggest you verify if the Remote Registry
    | > Service
    | > | > is
    | > | > enabled on the server.
    | > | >
    | > | > If there is anything that is unclear, please feel free to let me
    know.
    | > | >
    | > | > Best Regards,
    | > | >
    | > | > Jason Tan
    | > | >
    | > | > Microsoft Online Partner Support
    | > | > Get Secure! - www.microsoft.com/security
    | > | >
    | > | > =====================================================
    | > | >
    | > | > When responding to posts, please "Reply to Group" via your
    newsreader
    | > so
    | > | > that others may learn and benefit from your issue.
    | > | >
    | > | > =====================================================
    | > | > This posting is provided "AS IS" with no warranties, and confers no
    | > | > rights.
    | > | >
    | > | >
    | > | >
    | > | >
    | > | >
    | > | > --------------------
    | > | > | From: "Franz Schenk" <[email protected]_SPAM.ch>
    | > | > | Subject: FSMT: Problem with DFS Root consolidation wizard
    | > | > | Date: Tue, 28 Feb 2006 14:27:35 +0100
    | > | > | Lines: 34
    | > | > | X-Priority: 3
    | > | > | X-MSMail-Priority: Normal
    | > | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
    | > | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
    | > | > | X-RFC2646: Format=Flowed; Original
    | > | > | Message-ID: <e9wN#>
    | > | > | Newsgroups: microsoft.public.windows.server.migration
    | > | > | NNTP-Posting-Host: host11.sig-group.com 217.193.134.11
    | > | > | Path:
    | > TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    | > | > | Xref: TK2MSFTNGXA03.phx.gbl
    | > | > microsoft.public.windows.server.migration:22658
    | > | > | X-Tomcat-NG: microsoft.public.windows.server.migration
    | > | > |
    | > | > | Have a very strange problem with the DFS Root consolidation wizard
    | > (part
    | > | > of
    | > | > | the file server migration toolkit)
    | > | > |
    | > | > | - Have the DFS Roots on an enterprise windows 2003 server
    "dfssrv"
    | > on
    | > | > | location A
    | > | > | - Have the retired fileserver "filesrv-ret" on location B
    | > | > |
    | > | > | - have DNS records of "filesrv-ret" pointing to the IP address of
    | > | > | "filesrv-ret"
    | > | > | - have DNS records of "filesrv" (Original Name) pointing to the IP
    | > | > address
    | > | > | of "dfssrv"
    | > | > | - have the same entries in WINS
    | > | > |
    | > | > | - Have a share called "VPHome"
    | > | > |
    | > | > | - From location A, sucessfull access to the share is possible
    | > either
    | > by
    | > | > | \\filesrv\vphome or by the FQDN \\filesrv.domain.com\vphome
    | > | > |
    | > | > | - From location B, successfull access to the share is ONLY
    possible
    | > by
    | > | > | \\filesrv.domain.com\vphome and does NOT work with
    \\filesrv\vphome.
    | > I'm
    | > | > | getting the error message "the network path was not found".
    | > | > |
    | > | > | I'm absolutely sure that it is not a NetBIOS name resolution
    | > problem.
    | > A
    | > | > | network monitor trace shows the NBT Query Request for "filesrv"
    and
    | > the
    | > | > WINS
    | > | > | Server instantly answers with the correct IP address of the dfs
    root
    | > | > server.
    | > | > | The problem is that a lot of users have offline files to
    | > | > \\filesrv\vphome
    | > | > | (and a lot on other shared ressources) and it's therefore not
    | > possible
    | > | > to
    | > | > | replace all references to filesrv with the FQDN.
    | > | > |
    | > | > | Any idea where to start to search for the problem? Thank you all
    in
    | > | > advance
    | > | > | for any help!
    | > | > | Franz
    | > | > |
    | > | > |
    | > | > |
    | > | >
    | > |
    | > |
    | > |
    | >
    |
    |
    |
     
    Jason Tan, Mar 7, 2006
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.