First Hurdle

Sooooo....

I have my Windows Server 2003 server up and running, and I have a
workstation running XP Pro. Both hooked up to a hub, and I've created a
user to log on to my test domain (CONTOSO.COM) as shown in the MS Press
70-290 book. Logging on and browsing my little network with no problems...

Stupidly, I upgrade my workstation with SP2 and everything goes to lala
land.

On the PC, I can ping the server (and the DNS name) with no problem. On the
server, pinging the workstation I get "Request Timed Out". On the server, I
can browse down to the domain, double-click the workstation, and it tells me
I don't have any access rights to that computer...strange, as I'm logged in
to the server as a user in Domain Admins.

On the Workstation, I browse to the domain, but upon double clicking the
domain I get;

"Contoso is not accessible. You might not have permission to access this
network resource. Contact the adminis[blah]. The list of servers for this
workgroup is not currently available."

Although the user I'm logging in as is a member of domain admins on the
server, and administrator of the local machine. Since I'm at the the very
beginning of learning about Server 2003, I'm not really sure what I'm
looking for, as I've never experienced this problem when logging any client
(98, 2K, XP) to our old NT4 network at work...

I have removed SP2 from the workstation to no avail. Link lights are all up
on the hub and no errors (seemingly) from the network cards, so I'm a little
lost and stumped as I can't continue my study until this is fixed...

Haylp!

Steve Swallow

Steven Swallow

In microsoft.public.cert.exam.mcse, Steven Swallow climbed on a soapbox
& opined:

> Sooooo....
>
> I have my Windows Server 2003 server up and running, and I have a
> workstation running XP Pro. Both hooked up to a hub, and I've created
> a user to log on to my test domain (CONTOSO.COM) as shown in the MS
> Press 70-290 book. Logging on and browsing my little network with no
> problems...
>
> Stupidly, I upgrade my workstation with SP2 and everything goes to
> lala land.
>
> On the PC, I can ping the server (and the DNS name) with no problem.
> On the server, pinging the workstation I get "Request Timed Out". On
> the server, I can browse down to the domain, double-click the
> workstation, and it tells me I don't have any access rights to that
> computer...strange, as I'm logged in to the server as a user in Domain
> Admins.
>
> On the Workstation, I browse to the domain, but upon double clicking
> the domain I get;
>
> "Contoso is not accessible. You might not have permission to access
> this network resource. Contact the adminis[blah]. The list of
> servers for this workgroup is not currently available."
>
> Although the user I'm logging in as is a member of domain admins on
> the server, and administrator of the local machine. Since I'm at the
> the very beginning of learning about Server 2003, I'm not really sure
> what I'm looking for, as I've never experienced this problem when
> logging any client (98, 2K, XP) to our old NT4 network at work...
>
> I have removed SP2 from the workstation to no avail. Link lights are
> all up on the hub and no errors (seemingly) from the network cards, so
> I'm a little lost and stumped as I can't continue my study until this
> is fixed...
>
> Haylp!
>
> Steve Swallow
>
>
>

Check your Firewall. Especially any 3rd party firewall. Open them up and
see what happens,

JaR

JaR

And remember that SP2 activates the firewall by default

--
Kendal Emery
MCNGP #19
Now living in the great state of Colorado
Permament resident of the State of Confusion
"JaR" <> wrote in message
news:Xns9581857442EC5plentespamsuxsofthom@207.46.2 48.16...
> In microsoft.public.cert.exam.mcse, Steven Swallow climbed on a soapbox
> & opined:
>
> > Sooooo....
> >
> > I have my Windows Server 2003 server up and running, and I have a
> > workstation running XP Pro. Both hooked up to a hub, and I've created
> > a user to log on to my test domain (CONTOSO.COM) as shown in the MS
> > Press 70-290 book. Logging on and browsing my little network with no
> > problems...
> >
> > Stupidly, I upgrade my workstation with SP2 and everything goes to
> > lala land.
> >
> > On the PC, I can ping the server (and the DNS name) with no problem.
> > On the server, pinging the workstation I get "Request Timed Out". On
> > the server, I can browse down to the domain, double-click the
> > workstation, and it tells me I don't have any access rights to that
> > computer...strange, as I'm logged in to the server as a user in Domain
> > Admins.
> >
> > On the Workstation, I browse to the domain, but upon double clicking
> > the domain I get;
> >
> > "Contoso is not accessible. You might not have permission to access
> > this network resource. Contact the adminis[blah]. The list of
> > servers for this workgroup is not currently available."
> >
> > Although the user I'm logging in as is a member of domain admins on
> > the server, and administrator of the local machine. Since I'm at the
> > the very beginning of learning about Server 2003, I'm not really sure
> > what I'm looking for, as I've never experienced this problem when
> > logging any client (98, 2K, XP) to our old NT4 network at work...
> >
> > I have removed SP2 from the workstation to no avail. Link lights are
> > all up on the hub and no errors (seemingly) from the network cards, so
> > I'm a little lost and stumped as I can't continue my study until this
> > is fixed...
> >
> > Haylp!
> >
> > Steve Swallow
> >
> >
> >
>
> Check your Firewall. Especially any 3rd party firewall. Open them up and
> see what happens,
>
> JaR

