Window Server 2003 Enterprise Help.

Hey,
You might say I'm a little young to be playin around with this but, oh well. Anyways, I'm getting awfully bored, and decided to use my old Desktop as a Home Server for backups/testing TS and the like.
Anyways, I have installed Win Server 2003 Enterprise, and have added the following roles:

• 
  File Server
  Application Server
  Mail Server
  Terminal Server
  Domain Controller(Active Directory)
  DNS Server
  DHCP Server
  Streaming Media Server
  anddd WINS Server(I honestly have no clue what this is, but it sounded cool. lol)

Now the question is, I have a router that has NEVER been used, I have a direct connection from the Desktop/Server to the WAN port of the router, and another connection from the LAN ports to my laptop, I have added my Laptop to AD and a username. When I go into the Connections, I hover over the Ethernet and it says "Limited or no connectivity" I have tried 2 different Ethernet Cables, and nothing seems to work. Do I need to configure the router for it to all work? Or do something to the server to make it work? LOL.
I'm really stuck here, and I'm getting FRUSTRATEDDDDD! I'm almost tempted to throw XP back on it and sell it! Any Help would be appreciated! Oh also, would a Windows Server 2003 for Dummies book Benifit me? I would like to learn all this before I buy a proper server, and before I spend a rediculous amount of money on Networking Gear.

 

There's probably a firewall on the wan port so put the server on one of the lan ports.

 

thats true, the router has inbuilt firewall.

 

The Service pack 2 for server 2003 has had some bugs and in some cases it would render your network capabilities useless.
if you have sp2 for server 2003 installed you might wanna read this, maybe it helps :

http://support.microsoft.com/kb/936594/

 

Uh, when you connect your home server to the WAN side of the router, have you manually configured all of the IP stuff - like manually entering an IP address for it to use, or did you just set it up to defer to any other DHCP server that might be on the network? The router itself is not going to be dishing IP numbers via DHCP out to the WAN side of the router. Also, why do you have the home server set to act as a DHCP server - the router is doing that role right now.

If you want the home server to take over the role of main network controller, then what you really need is something like a hub or a switch, something "dumb" and not a router.

 

Exactly--your server has no ip address and it is as if it is the internet. Your router cannot direct traffic out to the server (internet) because the router has no information of the outside world.

We need a better idea of what you are trying to accomplish.

Put the server on a LAN port and allow the dhcp to be handled by your router. If you really want to set up your server to handle DHCP duties, disable that function on the router, but then you need to set the information in the server to route out to the gateway (your router).

Make sure the router and server are in the same network, but set the dhcp range so that the router/gateway is not within the range.

 

I'm pretty sure the problem is the DHCP and DNS service running on the 2003 server. You r laptop is getting its setting from that, however, it is likely you haven't told your 2003 server to direct outbound packets to your router which will direct it to the Internet.

This can be fixed by running the ICS service on the 2003 server

edit:

I don't recommend this path as it will cause problems with Active Directory. The 2003 DNS server needs to be a listed DNS server otherwise you'll run into problems.


@OP

A 2003 dummies book will help intensly. You need to at least understand the basics of TCP/IP and the OSI model.

BTW, WINS server is a service that converts NETBIOS names to IP addresses. It can be useful, I'd turn it off till you know what you are doing. File server won't hurt anything really. Application, Mail, and Terminal server may cause some confusion later but you should be ok.

 

Where did I say anything about DNS? I said DHCP. And I said he can let the router hands DHCP, but if he wants to he can put that role on the server.

In a large environment you normally have a different server handle DHCP duties and authorize the DHCP server on the DC (prevent hijacks).

Yes, you can do all three roles on one server in a small environment if you wish, but on a busy network you're asking the DC to do a lot of work, especially if you have short DHCP lease times.

 

Yuh, I'll go and get a switch sometime this week.

 

Your router has a built in switch. If you just use the LAN ports (well, assuming you have more than 1) you don't need to buy a switch or hub (ugh--no hub--too many collissions)

 

Well, computers get their DNS servers from the DHCP. And he mentioned he added his laptop to the AD, so the server's DNS server will be necessary to point the laptop to the logon server (which happen to be the same machine in this case.) And that is just the beginning.

The server 2003 DNS server is crucial for a functional Active directory domain which is why DNS comes into play.

You won't need a switch IMO. Your current option will work. Another option is to use the above method of having the router's DHCP service dish out the IP addresses, but have the 2003 DNS server as the primary DNS. Then have the 2003 DNS service forward outside queries to the ISP's DNS server, which is a little complicated. They'll have to be on the same network segment. Since I'm sure that didn't make any sense, I had earlier recommended you do not follow this route.

Again, the easiest way would be to plug your 2003 server into the router and the laptop into the server 2003. Then enable Internet Connection sharing on the Server 2003.

yeah, considering these days a small switch will be the same price as a hub.

 

Yeah...and?

I never said he shouldn't do it...I just said there are other ways of doing.

