Windows Forum

Ask something
Discussion Locked

Unable to browse native win2k domain

0 helpful
8 replies

by culizard

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a small test network setup in the following config:

1 Win2k DC of the reskit.com domain (IP addresses 192.168.0.1 and 192.168.0.201)

1 Win2k DC of the charles.reskit.com domain (192.168.0.3)

2 Win2k Pro machines (DHCP assigned addresses, currently 192.168.0.50 and 51)

All except the charles.reskit.com are logged in as the reskit.com administrator.

Also connected to the network, but not the domain are two WinNT boxes, one with a static address of 192.168.0.12 and the otherwith a DHCP address.

When I try to browse to the reskit domain through my network places, I get the following message:

"Reskit is not accessible

No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. "

A search of Technet only mentioned this error in regards to workstation issues, when 10+ inbound connections are made. I've checked licensing on my server, but it doesn't seem to have any problems. I am completely at a loss here... can someone help? Thanks!

8 replies

by pitsnake

go into Admin tools / Services ... and turn off "License Logging Service" .. then test and you will then be able to determine whether or not it is a licensing issue.

If it is you will need to supply the correct licensing information to the server. If it is not then there is a good chance that you do not have WINS properly configured, but I would bet 10 to 1 that the problem lies within licensing.

Good Luck,

Michael Ward, MCSE, MCP+I

by culizard

Michael,

I have already attempted to turn the license service off, and it has no effect. However, I haven't touched WINS yet; I thought DNS and AD would take care of all the name resolution, so I wasn't going to bother messing with it right now. What do you think it could be in WINS?

Steve Custer, MCSE, A+

by maxwell edison

Greetings,

There may be several issues you are dealing with. I would recommend reviewing the following Microsoft articles on Installing a Windows 2000 Server as a Domain Controller.

They'll offer a Step-by-Step Guide to a Common Infrastructurefor Windows 2000 Server Deployment. There are quite a few additional links to other related Windows 2000 server deployment documentation.

(REMOVE SPACES from the pasted URL.)

http://www.microsoft.com/windows2000/techinfo/planning/server/serversteps.asp

( By the way, I'm going through the same upgrade right now, and have found these articles extremely helpful, especially concerning the set-up for my test network.)
Good luck,

Maxwell

by culizard

That's good advice. Eventually I ended up rebuilding the DC, which worked, so I don't know if this would've worked or not, but you can have the points =)

This discussion is closed to new replies.