Loss Connections

[Guest]

We had a Novell Network. We now installed a Windows 2000 Advance Server. Since, we have been having lots of problems

1. It takes a long time for users to log into the domai
2. Our network for some reason will drop the connection. Once the users have logged in the drive mappings have a red x through them. Once I reboot evrything comes up
3. Some users can get to the internet. Others, I have to go to the computer management icon, click on services, click on computer browser and start the browser service

Can anyone help me. I am not a Microsoft guru so maybe I have not set something up properly

Thanks

 

[Jetro]

If you the Novell guru a setup wouldn'd be hard. Could you please, tell more
about the network (domain/workgroup) clients, protocols, the Internet
access, and Server configuration (DNS/DHCP/WINS/NICs)?

 

[SaltPeter]

We had a Novell Network. We now installed a Windows 2000 Advance Server.

Since, we have been having lots of problems.

1. It takes a long time for users to log into the domain
2. Our network for some reason will drop the connection. Once the users

have logged in the drive mappings have a red x through them. Once I reboot
evrything comes up.

3. Some users can get to the internet. Others, I have to go to the

computer management icon, click on services, click on computer browser and
start the browser service.

Can anyone help me. I am not a Microsoft guru so maybe I have not set something up properly.

Thanks

Sounds like a name resolution problem, unlike NT4 and Novell, W2K relies on
DNS name resolution primarily. I'ld verify the DNS server(s) for starters.
ipconfig, nslookup can help. If you deploy ip_addresses through dhcp,
specify the DNS server's ip_address in the DHCP scope options.

You need to pay carefull attention to how your DNS server is configured. You
should configure forwarders and delete the root zone as well as have the
clients use the private DNS server instead of an ISP's DNS server. This way
a client consults a local DNS which queries an external DNS server on behalf
of client (and intranet queries are therefore efficient).

This KB may help:
http://support.microsoft.com:80/support/kb/articles/q291/3/82.asp

DNS is critical to a W2K domain's efficiency.

 

[Guest]

We have 20 PCs connected to a switch. 1 Advance Server connected to the same switch. A 3com router which also acts as the DHCP server is connedted into the same switch. The ISP is providing the DNS.
DNS = sj.co
PDC = sj.local.com (Advanced Server

I was very confused as to setting up the domain controller. The ISP is hosting the DNS so I just added local on to it for the PDC. Is this a problem. All PC's are using the DHCP to obtained their IP addresses.

Any suggestions.

 

[Jetro]

Domain with AD must have local DNS server. Delete the root ('.') zone if it
exists, and better configure ISP's DNS servers as forwarders. Disable DHCP
server on the router, install/activate it on your server, configure (almost
everything in the scope should point on the server IP) and authorize. If
there are the downlevel (pre-W2k) clients, you need WINS and NetBIOS over
TCP/IP.
Some right-clicks and reading Windows Help would be well enough to advance.

 

[SaltPeter]

We have 20 PCs connected to a switch. 1 Advance Server connected to the

same switch. A 3com router which also acts as the DHCP server is connedted
into the same switch. The ISP is providing the DNS.

DNS = sj.com
PDC = sj.local.com (Advanced Server)

I was very confused as to setting up the domain controller. The ISP is

hosting the DNS so I just added local on to it for the PDC. Is this a
problem. All PC's are using the DHCP to obtained their IP addresses.

Any suggestions.

The ISP can provide DNS name resolution for public queries. But that DNS
server can't include private intranets since private ip_address scopes
aren't routable out there.

Think of it as a feature of DNS instead of a limitation. Your local private
DNS caches those queries forwarded to the ISP's DNS server. This occurs once
you remove the root zone and configure the forwarders appropriately. You are
in fact telling the private DNS server that it's not the final authority for
the global DNS namespace. Yet you can then delegate and organize your
namespace into DNS zones internally. Also, forwarding the query up to ISP
from private DNS server is quite fast even if the query isn't a cached
query.

Unlike Netbios domains, DNS gives W2K something that has been a proven
method of organisation since the very beginng of ArpaNet: a delegated
hierarchy.