Anilrgowda

Id like to allow people to work from home by remoting into the office using terminal server, the current set up is this

internet
netgear router (links from the wall to the router, from the router to the win server with isa/exchange)
win server 2003 (with isa 2000 / exchange 2003 for giving the office internet and email)
win server ( domain controller)
XP Pro (client machines)

Is it possible to set up a 3rd win 2003 server with TS on it and make remote desktop connections from outside the office to that machine, and can you help point me in the direction of how to do that.

Anilrgowda

i had a look at the cisco 870 it will do what you want. Having said that Cisco is a world in its own, they are certainly one of the best products on the market but configuring them is like nothng else and is certainly not simple. While you may learn enough to get it up and running, what happens in two years time when you need to change something, you will have to re-learn it all as you wont retain that much info. (having said all that i have heard that some of the low end cisco do have a http gui, so maybe this is one)
for your cenario i would recomend the watchguard as configuring and managing will be a lot more simple.

"isnt there a cap of only 2 remote connections onto a xp machine at once?"
No the cap is 1, 2 on SBS (and must be administrators), as many as you have licence for on Terminal server .

Just about all makers of routers will have a low end product that will do what you want (Netgear, Dlink, Linksys, ...) if you call them direct they will be able to recommend a model that you can then price.

"Netman you said about redicting the port, this one of the things i really cant my head around. I can see how TS or VPn to our main internet server would work, i just unlock the port and forward it to that server. But as i said in my first post, the router only connects to that machine, so how i can tell the router to forward all port to internte machine then tell that server to forward everything to another one."

Not sure if you need ports explained a bit better for you so here goes,
Think of ports like doors into a building, and the servers are the buildings, and the router is the concierge for all the buildings it looks after. Each door gives access to certain things (Web pages = door 80, File transfer = door 21, Terminal Services = door 3389,....). Therefor when a request comes in from the outside world they go to the concierge (Router) and request access to a particular door (port) the concierge then directs them to the buiding (server) that has that door open. The problem with just forwarding everything to one server is that you must then run around and ensure that all the doors that you dont want people to break in through are locked, and you must do this all the time as you may get a patch that suddenly unlocks that door, or allows someone to easily pick the lock. Therefor if the concierge (router) doesnt let them to the door it makes life a lot easier.
That is the easiest way i have found to explain it as it lets you relate to a physical world scenario.