TheTechGuysNYC
asked on
Setting up a Windows Server 2003 Network... my situation. In need of URGENT help!!
I know about the whole "There is no such thing as a stupid question" thing, but this, is a stupid question. This is not the first network I have set up, yet the same processes that were successful before (or possibly I missed something... definitately a possibility) aren't quite as successfull this time. So I am asking for help as I am going in circles.
Basic Steps to set up a Windows Server 2003 network with 5 PCs and 1 laptop and a DSL modem connected to a switch as follows:
1) Server has 2 NIC cards: NIC #1 goes from server to Switch.
NIC #2 goes from server to DSL modem.
Therefore, I should think, the server is acting as a DHCP client which “hands” IP addresses out for a certain amount of time unless otherwise specified as infinite.
2) All other PCs are running Windows XP and are connected by a single Ethernet cable directly to the Switch. There is no router/hub etc.
Problem: cannot get the server or the PCs an IP address. Message “Limited or no connectivity” is now my worst enemy on the planet earth.
- I gave NIC #1 on the server a static IP address.
o Any suggestions for a particular IP address to assign to this server would be welcome…
Active Directory is functioning. It was set up via DCPROMO (new tree/forest and the server is domain controller) and all users are set up with non-expiring passwords (I edited the password policy to bypass the password complexity requirement as per request by the customer). I had DHCP enabled and authorized and set up a scope of 192.168.2.100-120 for the addresses to be handed out. Before getting to the point where I even bothered excluding any IP address other than the server’s, I stopped and clear all my progress up until that point because something is wrong. I had DNS working.
The Network was functioning fine when given Static IP addresses which, quite obviously, though not to me, that something is not configured properly. It is this “something” that is stopping me from finishing off this network, which currently is in ruins. There are NO firewalls running at the moment (when I get the network up and running they will be installed and configured).
Before I left, I removed all services: DHCP, DNS, Print Server, File Server, etc. to start from scratch. I left the Active Directory.
I would like the server to allow ICS (stupid question, but should I use a router to provide internet?)
Any other questions.. please feel free.
Basic Steps to set up a Windows Server 2003 network with 5 PCs and 1 laptop and a DSL modem connected to a switch as follows:
1) Server has 2 NIC cards: NIC #1 goes from server to Switch.
NIC #2 goes from server to DSL modem.
Therefore, I should think, the server is acting as a DHCP client which “hands” IP addresses out for a certain amount of time unless otherwise specified as infinite.
2) All other PCs are running Windows XP and are connected by a single Ethernet cable directly to the Switch. There is no router/hub etc.
Problem: cannot get the server or the PCs an IP address. Message “Limited or no connectivity” is now my worst enemy on the planet earth.
- I gave NIC #1 on the server a static IP address.
o Any suggestions for a particular IP address to assign to this server would be welcome…
Active Directory is functioning. It was set up via DCPROMO (new tree/forest and the server is domain controller) and all users are set up with non-expiring passwords (I edited the password policy to bypass the password complexity requirement as per request by the customer). I had DHCP enabled and authorized and set up a scope of 192.168.2.100-120 for the addresses to be handed out. Before getting to the point where I even bothered excluding any IP address other than the server’s, I stopped and clear all my progress up until that point because something is wrong. I had DNS working.
The Network was functioning fine when given Static IP addresses which, quite obviously, though not to me, that something is not configured properly. It is this “something” that is stopping me from finishing off this network, which currently is in ruins. There are NO firewalls running at the moment (when I get the network up and running they will be installed and configured).
Before I left, I removed all services: DHCP, DNS, Print Server, File Server, etc. to start from scratch. I left the Active Directory.
I would like the server to allow ICS (stupid question, but should I use a router to provide internet?)
Any other questions.. please feel free.
ASKER
Yea, they are, but not even the server is getting an IP address. I will try using the patch.
I think I have to totally restart the networking process from scratch. Any ideas? Keep throwing them at me. If you need more info let me know
I think I have to totally restart the networking process from scratch. Any ideas? Keep throwing them at me. If you need more info let me know
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have to agree with DeadNight on buying a router for your network. Not to "steel his thunder" but just to add the link below which points out many of the associated problems with using ICS. It also interferes with RRAS if you ever want to set up a VPN on the server.
Following refers to XP, but problems are similar. See the section near the bottom entitled "Problems"
http://www.petri.co.il/configuring_ics_on_windows_xp.htm
In addition the "Limited or no connectivity" message is likely due to your DHCP server not running and or configured properly. You have a physical connection but no TCP/IP connectivity, due to IP assignment.
You need to re-install the services you removed. You say you removed DNS, DHCP, and file and print, and left Active Directory? No DNS, no Active Directory. You might even want to do a clean install if you haven't gone too far.
If adding a router you can configure this with a single network card. When setting up your network adapters an important point with DNS is only point your workstations to the Domain Controller as a DNS server (not the ISP's DNS or the router) and the same for the server, point it to itself. The ISP's DNS IP's should be entered as DNS forwarders in the DNS management console.
Following refers to XP, but problems are similar. See the section near the bottom entitled "Problems"
http://www.petri.co.il/configuring_ics_on_windows_xp.htm
In addition the "Limited or no connectivity" message is likely due to your DHCP server not running and or configured properly. You have a physical connection but no TCP/IP connectivity, due to IP assignment.
You need to re-install the services you removed. You say you removed DNS, DHCP, and file and print, and left Active Directory? No DNS, no Active Directory. You might even want to do a clean install if you haven't gone too far.
If adding a router you can configure this with a single network card. When setting up your network adapters an important point with DNS is only point your workstations to the Domain Controller as a DNS server (not the ISP's DNS or the router) and the same for the server, point it to itself. The ISP's DNS IP's should be entered as DNS forwarders in the DNS management console.
ASKER
My Status:
Network is up and running. The sever is functioning properly. There was a problem with DNS and DHCP was unauthorized even though I can specifically remember authorizing it. The only thing is, the clients have no internet access, even though the server does... (Also, is there a way to have the server connect automatically to the internet when logging on? maybe some kind of script? A setting?
Both NIC cards on the server have static IP addresses at the moment, those both ending in 100 and 101. but for some reason, there is no option for adding ICS... Only the "Settings" button for Windows Firewall is there. Also, at this point in time each client cannot connect to the internet, even via connecting on their own.
i do want to learn how to use ICS, which is why i am doing it.
I am thinking about going for the router option. In doing so: 1) I will only need 1 NIC card 2) It will handle the internet and all clients will have access without having to dial up on their own.
The connection will go as follows, correct me if I am wrong: DSL modem to router, router and server to Switch. No?
Network is up and running. The sever is functioning properly. There was a problem with DNS and DHCP was unauthorized even though I can specifically remember authorizing it. The only thing is, the clients have no internet access, even though the server does... (Also, is there a way to have the server connect automatically to the internet when logging on? maybe some kind of script? A setting?
Both NIC cards on the server have static IP addresses at the moment, those both ending in 100 and 101. but for some reason, there is no option for adding ICS... Only the "Settings" button for Windows Firewall is there. Also, at this point in time each client cannot connect to the internet, even via connecting on their own.
i do want to learn how to use ICS, which is why i am doing it.
I am thinking about going for the router option. In doing so: 1) I will only need 1 NIC card 2) It will handle the internet and all clients will have access without having to dial up on their own.
The connection will go as follows, correct me if I am wrong: DSL modem to router, router and server to Switch. No?
ASKER
What i want, in the end is: 1) The server to have acces to the internet without having to start the connection manually i.e. automatically. 2) The clients to have access to the server (obviously :)) via DHCP. **This has been accomplished. 3) The clients to have access to the internet upon logging on to the server without having to connect themselves.
As I said aove, there is no option for ICS for som reason. Maybe there is something that I am missing? If worst comes to worst i will use a router (if you would be so kind, provide a short, concise description on setup of the hardware and any changes that need to be made just so I know I did everything correctly).
As I said aove, there is no option for ICS for som reason. Maybe there is something that I am missing? If worst comes to worst i will use a router (if you would be so kind, provide a short, concise description on setup of the hardware and any changes that need to be made just so I know I did everything correctly).
1) The server to have access to the Internet without having to start the connection manually i.e. automatically.
Is this a PPPoE connection?
What version of Server 2003 are you running?
ICS is only available on Standard Edition and Enterprise Edition. It is not included with Web Edition Datacenter Edition, or the 64-bit versions of the Windows Server 2003 family. I am not sure about SBS.
As an alternative you may be able to configure using the NAT option of Routing and Remote Access. Router is still a better idea :)
Is this a PPPoE connection?
What version of Server 2003 are you running?
ICS is only available on Standard Edition and Enterprise Edition. It is not included with Web Edition Datacenter Edition, or the 64-bit versions of the Windows Server 2003 family. I am not sure about SBS.
As an alternative you may be able to configure using the NAT option of Routing and Remote Access. Router is still a better idea :)
ASKER
Well, I solved it myself. It is kind of a cheap work-around, but I just made each computer connect automatically by itself when logging on via a shortcut placed in the startup folder :) (I also had to take away the prompt for user name/passsword).
In answer to your question: Yes this is a PPPoE connection. And I am running Server 2003 Standard Edition
In answer to your question: Yes this is a PPPoE connection. And I am running Server 2003 Standard Edition
ASKER
i would still, though I figured out a work-around, like to know how to do it otherwise. Thanks for everyone's help. It is really appreciated!!!!!
I'm not sure how you would force the PPPoE connection to automatically initiate. On a workstation the connection software is usually added to the start menu. However with a server there may not be any log on, therefore you would have to set it up as a service, not a "best practices" idea for a server environment Internet connection.
Once started though there should be an option in the connection properties to set it to "always on" or "keep alive"
As for ICS it might not be available by default as you should not enable ICS a domain controller, DHCP server, or DNS server. Better option would be to enable NAT using RRAS (Routing and Remote Access). I have also heard of people creating a bridge between the two adapters, but never tried it.
To enable NAT open the RRAS management console, right click on the server name and choose "configure and enable RRAS". This starts the configuration wizard, choose NAT. Then just follow the wizard. You will be asked as to which adapter is to be the WAN and which the LAN.
The router still seems the better option as it will better manage your PPPoE connection for all users.
Once started though there should be an option in the connection properties to set it to "always on" or "keep alive"
As for ICS it might not be available by default as you should not enable ICS a domain controller, DHCP server, or DNS server. Better option would be to enable NAT using RRAS (Routing and Remote Access). I have also heard of people creating a bridge between the two adapters, but never tried it.
To enable NAT open the RRAS management console, right click on the server name and choose "configure and enable RRAS". This starts the configuration wizard, choose NAT. Then just follow the wizard. You will be asked as to which adapter is to be the WAN and which the LAN.
The router still seems the better option as it will better manage your PPPoE connection for all users.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sounds good... there are no changes that must be made on the server itself?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
TheTechGuysNYC, have you been able to resolve the various issues?
--Rob
--Rob
Are those ws running XP SP2?
The link below probably can help you out with limited connectivity error.
http://www.pchell.com/support/limitedconnectivity.shtml
HTH,
Reffandy