win2k document

[Matt Helm]

http://www.microsoft.com/downloads/details.aspx?
FamilyID=7424168e-f745-4450-b671-
aac2c79568eb&displaylang=en

Well this is great! if your have windows 2003. Is there a
similar document for win2k?

Thanks
helm

 

[John Lewis]

http://www.microsoft.com/windows200...2000/en/server/help/sag_RRAS_scen_pptp_bo.htm

Shorter link:

http://shorterlink.com/?X44AYX

Also, the 2003 docs are applicable in most situations. Few configuration
differences, but the theory is the same.

 

[Matt Helm]

Thanks

I noticed that this article explains something called
dial on demand routing with a corp office and branch
offices.

Do this work both ways with initiating?

I have two small offices that need to be connected
seemlessly. Would this mean that one office could see the
offices workgroup and shares in there network
neighborhood?

 

[Bill Grant]

Well, yes and no. Setting up a router-to-router link between two sites
gives you IP routing between the two sites.

Name resolution (and browsing) is a separate issue. Basically you now
have two sites connected by an IP router (a slow one). Name resolution
across the link will depend on your DNS and/or WINS setup. Network
Neighborhood depends on the computer browser service, so the same conditions
apply as in any other routed network. To build a merged browse list, you
must have at least one PDC (or its W2k/W2k3 equivalent) . You also need some
way for the segment browse masters to see each other using their special
Netbios names. This usually involves running WINS(either one WINS server for
the combined network or WINS servers in each site replicating across the
link). See KB 150800 and 188001 for details on browsing a routed network.