Announcement

Collapse
No announcement yet.

Problem using Server Names for Drive Mapping

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem using Server Names for Drive Mapping

    Hi I not sure if i'm posting in the right section but we are having a problem mapping a network drive using the server name.

    The environment is a Windows 2003 server setup (fully patched) and we are accessing the network from a remote XP PC via a Netgear VPN. The XP workstation is in a workgroup and the server is in a domain

    We can ping the server across the VPN and we can mapped a drive using the
    //192.168,2.4/sharename syntax and it works fine. If however we try and use the server name it can nolt find it.

    If we try and use the browse function on the Map Drive screen the Domain is not shown just the local workgroup. Do I have a DNS problem

    Many Thanks

  • #2
    Re: Problem using Server Names for Drive Mapping

    Hi

    We had a similar problem with VPN users, check they are getting assigned the correct DNS, it's needs to be the internal one.

    Also if you've got a wins server running this can be added as part of your DHCP vpn scoope.

    quick fix is to edit the PCs host file and add the entries yourself

    I'd start by using the NSlookup command to troubleshoot.

    Comment


    • #3
      Re: Problem using Server Names for Drive Mapping

      WINS setup and working properly???

      Comment


      • #4
        Re: Problem using Server Names for Drive Mapping

        Is the 'Computer Browser' service enabled and set to 'automatic'?

        Comment


        • #5
          Re: Problem using Server Names for Drive Mapping

          Use the LMHOSTS.SAM file to do this. It contains the instructions you need. Edit it, then rename it to LMHOSTS
          A recent poll suggests that 6 out of 7 dwarfs are not happy

          Comment

          Working...
          X