Kendal Emery

In microsoft.public.cert.exam.mcse, Kendal Emery climbed on a soapbox &
opined:

> And remember that SP2 activates the firewall by default
>

That would have sorta been my point.

JaR

While you are doing your testing on the lan and behind a firewall I assume,
disable the XP ICF firewall that by default is enabled in XP SP2. Then make
sure your dns is configured correctly in that the domain controller points
only to itself as it's preferred dns server n tcp/ip properties and as shown
via Ipconfig /all and that your domain member computers point ONLY to domain
controllers running dns and containing the domain zone. Often problems arise
because ISP dns servers are added to the preferred dns server list for
domain computers. See the link below on AD dns faq and know it well for your
studies.

http://support.microsoft.com/default...en-us%3B291382

Run the support tool netdiag first on the domain controller and then dcdiag.
Run netdiag on the domain computer that you are having a problem with. Look
for failed tests/errors/warnings particularly relating to dns, dclist,
kerberos, and secure channel. You will find netdiag and dcdiag to be two
extremely helpful tools in troubleshooting domain and networking issues.
Other very helpful tools will be gpotool and gpresult. The support tools are
on the install disk of the appropriate operating system in the support/tools
folder where you will have to run the setup program there to install
them.Also get into the habit of checking Event Viewer on all computers
involved whenever you experience problems. There also seems to be an issue
sometimes with smb signing of which Windows 2003 requires by default. So you
may want to temporarily open Domain Controller Security Policy and go to
security settings/local policies/security options and for the option
Microsoft network server:digitally sign communications(always) configure it
to be disabled - NOT undefined and then run gpupdate /target:computer /force
to cause the security policy to be refreshed to see if that helps. ---
Steve

"Steven Swallow" <> wrote in message
news:ckk1an$10o$...
> Sooooo....
>
> I have my Windows Server 2003 server up and running, and I have a
> workstation running XP Pro. Both hooked up to a hub, and I've created a
> user to log on to my test domain (CONTOSO.COM) as shown in the MS Press
> 70-290 book. Logging on and browsing my little network with no
> problems...
>
> Stupidly, I upgrade my workstation with SP2 and everything goes to lala
> land.
>
> On the PC, I can ping the server (and the DNS name) with no problem. On
> the
> server, pinging the workstation I get "Request Timed Out". On the server,
> I
> can browse down to the domain, double-click the workstation, and it tells
> me
> I don't have any access rights to that computer...strange, as I'm logged
> in
> to the server as a user in Domain Admins.
>
> On the Workstation, I browse to the domain, but upon double clicking the
> domain I get;
>
> "Contoso is not accessible. You might not have permission to access this
> network resource. Contact the adminis[blah]. The list of servers for
> this
> workgroup is not currently available."
>
> Although the user I'm logging in as is a member of domain admins on the
> server, and administrator of the local machine. Since I'm at the the very
> beginning of learning about Server 2003, I'm not really sure what I'm
> looking for, as I've never experienced this problem when logging any
> client
> (98, 2K, XP) to our old NT4 network at work...
>
> I have removed SP2 from the workstation to no avail. Link lights are all
> up
> on the hub and no errors (seemingly) from the network cards, so I'm a
> little
> lost and stumped as I can't continue my study until this is fixed...
>
> Haylp!
>
> Steve Swallow
>
>

Steven L Umbach

Yep, that was the first thing I turned off!



"Kendal Emery" <> wrote in message
news:...
> And remember that SP2 activates the firewall by default
>
> --
> Kendal Emery
> MCNGP #19
> Now living in the great state of Colorado
> Permament resident of the State of Confusion
> "JaR" <> wrote in message
> news:Xns9581857442EC5plentespamsuxsofthom@207.46.2 48.16...
> > In microsoft.public.cert.exam.mcse, Steven Swallow climbed on a soapbox
> > & opined:
> >
> > > Sooooo....
> > >
> > > I have my Windows Server 2003 server up and running, and I have a
> > > workstation running XP Pro. Both hooked up to a hub, and I've created
> > > a user to log on to my test domain (CONTOSO.COM) as shown in the MS
> > > Press 70-290 book. Logging on and browsing my little network with no
> > > problems...
> > >
> > > Stupidly, I upgrade my workstation with SP2 and everything goes to
> > > lala land.
> > >
> > > On the PC, I can ping the server (and the DNS name) with no problem.
> > > On the server, pinging the workstation I get "Request Timed Out". On
> > > the server, I can browse down to the domain, double-click the
> > > workstation, and it tells me I don't have any access rights to that
> > > computer...strange, as I'm logged in to the server as a user in Domain
> > > Admins.
> > >
> > > On the Workstation, I browse to the domain, but upon double clicking
> > > the domain I get;
> > >
> > > "Contoso is not accessible. You might not have permission to access
> > > this network resource. Contact the adminis[blah]. The list of
> > > servers for this workgroup is not currently available."
> > >
> > > Although the user I'm logging in as is a member of domain admins on
> > > the server, and administrator of the local machine. Since I'm at the
> > > the very beginning of learning about Server 2003, I'm not really sure
> > > what I'm looking for, as I've never experienced this problem when
> > > logging any client (98, 2K, XP) to our old NT4 network at work...
> > >
> > > I have removed SP2 from the workstation to no avail. Link lights are
> > > all up on the hub and no errors (seemingly) from the network cards, so
> > > I'm a little lost and stumped as I can't continue my study until this
> > > is fixed...
> > >
> > > Haylp!
> > >
> > > Steve Swallow
> > >
> > >
> > >
> >
> > Check your Firewall. Especially any 3rd party firewall. Open them up and
> > see what happens,
> >
> > JaR
>
>