He also said this is an old computer...overloading and old computer with too many roles will result in a slow network.

You're taking one half-described point I made and running wild. My original post said that if you want to do it your way, just make sure you set the gateway properly in the DHCP scope.

Ultimately, you are probably right--he's setting up a little two or three device computer lab and he's not likely to be overloading it, but my point I was trying to make is that the best practice is to separate some functions. It is perfectly normal and indeed preferred to setup a dhcp server on a separate machine and authorize that server in active directory.

 

Yeah, I think I misread the OP's post. I failed to notice the WAN port plug in from his laptop and router to the 2003 server. That's an interesting connection. So if I understand it correctly the network goes: Internet/2003/router/laptop??

Kind of an odd connection for his network....

 

Ah, just a mistake he made. We need to get him another router and then he can setup a vpn connection from his laptop and computer to his server on the other side of the psuedo-cloud....

I'm giving myself a headache.

I always over complicate things....

 

Oh boy, a VPN connection across two feet of physical space. Might as well add a couple more hops to it to flesh it out.

 

Theres currently no internet on the 2003.
I've found a cheap switch on ebay here

 

Ah man. If there is no internet, then that explains the whole "limited or no connectivity." That error message is refering to Internet connectivity.....

:facepalm:

 

ahh, right. but i still have the problem of my computers not being able to find the server; or will the internet fix that?

 

If you were able to add it to the AD, then you should be able to see the server.

If you are trying to access shared file folders then that may be a whole 'nother issue. BTW, I couldn't tell. Is DHCP turned on or off on the router?

 

ok, im having much more luck connecting via the main wireless router, i can now connect to the server from the computers, but, i want just my computers to have access, and no one elses, and have the wireless connection, just as an internet connection, and use my own wired router for my computers, if that makes any sense.

 

Makes perfect sense.

Setup your wired network as a separate network segment, which means giving the wired ethernet ports an address like 192.168.10.x. You can either do it through DHCP or have to make them static depending on how your network is laid out.

If that doesn't makes sense, well, draw out how your network is laid out and we'll help ya out there.

To prevent access to the files, just set the share priviledges to allow only Domain accounts to access them. You can't complete hide the share. You can only enable password protection.

 

Ok. Heres my home network setup. Everything past the server is mine.

 

Well, your server's wireless connection is going to be assigned an ip adress like 192.168.1.x.

If your router has DHCP on, then turn it off. Have it turn into "bridge" mode or "gateway" mode. Whatever it may be called.

Next setup your Server 2003 DHCP service to run on the wired ethernet connection on the server. It will next ask to assign it a fixed IP address. Give it an address like 192.168.2.1 or whatever you had it to begin with.. Now it will ask for DNS server and gateway settings.

For your primary DNS server, have it direct it your server, which will be 192.168.2.1 or whatever you had it to begin with. Next find out the IP address your wireless connection is on. That IP address will work for your secondary DNS server and your Gateway settings.

Your subnet setting will be 255.255.255.0 unless you came up with a private class A/B network.

Lastly it will ask for scope settings. put down a scope setting of 192.168.2.2 - 192.168.2.250.

I can't remember what else it asks you.

Next setup Internet connection sharing by right clicking your wireless connection under Network Connections. There might be other steps I can't remember. That should get it started though. Try that.

 

Is your server really multi-homed?

 

I dont understand what this means.

Do I need to buy a switch?, if so, I'll buy one now, if not, I'll buy something else. LOL. BTW it wont be something of quality, becuase, I am 15, and have no income, except from what I sell. I have 20 bucks left :/ That is enough to buy a switch off eBay though...

when i am just connected to the wired router, i cannot access the router config, its like it cannot see it, even though, it is connected, and both the wireless and wired router have the same access i.p, 192.168.1.1, so when i type that in, it goes to the wirelss config.

 

In this case, turn off your wireless connection. Open your browser and then try to access 192.168.1.1

Yes it is a multi home server.

 

Your picture shows your server connected to the router and the wireless router. A multi-homed computer has two network interfaces. Does the server have two network interfaces?


You have got to learn to walk before you can run. You are just throwing this thing together without some basic knowledge and without a clear sense of direction is the problem. I admire your chutzpuh, but that is a recipe for disaster.

What is the ultimate goal here? Which computers are going to be part of your domain? Is that really what you want? Are all these computers there to do with as you wish, or are they family members who will get really pissed off when their user profiles seemingly disappear or cannot log into their computers? What exactly are the makes and models of these routers?
You may not need any more equipment, but you need a plan.

This could take hours to workout and that is if you, surfasb and I were all sitting in your basement drinking Jolt cola (do they still make Jolt?)

I feel like we are three blind men each holding a different part of an elephant.

I think I'm too tired for this tonight...

 

Maybe we could all take turns RDP'ing in and mucking around in serial fashion!

 

