Resolve Printer long names mapping by FQDN name

Discussion in 'Active Directory' started by chua, Dec 1, 2008.

  1. chua

    chua Guest

    My network is running on AD2003 r2 and XP clients. I'm using .vbs script to
    map network printers during clients login to network. However, i have errors
    when the users logon to windows.

    Error shown on client:

    Scripts: sysvol\path….
    Line: 2
    Char: 1
    Error:
    Code:
    Source: Microsft VBScript runtime error.

    My scripts looks like this:
    Set objNetwork = CreateObject("WScript.Network")
    objNetwork.AddWindowsPrinterConnection "\\ServerName\PrinterName".

    However, if i change the UNC path to "\\ServerName.DomainFQDN\PrinterName".
    it works perfectly OK. But the thing is , it will cause long names. I want to
    know why i cant mapped printers using the Netbios in .Vbs.. i tried typing
    \\servername or \\servername\printer on the clients, it works OK... please
    assist. i need the mapping printers to work.


    regards,

    steve
     
    chua, Dec 1, 2008
    #1
    1. Advertising

  2. Hello chua,

    Make sure that your machines use only domain internal DNS servers. No external
    ip's on the NIC configuration. Are all machines registered correctly in DNS
    forward/reverse lookup zone.

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


    > My network is running on AD2003 r2 and XP clients. I'm using .vbs
    > script to map network printers during clients login to network.
    > However, i have errors when the users logon to windows.
    >
    > Error shown on client:
    >
    > Scripts: sysvol\path..
    > Line: 2
    > Char: 1
    > Error:
    > Code:
    > Source: Microsft VBScript runtime error.
    > My scripts looks like this:
    > Set objNetwork = CreateObject("WScript.Network")
    > objNetwork.AddWindowsPrinterConnection "\\ServerName\PrinterName".
    > However, if i change the UNC path to
    > "\\ServerName.DomainFQDN\PrinterName". it works perfectly OK. But the
    > thing is , it will cause long names. I want to know why i cant mapped
    > printers using the Netbios in .Vbs.. i tried typing \\servername or
    > \\servername\printer on the clients, it works OK... please assist. i
    > need the mapping printers to work.
    >
    > regards,
    >
    > steve
    >
     
    Meinolf Weber, Dec 1, 2008
    #2
    1. Advertising

  3. chua

    chua Guest

    Yes i did, the clients is pointing to the internal DNS only. Clients machine
    is registering in the DNS and Reverse Zone has been configured n registered
    as well.. i cant think of what caused it.. Will enabled WINS solve the issue?

    "Meinolf Weber" wrote:

    > Hello chua,
    >
    > Make sure that your machines use only domain internal DNS servers. No external
    > ip's on the NIC configuration. Are all machines registered correctly in DNS
    > forward/reverse lookup zone.
    >
    > Best regards
    >
    > Meinolf Weber
    > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    > no rights.
    > ** Please do NOT email, only reply to Newsgroups
    > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    >
    >
    > > My network is running on AD2003 r2 and XP clients. I'm using .vbs
    > > script to map network printers during clients login to network.
    > > However, i have errors when the users logon to windows.
    > >
    > > Error shown on client:
    > >
    > > Scripts: sysvol\path..
    > > Line: 2
    > > Char: 1
    > > Error:
    > > Code:
    > > Source: Microsft VBScript runtime error.
    > > My scripts looks like this:
    > > Set objNetwork = CreateObject("WScript.Network")
    > > objNetwork.AddWindowsPrinterConnection "\\ServerName\PrinterName".
    > > However, if i change the UNC path to
    > > "\\ServerName.DomainFQDN\PrinterName". it works perfectly OK. But the
    > > thing is , it will cause long names. I want to know why i cant mapped
    > > printers using the Netbios in .Vbs.. i tried typing \\servername or
    > > \\servername\printer on the clients, it works OK... please assist. i
    > > need the mapping printers to work.
    > >
    > > regards,
    > >
    > > steve
    > >

    >
    >
    >
     
    chua, Dec 1, 2008
    #3
  4. chua

    sqwazi

    Joined:
    Apr 12, 2011
    Messages:
    1
    Hello Steve,

    Did you ever solve this problem? We are experiencing the same thing and we can't figure it out. Thanks.

    Isaac
     
    sqwazi, Apr 12, 2011
    #4
    1. Advertising

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

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Hope

    Fix for long, long, long deleting and copying of files?

    Hope, Feb 9, 2008, in forum: Windows Vista General Discussion
    Replies:
    14
    Views:
    634
    philo
    Feb 11, 2008
  2. Tecnik
    Replies:
    4
    Views:
    5,560
    Kevin D. Goodknecht Sr. [MVP]
    Nov 18, 2005
  3. CJSnet
    Replies:
    2
    Views:
    221
    CJSnet
    Dec 19, 2005
  4. Meinolf Weber [MVP-DS]

    Re: Mapping drive using fqdn fails, but netbios name ok.

    Meinolf Weber [MVP-DS], Jan 6, 2010, in forum: Windows Server
    Replies:
    2
    Views:
    361
    Ace Fekay [MVP-DS, MCT]
    Jan 10, 2010
  5. Meinolf Weber [MVP-DS]

    Re: Mapping drive using FQDN gives error, but NETBIOS name is ok..

    Meinolf Weber [MVP-DS], Jan 6, 2010, in forum: Server Networking
    Replies:
    0
    Views:
    683
    Meinolf Weber [MVP-DS]
    Jan 6, 2010
Loading...

Share This Page