Steven Swallow

Hullo again!

I'll work through this little lot tonight and see if i can get some joy.
The server itself has no net access, but the possibility is that the
workstation could have a DNS issue...I check it all out and let you know how
I get on.

Thanks,

Steve

"Steven L Umbach" <> wrote in message
news:8Xmbd.387240$Fg5.301399@attbi_s53...
> While you are doing your testing on the lan and behind a firewall I
assume,
> disable the XP ICF firewall that by default is enabled in XP SP2. Then
make
> sure your dns is configured correctly in that the domain controller points
> only to itself as it's preferred dns server n tcp/ip properties and as
shown
> via Ipconfig /all and that your domain member computers point ONLY to
domain
> controllers running dns and containing the domain zone. Often problems
arise
> because ISP dns servers are added to the preferred dns server list for
> domain computers. See the link below on AD dns faq and know it well for
your
> studies.
>
> http://support.microsoft.com/default...en-us%3B291382
>
> Run the support tool netdiag first on the domain controller and then
dcdiag.
> Run netdiag on the domain computer that you are having a problem with.
Look
> for failed tests/errors/warnings particularly relating to dns, dclist,
> kerberos, and secure channel. You will find netdiag and dcdiag to be two
> extremely helpful tools in troubleshooting domain and networking issues.
> Other very helpful tools will be gpotool and gpresult. The support tools
are
> on the install disk of the appropriate operating system in the
support/tools
> folder where you will have to run the setup program there to install
> them.Also get into the habit of checking Event Viewer on all computers
> involved whenever you experience problems. There also seems to be an issue
> sometimes with smb signing of which Windows 2003 requires by default. So
you
> may want to temporarily open Domain Controller Security Policy and go to
> security settings/local policies/security options and for the option
> Microsoft network server:digitally sign communications(always) configure
it
> to be disabled - NOT undefined and then run gpupdate /target:computer
/force
> to cause the security policy to be refreshed to see if that helps. ---
> Steve
>
> "Steven Swallow" <> wrote in message
> news:ckk1an$10o$...
> > Sooooo....
> >
> > I have my Windows Server 2003 server up and running, and I have a
> > workstation running XP Pro. Both hooked up to a hub, and I've created a
> > user to log on to my test domain (CONTOSO.COM) as shown in the MS Press
> > 70-290 book. Logging on and browsing my little network with no
> > problems...
> >
> > Stupidly, I upgrade my workstation with SP2 and everything goes to lala
> > land.
> >
> > On the PC, I can ping the server (and the DNS name) with no problem. On
> > the
> > server, pinging the workstation I get "Request Timed Out". On the
server,
> > I
> > can browse down to the domain, double-click the workstation, and it
tells
> > me
> > I don't have any access rights to that computer...strange, as I'm logged
> > in
> > to the server as a user in Domain Admins.
> >
> > On the Workstation, I browse to the domain, but upon double clicking the
> > domain I get;
> >
> > "Contoso is not accessible. You might not have permission to access
this
> > network resource. Contact the adminis[blah]. The list of servers for
> > this
> > workgroup is not currently available."
> >
> > Although the user I'm logging in as is a member of domain admins on the
> > server, and administrator of the local machine. Since I'm at the the
very
> > beginning of learning about Server 2003, I'm not really sure what I'm
> > looking for, as I've never experienced this problem when logging any
> > client
> > (98, 2K, XP) to our old NT4 network at work...
> >
> > I have removed SP2 from the workstation to no avail. Link lights are
all
> > up
> > on the hub and no errors (seemingly) from the network cards, so I'm a
> > little
> > lost and stumped as I can't continue my study until this is fixed...
> >
> > Haylp!
> >
> > Steve Swallow
> >
> >
>
>

Steven Swallow