networking problem!

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

Guest
(This post is originally posted at microsoft.public.windowsxp.general, but
there I got an respond asking me to post it in a win2k3 ng)

Hey

I got 2 computers a home. pcA uses winXPpro+sp2, pcB uses win2k3

These 2 computers are connected to each other via a router.

I've created a Active Directory on the win2k3 computer, and now I wants the
winXP box to join the AD.

Both computers are using static IP

Both compueters have set up a LMHOSTS file:
192.168.1.30 "HOMEAD \0x1b" #PRE
192.168.1.30 PCB #PRE #DOM:HOMEAD
192.168.1.20 PCA

In "Advanced TCP/IP Settings" on the winXP machine, default NetBIOS setting
is selected... should I use "Enable NetBIOS over TCP/IP" instead ??

When I run nbtstat -c from the winXP machine I get this... I think it's a
bit strage that the 3 last lines shows HOMEAD with 2 dots (..) at the end

Local Area Connection:
Node IpAddress: [192.168.1.20] Scope Id: []
NetBIOS Remote Cache Name Table
Name Type Host Address Life [sec]
------------------------------------------------------------
HOMEAD <1C> GROUP 192.168.1.30 -1
PCB <03> UNIQUE 192.168.1.30 -1
PCB <00> UNIQUE 192.168.1.30 -1
PCB <20> UNIQUE 192.168.1.30 -1
HOMEAD.. <03> UNIQUE 192.168.1.30 -1
HOMEAD.. <00> UNIQUE 192.168.1.30 -1
HOMEAD.. <20> UNIQUE 192.168.1.30 -1


Here I run nbtstat from the winXP machine against the win2k3 machine:
nbtstat -a PCB
Local Area Connection:
Node IpAddress: [192.168.1.20] Scope Id: []
Host not found.

When I try to add the winXP box to the domain, I get this message:
"The domain name HOMEAD might be a NetBIOS domain name. If this is the
case, verify that the domain name is properly registered with WINS."

Please, what should I do to solve this problem?
 
Re: networking problem!

Hello,

remove the lmhost stuff

maje your winxp to use the pcB as primary DNS in the network configuration
check both clock are in sync (< 5 mn)
join the domain with the FQDN like mydomain.com


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Jeff" <it_consultant1@hotmail.com.NOSPAM> wrote in message
news:etfmOlG%23HHA.3716@TK2MSFTNGP03.phx.gbl...
> (This post is originally posted at microsoft.public.windowsxp.general, but
> there I got an respond asking me to post it in a win2k3 ng)
>
> Hey
>
> I got 2 computers a home. pcA uses winXPpro+sp2, pcB uses win2k3
>
> These 2 computers are connected to each other via a router.
>
> I've created a Active Directory on the win2k3 computer, and now I wants
> the
> winXP box to join the AD.
>
> Both computers are using static IP
>
> Both compueters have set up a LMHOSTS file:
> 192.168.1.30 "HOMEAD \0x1b" #PRE
> 192.168.1.30 PCB #PRE #DOM:HOMEAD
> 192.168.1.20 PCA
>
> In "Advanced TCP/IP Settings" on the winXP machine, default NetBIOS
> setting
> is selected... should I use "Enable NetBIOS over TCP/IP" instead ??
>
> When I run nbtstat -c from the winXP machine I get this... I think it's a
> bit strage that the 3 last lines shows HOMEAD with 2 dots (..) at the end
>
> Local Area Connection:
> Node IpAddress: [192.168.1.20] Scope Id: []
> NetBIOS Remote Cache Name Table
> Name Type Host Address Life [sec]
> ------------------------------------------------------------
> HOMEAD <1C> GROUP 192.168.1.30 -1
> PCB <03> UNIQUE 192.168.1.30 -1
> PCB <00> UNIQUE 192.168.1.30 -1
> PCB <20> UNIQUE 192.168.1.30 -1
> HOMEAD.. <03> UNIQUE 192.168.1.30 -1
> HOMEAD.. <00> UNIQUE 192.168.1.30 -1
> HOMEAD.. <20> UNIQUE 192.168.1.30 -1
>
>
> Here I run nbtstat from the winXP machine against the win2k3 machine:
> nbtstat -a PCB
> Local Area Connection:
> Node IpAddress: [192.168.1.20] Scope Id: []
> Host not found.
>
> When I try to add the winXP box to the domain, I get this message:
> "The domain name HOMEAD might be a NetBIOS domain name. If this is the
> case, verify that the domain name is properly registered with WINS."
>
> Please, what should I do to solve this problem?
>
 
Re: networking problem!

Hello Jeff,

During the promotion you have to setup DNS, check that it is active directory
integrated. For the XP machine just give it a fixed ip config like this and
NO config in the lmhosts file:

XP
ip 192.168.1.20
sm 255.255.255.0
dg router ip
DNS 192.168.1.30

