Access home windows domain over the internet from inside secured network.

(I posted a copy of this message in the windows 2000 advanced server forum

I want to
Access shared folders on my domain over the internet from within a secured network
Authentication fails when I try to connect to my home domain from an internet connection within my campus network.

Setup
Domain
Location: Hom
OS: Windows 2000 domain. No (known) firewall enabled. (I set up the domain to optimize accessibility and make the network as open to the outside world as possible during this testing stage. This is an isolated home network set up only for experimental purposes and is not connected to any critical data at the moment. I plan to incorporate security at a future stage.
IIS 5 enabled
Domain internet connection: ADS

Clien
Location: Campus networ
OS: Windows XP sp1
Client internet connection: campus broadband network
This is the potential bugaboo. I don’t know which security protocols are installed on my campus network. I do know that SSH is required to access some campus resources from outside the campus network.

Experience
Remote desktop works from the campus connection. That is, using the client computer from within the campus network I can successfully RDP over the internet to a computer on my home windows domain. (I find it surprising that I can authenticate a remote desktop session with my home domain over the internet from campus but I cannot authenticate to simply access shares on the external domain.

I can connect to my home domain from other windows computers OUTSIDE the campus network. For example, I can connect to and access my domain shares on my neighbor’s windows computer over a DSL connection. This leads me to conclude that the accessibility problem does not lie with my domain’s configuration, but with the security protocols in the campus’ internet connection

To sum up, I want to access my home windows domain from my campus internet connection. I want to connect to and bring up shared domain resources simply by typing the domain computer name in a windows search box, e.g.: Search for: computername.domain.com

Any tips or suggestions would be very helpful in researching my problem

Thank you

Kerr

(I will check this post frequently)

On Fri, 9 Apr 2004 15:51:03 -0700, "Kerry"
<(E-Mail Removed)> wrote:

>I want to:
>Access shared folders on my domain over the internet from within a secured network.
>Authentication fails when I try to connect to my home domain from an internet connection within my campus network.

>Experiences
>Remote desktop works from the campus connection. That is, using the client computer from within the campus network I can successfully RDP over the internet to a computer on my home windows domain. (I find it surprising that I can authenticate a remote desktop session with my home domain over the internet from campus but I cannot authenticate to simply access shares on the external domain.)

Remote Desktop and shares use different ports.

>I can connect to my home domain from other windows computers OUTSIDE the campus network. For example, I can connect to and access my domain shares on my neighbor’s windows computer over a DSL connection. This leads me to conclude that the accessibility problem does not lie with my domain’s configuration, but with the security protocols in the campus’ internet connection.

Valid conclusion.

>To sum up, I want to access my home windows domain from my campus internet connection. I want to connect to and bring up shared domain resources simply by typing the domain computer name in a windows search box, e.g.: Search for: computername.domain.com.

Then you need to provide for domain authentication and Windows sharing
over your connection.

>Any tips or suggestions would be very helpful in researching my problem.

Start with the admins of your campus firewall.

Jeff

Thanks for the tips Jeff. I am currently corresponding with the department that oversees the campus network. I have described my problem to their representatives and expect to get a response once my request reaches the right people. I hope to talk to the firewall administrators