Windows Forum

Ask something
Discussion Locked

NT Installation 101

0 helpful
9 replies

by wessir

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm not an administrator but I need some basic administrator knowledge. I need to set up a IIS development machine. I have a home network in which I can see all the computers in Network Neighborhood. I have a linksys cable modem router as the hub. I installed NT4 server and IIS on a new computer. Here's the problem; I can't access the new server from the other computers, I can't see it in network neighborhood, I can't find it in IE using it's name, I can't see any of the other computers from the server network neighborhood or any internet websites from the server IE. IIS is running and I can view the server's web pages from IE on the server. The link lights are on, why can't the other computer's see the server and why can't the server see the other computers?

9 replies

by mckaytech

The usual approach to troubleshooting this kind of problem is to start with connectivity and then solve any name resolution or browsing problems.

The first question is how you configured the IP address on the server. If you're not using your router to serve DHCP addresses, you'll have to set a static IP address on the same subnet with the same subnet mask.
Probably what I would do is go to one of the computers that is working properly, open a command window and enter "ipconfig /all" and carefully note the settings with particular attention to the IP, subnet mask and gateway.
Duplicate those settings on the server (except the IP address - choose one that is not already present on the system).

That having been done, then see if you can ping the other computers on the network and whether you can ping the gateway (should be the internal address of the router). If so, you're halfway there (or possibly all the way).

If you can ping all the way around, then the thing to check isthe domain/workgroup situation. Did you build this server as a member server or as a domain controller? If you built it as a domain controller, you'll have to add all the other computers to the domain for everything to work right.

Hope that helps you get started...

paul

by wessir

Wish there was an option "helped but didn't solve problem". This helped me narrow down the problem. The router is a DHCP server and connection does seem to be the problem. Trying to ping it from the server says "Destination host unreachable". The new server is set to receive an IP address from the DHCP server and is currently at 0.0.0.0 NT recognizes the NIC and it is started. The link lights are on, the cable checks out, what else should I check?

by nottooshabby

IIS machine? Please define. The first step to log into a domain, require that any PC running Win95, 98, or ME lists "Client for MS Networks" in it Network Control Panel. Click "Properties", check "Log on to Windows NT Domain" and enter the name of the domain of which your NT4 Server is the PDC. Upon boot up you will be advised if the log on succeeds of fails. Good luck.

by erickl

This will depend on the OS of "the other machines." All machines must share a common protocol that supports whatever you might be trying to do. If they are Win95/98, you will need to use the NetBEUI protocol, in my experience, to access via Network Neighborhood. In the environment that you describe, you won't find it in IE, by it's name, unless you are running a WINS server on the network (or can point to one that you can use.)

by mckaytech

If IPCONFIG on the server shows that the IP address is 0.0.0.0 and that DHCP is enabled, it is not receiving a DHCP address and that's where the problem is. At this point, there are a couple of possibilities: bad NIC or NIC driver or configurationproblem with the DHCP server on the router.

Depending on what router you are using, it may only support a limited number of IP addresses or it may have a narrowly defined scope and all the available addresses have already been issued.

I think at this point, I would see if an updated driver is available for the NIC and maybe try a set of static IP parameters to see if you can at least get the connectivity going. In the long run, I think you're going to want a static IP for the server anyway and now might be a good time to try one. Just be sure and pick an IP address that is outside the range of those being supplied by your router but is still within the same subnet.

paul

by wessir

I think you've helped me get to to the root of the problem. I can plug in anther computer to the router port and it works. The NIC is the no-name budget variety and highly suspect. Now that it is the main suspect I recall having some trouble withthe initial install. Will try your suggestions, thanks alot!

This discussion is closed to new replies.