Re: XP Pro can't join W2K domain, or get to internet

From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 08/14/04 

Date: Sat, 14 Aug 2004 16:38:05 +0200

Hi,

OK. My suggestion is to:
- change DNS settings of the server and then restart NetLogon service or
reboot the server if you want.
- check if you can add the computer to domain
- then open DNS MMC on the server and right click the server name and click
forwarders tab. Here enable forwarder and enter IP of your ISP DNS. This
will forward any request that AD DNS doesn't know anything about (like
*.hotmail.com, *.google.com, ... * ... etc..) to your ISP's DNS.

- do clients on the network use proxy to access the internet? What happens
if you try to telnet from command line to e.g.

telnet www.cnn.com 80

Do you get blank screen or does it say it can't connect?

Would it be possible to setup a PC (e.g. XP PC) behind gateway and start
telnet service on it. Then from your PC try to connect to it and see with
what IP request comes to your PC behind gateway. This way you will know if
the problem is in NAT or something like that. Even if you don't get reply
back you should still see connection attempts if you run

netstat -an

in command line. If will get anything on the computer behind gateway then
there is probably something wrong with gateway setup. We can go into details
of this setup later.

I don't know what you run for gateway but some devices count licenses that
you buy against internal clients. Check to see it this could be a problem.
You could also restart gateway and then try again.

Well so much for now :-)

Mike

"Alan Baldwin" <fineimages77@yahoo.com> wrote in message
news:eULmRmggEHA.2916@TK2MSFTNGP12.phx.gbl...
> Mike,
> >>NetBIOS should not resolve the problem, but it could cause it if it was
> installed.
> HMM, I didn't know that. I have run into a few times where a Windows 2000
> workstation wouldn't join a Windows NT 4.0 domain using TCP/IP, but if I
> enabled NetBIOS, it joined fine. Then I removed NerBIOS, and TCP was
> working from then on. Pretty weird.
>
> Funny you should mention taking the IP of an existing machine. I did
that,
> using the workstation at the desk I was using. I hooked that computer
back
> up, checked the IP it was getting, turned it off, went to server and
> deleated that IP from the leases, then gave that as a static for the
laptop.
> (Same subnet, gateway and DNS.) Still didn't work. On that same note,
one
> other thing I tried was using the DNS numbers from the ISP, just to see if
I
> could get it to go out to the Internet, but it didn't. I figured it
> wouldn't solve the problem, since IP numbers weren't getting out past the
> Gateway anyhow when I pinged them.
>
> Date and time were the first things I discovered to be way off, and
thought
> that I had foudn the problem. I was quite excited, thinking surely that
was
> it. Wrong. <G> Date and time match the server within about 1 minute now.
> Still didn't help.
>
> >>Where is Win2K server DNS setting point at? It should point back at
itself
> >>(server's own IP should be under TCP/IP settings -> DNS server setting)
if
> AD server is also DNS server.
> HMM, that looks like it wasn't set up correctly. I will change that when
I
> go over there. I have the ISP DNS settings in the DNS box on the server
TCP
> properties. This was the first Windows 2000 Server I ever set up 3-4
years
> ago, so I guess I messed that up. I'll have to fix that. I just never
> noticed it before, and since it was working, didn't think anything of it.
> Thanks for that call!
>
> >>Check that AD DNS service is running and restart NetLogon service on AD
> (Don't disable the service, just restart it).
> Will try that when I get there.
>
> Sounds like I have 3-4 things to try now when I get back over there.
Thanks
> Mike!!! I will post back my findings.
> Alan
>
>

Relevant Pages
Loading