All the computers in the network map are not mine, only the ones past the server. I only want the server to affect the Computers past the server. I want to use the Wireless Router for the other house, and have the wirelss feed my server internet, to dish out to my computers via corded ethernet. Wireless Router is a NetComm BP504UK, and the Wired in my room, is a ZyXel Prestige 334 Firewall Router. If this is all going to be trouble, I can accept that it wont work the way I want it, and will give up. But, I have accomplished one thing, I can connect to the server, and vise versa.

 

And what do you mean by affect the computers past the server?

 

Most computers theses days are multi homed. A wireless connection and a wired connection available on a desktop isn't all that shocking theses days, would you think?

I personally would encourage the kid to setup his own domain. Even without a book it isn't that hard. Get the 2003 server up, add a few computers and user accounts and he's ready to go.

I do encourage however that at the very least you read up on TCPIP and the OSI model. Wikipedia will teach ya the basics.

@OP

So how far into my previous post did you get?

 

I just want to know what he has exactly so I can make informed suggestions.

While not exactly rare, I don't see that many desktops that are multi-homed--especially olders ones, which he stated earlier.

If it is, though, it does make a big difference regarding our earlier discussion. Now the server really must be the DHCP server, as well as a router.

Ideally, we essentially need two separate networks from his albeit basic description (based more on location than necessity). The network for the other computers and the network for his little domain. The NICs need to be set up to attach to two different networks, and the server needs to route between them for this all to work.

It's messier and needlessly more complicated for his little computer lap.

I would set it up differently than what he has drawn, but I don't have time right now to go into details and will have to return to this later if you guys haven't worked out the details.

 

I assume to connect to the wireless router on the previous picture, he's using a wireless adapter. Not exactly out of the ordinary.

And, well, he already installed the DHCP role so that isn't a biggie.

He has already stated he wishes for this configuration.

 

Is the server going to be on all the time (24/7)?

 

Ok. Just to clarify things a little better, for me, and for you, I'll tell you what I have, What I have accomplised, and What I want to accomplish.

What I have:
-Acer Veriton 3600g running Windows Server 2003 Enterprise Edition
-NetComm NB504UK Wireless Router, running Internet Connection
-ZyXel Prestige 334 Firewall Router
-A Bunch of computers

I have 2003 Enterprise installed on my old desktop to run as the server, I have my laptop, and a heap of other computers throughout the house, though, that arent mine, still can be used to test a few things. I currently have the following role's installed:
-File Server
-Application Server
-Terminal Server
-Domain Controller (Active Directory)
-DNS Server
-DHCP Server
-Streaming Media Server

What I have accomplished
I have successfully ran the server, via the Wireless Connection, I can connect to TS from all computers using my AD Login, and can access shared folders that were setup. What I have accomplised, is pretty much what I expected plus more to do on this thing! I can successfully manage Active Directory without direct help from books, etc. The Mail/POP3/SMTP server was easy to manage, but got too complicated in the end, so I thought I'd leave that for another day.

What I want to accomplish
All what I've said seems as though I have it all pretty well worked out, but I would like it to work on my own Wireless or Wired Network, in my room. I can, however, use the server over the main wireless router. The Server will be on 24/7 providing a backup for certain folders. Terminal Services isnt a huge drama, as I would barely use this anyway - it's mainly used for software testing. One thing I would like to do, is, use clickview, and put all my movies/videos etc on the clickview server, and be able to access them from my computers - or, learn how to use the Streaming Media Server. I'd also like to run a print server - fairly simple, but I just havent gotten around to installing my printer. One other thing, I would love to be able to have a sharepoint site, again, no biggie, but something I would like to have.

Anyway, thats pretty much my plans

Cheers.

 

Well, we see that it works on your wireless network.

I assume the laptops connected to the server can see each other?

If that is the case, it is a simple matter of internet connection sharing, which I said before.

 

Well, I am glad the OP has what he wants now, but I still don't understand why you don't just turn off DHCP on the router, set up the server with AD, DNS,DHCP, and put them all on the same network with one wireless router.

The, he adds only his machines to the domain, but the others still will pick up the DHCP info. Every works, people who don't wish to be on the domain still have internet access. The only drawback is the server needs to be on all the time, but he said he was going to do that anyway.

You might even be able to print to the printer from all computers on the network that way, rather than just those on the smaller separate network.

 

It is quite possible he may not have direct control of the wireless routers.

I do agree the server should handle DHCP duties for his two laptops in the domains.

I don't see the point of taking over DHCP from the wireless router when those computers are on a separate network.

 

I confess that never occurred to me.

What I was trying to say is that he really doesn't need two separate networks (as in different ip ranges). He can use a single ip range offered by the server (so he can learn about dhcp server functions on Windows 2003) but separate the two groups of computers into Domain computers on non-Domain computers.

The non-Domain computers will still pick up dhcp info even if they are not attached to the domain.

I dunno...doesn't really matter. Just less work.

 

That would work, but I think he's specifically said he wants two separate networks. So there is that. Honestly, setting up DHCP isn't any more complicated than learning IP addressing. So I don't see the need for a comprehensive DHCP scope setup to learn DHCP functions.