Server 2k3 with connectivity
Last response: in Networking
i have installed MS server 2k3 enterprise edition, given roles for DC, DNS and DHCP, gone to Applications server and enabled DTC, added my computer and one user yet, as far as i know i can see these items in AD clearly. Oh i had also finished to configure the DHCP scope. on my server the IP address is static(thats obvious), the prefered DNS server is 127.0.0.1....My problem though is;
when i connect the computer onto the switch (its a basic 3com 8port), it reads "limited or no connectivity"
please help me "what am i not doing right, what am i missing doing"
when i connect the computer onto the switch (its a basic 3com 8port), it reads "limited or no connectivity"
please help me "what am i not doing right, what am i missing doing"
More about : server 2k3 connectivity
Check your DHCP scope. With the way you have it configured, you'll need DHCP to hand out DNS and the default router.
On the client side, DNS will be your local DNS server. This should forward out to your ISP's DNS server if unable to resolve locally.
You'll want to set the default gateway to your router instead of to your server.
If you were able to get the computer to join the domain and create the computer account, DNS internally is working properly.
As far as the switch, you'll want your router plugged into the switch and your server plugged into the switch.
Make sure this is a switch.
And the most important take away on this: Make sure your router has DHCP disabled on it. Your server is doing DHCP so you don't need the router to do it.
Also, make sure your router and server do not have the same IP address. For home use your DHCP scope can be x.x.x.100 to x.x.x.254 as an example.
The router is generally 192.168.1.1 or 0.1 - depending on brand. The server could be something like 192.168.1.10. If you're not using the 192 subnet, 10.x.x.x is reserved for business use. Same concepts apply
On the client side, DNS will be your local DNS server. This should forward out to your ISP's DNS server if unable to resolve locally.
You'll want to set the default gateway to your router instead of to your server.
If you were able to get the computer to join the domain and create the computer account, DNS internally is working properly.
As far as the switch, you'll want your router plugged into the switch and your server plugged into the switch.
Make sure this is a switch.
And the most important take away on this: Make sure your router has DHCP disabled on it. Your server is doing DHCP so you don't need the router to do it.
Also, make sure your router and server do not have the same IP address. For home use your DHCP scope can be x.x.x.100 to x.x.x.254 as an example.
The router is generally 192.168.1.1 or 0.1 - depending on brand. The server could be something like 192.168.1.10. If you're not using the 192 subnet, 10.x.x.x is reserved for business use. Same concepts apply
Related ressources:
- ForumWin XP or Win server 2k3
- ForumIP conflict on 2k3 DHCP, new problem/old network
- ForumServer 2K3 Remote Desktop Access - is this right place?
- Forumdemote nt server and join 2k3 domain
- ForumProblem getting additional 2K DC onto 2K3 domain
- ForumTrust with 2k3 Server error
- ForumCan 2k3 server act as backup for 2k server ?
- Forum2k DC with 2k3 exchange server
- ForumWin 2k3 server and WinNT server on same network
- ForumOutlook 2003 and Exchange server disconnects
- ForumEffects of Group Policy of W2K and 2K3 Servers in the same..
- Forumexcel and wints 2k3
- ForumActive sync, MS Exchange 2k3 , WinCE sync problems.
- ForumOutbound Email Messages not processing w/SBS 2k3
- ForumPulling DHCP from Cable Modem instead of wireless router
- ForumConfigurig router with laptop
- ForumDisable Internet Access from server!
- ForumHow to change the computer name in xp connected with server
- ForumCan't ping Server
- ForumPrivacy / security with shared network connection
- More resources
Read discussions in other Networking categories
!
