Re: Resolve Printer long names mapping by FQDN name
- From: chua <chua@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 1 Dec 2008 06:25:02 -0800
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
- References:
- Resolve Printer long names mapping by FQDN name
- From: chua
- Re: Resolve Printer long names mapping by FQDN name
- From: Meinolf Weber
- Resolve Printer long names mapping by FQDN name
- Prev by Date: Lockout accounts
- Next by Date: Re: Lockout accounts
- Previous by thread: Re: Resolve Printer long names mapping by FQDN name
- Next by thread: Re: LDAP access problem
- Index(es):
Relevant Pages
|