Networking Forums

Networking Forums > Computer Networking > Windows Networking > Netbios broken cross-forest for win2k?

Reply
Thread Tools Display Modes

Netbios broken cross-forest for win2k?

 
 
Per-Torben
Guest
Posts: n/a

 
      04-13-2007, 07:40 AM
Hello everyone.

I really hope I could get some help here.

the network is made up by 2 forests (old and new). Everything is on the same
network (/23 net) and we don't have WINS.

Last night we shut down the 2k3 based DHCP server in the domain in the old
forest and made a a new dhcp server on the new domain. Everything went
smoothly and we resolved some dns-bugs by doing so.

However today none of our win2k clients (who are in the new domin) can
connect to our file server (which is still on the old domain) by it's netbios
name, but IP and DNS works perfectly. All the XP clients are working
perfectly and can resolve netbios names in both forests. They can resolve
netbios names in the new domain however.

Since all out logon scripts points to netbios name it's rather bad.

Please, any help or tip here is greatly appriciated.
--
regards
Per-Torben Sørensen
 
Reply With Quote
 
 
 
 
Lanwench [MVP - Exchange]
Guest
Posts: n/a

 
      04-15-2007, 11:47 PM
Per-Torben <(E-Mail Removed)> wrote:
> Hello everyone.
>
> I really hope I could get some help here.
>
> the network is made up by 2 forests (old and new). Everything is on
> the same network (/23 net) and we don't have WINS.
>
> Last night we shut down the 2k3 based DHCP server in the domain in
> the old forest and made a a new dhcp server on the new domain.
> Everything went smoothly and we resolved some dns-bugs by doing so.
>
> However today none of our win2k clients (who are in the new domin) can
> connect to our file server (which is still on the old domain) by it's
> netbios name, but IP and DNS works perfectly. All the XP clients are
> working perfectly and can resolve netbios names in both forests. They
> can resolve netbios names in the new domain however.
>
> Since all out logon scripts points to netbios name it's rather bad.
>
> Please, any help or tip here is greatly appriciated.


What's separating the two domains?
Are you seeing browser election problems?
Is there any reason you don't want to use WINS?


 
Reply With Quote
 
Per-Torben
Guest
Posts: n/a

 
      04-16-2007, 06:58 AM

--
regards
Per-Torben Sørensen


"Lanwench [MVP - Exchange]" wrote:

> Per-Torben <(E-Mail Removed)> wrote:
> > Hello everyone.
> >
> > I really hope I could get some help here.
> >
> > the network is made up by 2 forests (old and new). Everything is on
> > the same network (/23 net) and we don't have WINS.
> >
> > Last night we shut down the 2k3 based DHCP server in the domain in
> > the old forest and made a a new dhcp server on the new domain.
> > Everything went smoothly and we resolved some dns-bugs by doing so.
> >
> > However today none of our win2k clients (who are in the new domin) can
> > connect to our file server (which is still on the old domain) by it's
> > netbios name, but IP and DNS works perfectly. All the XP clients are
> > working perfectly and can resolve netbios names in both forests. They
> > can resolve netbios names in the new domain however.
> >
> > Since all out logon scripts points to netbios name it's rather bad.
> >
> > Please, any help or tip here is greatly appriciated.

>
> What's separating the two domains?
> Are you seeing browser election problems?
> Is there any reason you don't want to use WINS?
>
>
>

Nothing's seperating them routing-wise that's why I'm confused about this.
No reason that we're not using WINS except that I've been in this job for
less than 2 weeks, os thi was set up long before my time.

Hotfixed it by using WINS.
 
Reply With Quote
 
Lanwench [MVP - Exchange]
Guest
Posts: n/a

 
      04-19-2007, 09:53 PM
Per-Torben <(E-Mail Removed)> wrote:
>
>> Per-Torben <(E-Mail Removed)> wrote:
>>> Hello everyone.
>>>
>>> I really hope I could get some help here.
>>>
>>> the network is made up by 2 forests (old and new). Everything is on
>>> the same network (/23 net) and we don't have WINS.
>>>
>>> Last night we shut down the 2k3 based DHCP server in the domain in
>>> the old forest and made a a new dhcp server on the new domain.
>>> Everything went smoothly and we resolved some dns-bugs by doing so.
>>>
>>> However today none of our win2k clients (who are in the new domin)
>>> can connect to our file server (which is still on the old domain)
>>> by it's netbios name, but IP and DNS works perfectly. All the XP
>>> clients are working perfectly and can resolve netbios names in both
>>> forests. They can resolve netbios names in the new domain however.
>>>
>>> Since all out logon scripts points to netbios name it's rather bad.
>>>
>>> Please, any help or tip here is greatly appriciated.

>>
>> What's separating the two domains?
>> Are you seeing browser election problems?
>> Is there any reason you don't want to use WINS?
>>
>>
>>

> Nothing's seperating them routing-wise that's why I'm confused about
> this. No reason that we're not using WINS except that I've been in
> this job for less than 2 weeks, os thi was set up long before my
> time.
>
> Hotfixed it by using WINS.


There ya go.


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Adding NetBios to Win2K and Win 7 ??? JD Home Networking 0 08-12-2010 03:20 PM
Cross forest login failure melts Windows Networking 0 09-23-2005 10:09 AM
How to:DNS and IP for forest to forest explicit one-way trust 2000 server mp Windows Networking 0 07-05-2004 09:09 AM
Use of NetBIOS name while Installing Win2K Adv. Server as Domain Controller Pankaj Windows Networking 2 04-12-2004 11:37 AM
Cross forest/domain drive mapping Diane Windows Networking 0 11-24-2003 03:18 PM



1 2 3 4 5 6 7 8 9 10 11