Discussion Locked

What is need to see Nt servers and works

0 helpful
18 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have multiple lan segments with Novell and Nt 4.0 servers on them. The Novell servers have no problem seeing each other accross the routers, but the NT 4.0 servers cannot see each other accross the routers. I can ping the individual machines and can find them by ip address, but I cannot locate the domains. I have two domains on one lan segment which can see each other fine. Can anyone tell me what protocols need to be passed by the router besides tcp/ip?

18 replies

by yorkster

I believe ports 138 & 139 should be open also, I think cisco's iphelper does all this

by avachon

Hi, do you have wins set up for your nt servers? since you can ping the machines by ip address but not by netbios name, I think this is your problem. Without wins, the machines broadcast to find each other and broadcasts will not, in most cases, cross a router. You can also set up lmhost files, which is the same thing, but wins is the easier of the two (gui based and centralized). Hope this helps.

by calves

It could be that your cmos battery needs replacement.
Would be normal the system ask you to confirm the changes, if you battery died and everytime you turn your computer off, the date and time changes.

Good luck!

by sdfgsdf

the first thing i would check would be your gateway. make sure they are actually opinting to an intelligent device. check your trusts (i know, simple, but check them anyway or you might be real upset later), and make sure (assumming you use cisco routers) that you dont have any necessary ports closed blocking traffic.

by wmr029

We had this problem resolved for us by having our cisco router bridge our two subnets. (Note we have only the one domain but two distinct LAN segments)

by nsa13

Install WINS on both lan segments. Have the WINS servers push-pull client information to each other. Also, verify that your clients are set up to use the WINS server. If your using DHCP it shouldn't take more than a few minutes. If you can't 'locate the domains try to initiate a trust between both PDCs after setting up WINS.

WINS allows for Windows computers to register there NETBIOS name with this nameserver in order to resolve name querys.

Good luck!

by jaystar

The simplest way to solve this is set one of the Domain Controllers up as a WINS server. point all clients and other servers to it in the WINS section of the TCP/IP properties. If you are using DHCP, set the option in there for easy deployment. Inaddtion, you may want to change a few other settings now that you have WINS to reduce broadcast traffic:
Option 44 sets the WINS/NBNS Option
Option 46 sets the WINS/NBT node type (0x8 is the best option)

by jdroland

I'm not sure about that "Replace the battery", but most of the guys have the correct idea. # 7 gives you the details, but the one that gives you the port numbers should have been 137-139. The WINS is the answer because you aren't able to resolve by broadcast across your routers, therefore WINS is your only resolution! And I prefer the single WINS server over the multi-wins unless you have frequent down links, but obviously the clients couldn't get to something on the next segment anyway if hte link was down. That's just my opinion though, easier to manage, easier to clean up when that bozo in accounting renames their computer the same as your domain controller!

by michael mietlicki

It's not a protocol issue .. it's addressing. Ping the far side of the router and see if you get a response. First step.!

This discussion is closed to new replies.