2003
ip 192.168.1.30
sm 255.255.255.0
dg router ip
DNS 192.168.1.30


Then the joining shouldn't be any problem.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> (This post is originally posted at microsoft.public.windowsxp.general,
> but there I got an respond asking me to post it in a win2k3 ng)
>
> Hey
>
> I got 2 computers a home. pcA uses winXPpro+sp2, pcB uses win2k3
>
> These 2 computers are connected to each other via a router.
>
> I've created a Active Directory on the win2k3 computer, and now I
> wants the winXP box to join the AD.
>
> Both computers are using static IP
>
> Both compueters have set up a LMHOSTS file:
> 192.168.1.30 "HOMEAD \0x1b" #PRE
> 192.168.1.30 PCB #PRE #DOM:HOMEAD
> 192.168.1.20 PCA
> In "Advanced TCP/IP Settings" on the winXP machine, default NetBIOS
> setting is selected... should I use "Enable NetBIOS over TCP/IP"
> instead ??
>
> When I run nbtstat -c from the winXP machine I get this... I think
> it's a bit strage that the 3 last lines shows HOMEAD with 2 dots (..)
> at the end
>
> Local Area Connection:
> Node IpAddress: [192.168.1.20] Scope Id: []
> NetBIOS Remote Cache Name Table
> Name Type Host Address Life [sec]
> ------------------------------------------------------------
> HOMEAD <1C> GROUP 192.168.1.30 -1
> PCB <03> UNIQUE 192.168.1.30 -1
> PCB <00> UNIQUE 192.168.1.30 -1
> PCB <20> UNIQUE 192.168.1.30 -1
> HOMEAD.. <03> UNIQUE 192.168.1.30 -1
> HOMEAD.. <00> UNIQUE 192.168.1.30 -1
> HOMEAD.. <20> UNIQUE 192.168.1.30 -1
> Here I run nbtstat from the winXP machine against the win2k3 machine:
> nbtstat -a PCB
> Local Area Connection:
> Node IpAddress: [192.168.1.20] Scope Id: []
> Host not found.
> When I try to add the winXP box to the domain, I get this message:
> "The domain name HOMEAD might be a NetBIOS domain name. If this is
> the
> case, verify that the domain name is properly registered with WINS."
> Please, what should I do to solve this problem?
>
 
Re: networking problem!

Thanks for that quick reply :)

Right now it is configured like this on the XP:
ip 192.168.1.20
sm 255.255.255.0
dg router ip
DNS router ip

both default gateway and DNS using the same ip address, the ip address of
the router

I've tryed to set DNS to 192.168.1.30, but then I loose internet connection
on XP computer

any suggestions ????
 
Re: networking problem!

I guess the dns on the server isn't setup correctly or not running.


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Jeff" <it_consultant1@hotmail.com.NOSPAM> wrote in message
news:OyhWrEH%23HHA.2752@TK2MSFTNGP06.phx.gbl...
> Thanks for that quick reply :)
>
> Right now it is configured like this on the XP:
> ip 192.168.1.20
> sm 255.255.255.0
> dg router ip
> DNS router ip
>
> both default gateway and DNS using the same ip address, the ip address of
> the router
>
> I've tryed to set DNS to 192.168.1.30, but then I loose internet
> connection on XP computer
>
> any suggestions ????
>
>
 
Re: networking problem!

Set XP DNS settings to look at your DNS server. Set your DNS server
forwarders to ISP DNS servers.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Jeff" wrote:
> Thanks for that quick reply :)
>
> Right now it is configured like this on the XP:
> ip 192.168.1.20
> sm 255.255.255.0
> dg router ip
> DNS router ip
>
> both default gateway and DNS using the same ip address, the ip address of
> the router
>
> I've tryed to set DNS to 192.168.1.30, but then I loose internet
> connection on XP computer
>
> any suggestions ????
>
>
 
Re: networking problem!

What can I say? Well, I'll try to say thank you. Thank you for those great
tips. The problem is solved. Configring a forwarder on the DNS, and setting
XP to use my win2k3 machine as DNS server solved my problem....

This is just a home network I've set up at home. The reason I set it up is
that I want to learn about configuration of windows networks.. I'm happy now
because not only is the problem with my home network solved, I've also
learned from all those problems I had trying to configure it...

cheers

jeff
 
Re: networking problem!

Good to hear. You're welcome.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Jeff" wrote:
> What can I say? Well, I'll try to say thank you. Thank you for those great
> tips. The problem is solved. Configring a forwarder on the DNS, and
> setting XP to use my win2k3 machine as DNS server solved my problem....
>
> This is just a home network I've set up at home. The reason I set it up is
> that I want to learn about configuration of windows networks.. I'm happy
> now because not only is the problem with my home network solved, I've also
> learned from all those problems I had trying to configure it...
>
> cheers
>
> jeff
 
Back
Top