It's like this: Internet > dsl modem > wireless router > port 1 widows server 2003 > port 2 computer1 > computer2 connects via wireless+server administrator > computer3 connects via wireless > etc. I want windows server to be a domain controller/dns server/dhcp server/ftp server/media server, is it possible with the current topology? | Gateway DX4710-UB301A | Intel Core2 Quad Q6700@2.66Ghz w/6 Gb's of ram | Western Digital 640 Gb HDD | Nvidia Geforce 9500 GT | Dynex Sond Card w/5.1 Surround and Optical Audio Out |D-Link DWA-552 Wireless Card | Windows 7 RC | Ubuntu 9.10 alpha 2

It depends. How I've done it is as follows:Internet <-> Cable / DSL Router <-> Server <-> Wireless Access Point / Router <-> ClientsNote: My server has dual gigabit ethernet connections. This is important since the server will function asrouter using Routing and Remote Access. I have the Cable / DSL router connected to the server gigabit ethernet port 1. This has my Cable / DSL issues DHCP assigned address. I have the Wireless Access Point connected to the server gigabit ethernet port 2. The server interface to the Wireless Access oint and the Wireless Access Point both have a static assigned IP address. These static IP addresses are not on the same network as the Cable/ DSL router.Let's assume that I used one of the reserved ranges for both of these networks as follows:Server, Cable / DSL Interface192.168.0.1 / 255.255.255.0Server, Wireless Interface192.168.1.1 /255.255.255.0This establishes that each interface of the server is on a completely separate network. The Cable / DSL network is not connected to the Wireless network except through the server.You'll now need to setup the following on the Server:- Active Directory Directory Services, including DNS- Change DNS, bind /listen to only 192.168.1.1 (the private interface).- Install DHCP,bind/listen to only 192.168.1.1 (the private interface).- Configure DHCP to hand out the correct scope options as follows: DNS: 192.168.1.1 Subnet Mask : 255.255.255.0 Gateway: 192.168.1.1Awesome! So my clients now use my server as their defautl gateway and the server is responding to DNS requests. I can route out to the internet! Nope, not so fast. The server is now multihomed but it's not routing anything. It sees a packet addressed for the internet show up on the 192.168.1.1 interface addressed for someone else and says "oh, that's not me" and ignores it. To use the server as a router, you have to install Routing and Remote Access.Microsoft has a good site for Routing and Remote Access complete with labs as follows:http://technet.microsoft.com/en-us/network/bb545655.aspxYou'll have to install the Routing and Remote Access (RRAS) role. nce you do:- Configure and enableRouting and Remote Access- Specify Network Address Translation (NAT)- Specify your pulbic address to the internet. This would be your DHCP assigned Cable/DSL router provided address.- Finish and go! Your server is now functioning as a software router to the internet!Notes:- The clients are never directly connected to the internet, all clients will route through your server to get to the internet.- Clients are NAT'ed behind your server.Some Additional Pointers:- Disable All NetBIOS related settings on the public interface. No "Client For Microsoft Networks", No "File and Printer Sharing",DisableNetBIOS over TCP/IP. Again, this is for thepublic (Cable/DSL router DHCP assigned) interface only! If you perform this ont he private interface your domain won't function as aa domain. You disable these because these will advertise the domain as such to the outside world.- Run a firewall/antivirus solution!

It is not recommendedfor the same server to beboth a Domain Controller and a router. I don't remember exactly why, but I did read this recently.On my home network, the servers and workstations are all on the same subnet, that provided by the wireless router. This router provides DHCP and NAT and connects directly to the cable modem. Although none of the wireless clients are in my domain at this time there is no reason why they couldn't be.

Are you referring to this article?http://support.microsoft.com/default.aspx/kb/908370These issues were supposedly resolved some time back and the article mentions how to overcome any problems.Agreed that the all-in-one role is not the best but going with the orignal posters specification of using the server as "domain controller/dns server/dhcp server/..." Imade the previous recommendation.I like having the wireless router face internally, this allows clients using file and printer services, netbios, etc. to be protected internally (sadly, WINS is still not dead and I don't want to stick a WINS server out on theinternet even NAT'ed)and provides some interesting things to do with the new Network Access Protection features in Server 2008.That andI have a ready made DMZfor any internet facing applications that I don't want to share the same subnet with my domain and domain clients.

The only problem is that I don't have 2 nic's, so right now, it is acting as a nas. Basically what I want to do is access my ftp server form the outside, more or less for school work etc.| Gateway DX4710-UB301A | Intel Core2 Quad Q6700@2.66Ghz w/6 Gb's of ram | Western Digital 640 Gb HDD | Nvidia Geforce 9500 GT | | Dynex Sond Card w/5.1 Surround and Optical Audio Out |D-Link DWA-552 Wireless Card | Windows 7 RC | Ubuntu 9.10 alpha 2 |

my server is just a nas at the moment w/ lan ftp server and media server capabilities| Gateway DX4710-UB301A | Intel Core2 Quad Q6700@2.66Ghz w/6 Gb's of ram | Western Digital 640 Gb HDD | Nvidia Geforce 9500 GT | | Dynex Sond Card w/5.1 Surround and Optical Audio Out |D-Link DWA-552 Wireless Card | Windows 7 RC | Ubuntu 9.10 alpha 2 |

Haven't read that article. See above posts | Gateway DX4710-UB301A | Intel Core2 Quad Q6700@2.66Ghz w/6 Gb's of ram | Western Digital 640 Gb HDD | Nvidia Geforce 9500 GT | | Dynex Sond Card w/5.1 Surround and Optical Audio Out |D-Link DWA-552 Wireless Card | Windows 7 RC | Ubuntu 9.10 alpha 2 |

Hi, If you just want to make users able to access the FTP server from the Internet, you do not need to install the AD DS role on the server. You can use the wireless router to publish the FTP server to the Internet. Thanks.