Any of those servers multihomed? Sounds like a DNS or
WINS problem, probably WINS. Check the <1Bh> entry in the
WINS database, it should be an address that is accessible
to all the clients. If all the printers that a user would
use (users use? like woodchuck chuck... sorry to much
caffine) are on thier subnet, you could ditch WINS
altogether and rely on broadcasts for browsing (better
slow browsing than no browsing I say), but that's a bad
idea. Since broadcasts don't normally traverse routers,
Win 2K workstations could dynamically register themselves
with DNS, so they should be fine, but those pesky 98 boxes
can't do that. So how do you get them to register with
the WINS server across the router? Hmmm... You must either
have static address at the remote sites, or be using a
DHCP forwarder. Maybe a WINS proxy? That would be my
guess. KB 121004 may be helful. If computer A cannot
access computer B, then the problem could be that computer
A cannot access the WINS server, or computer B did not
register with the WINS server. Since your server probably
registered with the WINS server (check the WINS database
to confirm this) and the user reports problem contacting
the DC (cannot find netlogon entry) we'll assume the
problem is not in the registering, but in the query. In
this case WINS Proxy might solve the problem.
>-----Original Message-----
>Yep, I sure do. Both of my 2K3 domain controllers are
>running WINS, DNS and DHCP.
>
>
>>-----Original Message-----
>>Do you have WINS and DNS setup on your network?
>>
>>>-----Original Message-----
>>>Hello. I am in the process of upgrading my Windows NT
>>>4.0 domain that used to have a PDC and 2 BDC's, to a
>>>Windows Server 2003 domain using AD and 2 domain
>>>controllers. I ran the AD migration wizard a month or
>>>two ago and all seemed to be working well. I'm at the
>>>point now where I have my 2 2K3 DC's and I'm getting
>>>ready to shutdown my last NT 4 BDC. I guess it's worth
>>>noting that about 85% of my workstations are still
>>>running Windows 98 and we are planning to upgrade them
>>>all to XP Pro next year. Oh yeah, my company has 15
>>>different offices, each with its own subnet, most have
>no
>>>servers at all.
>>>
>>>OK, here's my problem. A week or so ago, I started
>>>getting calls from users saying that they could not
>print
>>>to network printers anymore. They received a message
>>>saying that the network resource could not be found.
>>>Other random users were still able to print to the same
>>>printer. In addition to this, other users received a
>>>message saying that their domain password was not
>correct
>>>or access to their login server had been denied when
>they
>>>tried to logon to the network. After checking their
>>>domain account, I found that their password was not
>>>incorrect and their account was not locked out. I just
>>>had the user reboot once or twice and then they were
>able
>>>to log in OK. Most of the time, they would receive the
>>>printer problems shortly thereafter. I can not really
>>>find a pattern as to which users are experiencing
>>>problems. It is happening in several, but not all, of
>>>our offices, but is happening just on Windows 98
>>>machines.
>>>
>>>I have searched through my DC's event logs and have not
>>>found any useful information. While combing through
>the
>>>Microsoft KB, I happened upon some information about
>the
>>>Computer Browser service. My suspicion is that I have
>>>something misconfigured on one of my NT Workstation or
>>>Win 98 machines, but I am not completely sure. I have
>>>not been able to find any information on how the
>computer
>>>browser service pertains to 2K3 and the recommended
>>>configuration, so I am hoping that someone out there
>can
>>>help me out.
>>>
>>>Does anyone have any suggestions or recommendations
>that
>>>might help me out? I appreciate any info you can lend.
>>>
>>>Thanks
>>>-Chris
>>>
>>>.
>>>
>>.
>>
>.
>
|
Similar Threads
Linear Mode
