RE: Odd problem with basic AD login script
- From: Ryan Hanisco <RyanHanisco@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 22 Jun 2007 10:56:06 -0700
Cory,
A lot of things, like drive mappings and network neighborhood, still rely on
NetBios for name resolution. Since this is based on broadcast, it doesn't
cross the routed subnet boundary -- This is where WINS comes in. By setting
the node type, you can tell the OS to check with DNS before looking to WINS
or doing a broadcast for the master browser.
This can resolve the issue, but it is a good idea to have WINS there as well
as it can streamline the whole process and anything that takes broadcasts off
your network is a good thing.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL
Remember: Marking helpful answers helps everyone find the info they need
quickly.
"CoryB-" wrote:
I will check into the node type. As for WINS we are not using it at all as.
all our systems are Windows XP and servers are 2003. Is there any need for
WINS?
"Ryan Hanisco" wrote:
Cory,
I would suggest looking at your node type in DNS to make sure you are at
0x8. This will make name resolution look to DNS first. From there, make
sure that your WINS servers are up and working correctly.
This should make the name resolution work better. I am assuming that there
is an issue finding the other servers' domain affiliation across the subnet
boundary. WINS should resolve this.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL
Remember: Marking helpful answers helps everyone find the info they need
quickly.
"CoryB-" wrote:
I have a couple users in our company who get a strange issue on login. We
have a very basic login script that maps public folders from 2 servers on 2
different subnets that are connect to one another via VPN. They are able to
map to the server in their subnet but when the Net Use command runs for the
other server they are prompted to enter a password. The funny thing is if I
connect to the exact same share using the run command there is no problem.
As well I can maully map the drive once the user is logged in. Others at
this site do not have this issue and get all the drive mappings. As well I
have checked security on the shares/folders and all is fine. Any ideas?
CoryB
- Follow-Ups:
- Re: Odd problem with basic AD login script
- From: suzukiman650
- Re: Odd problem with basic AD login script
- Prev by Date: Re: Restore Local Policies to Default?
- Next by Date: Re: If a computer is not used for more than 3 months auto disable
- Previous by thread: Re: Restore Local Policies to Default?
- Next by thread: Re: Odd problem with basic AD login script
- Index(es):
Relevant Pages
|