Ports required for authentication and file sharing over the internet?

I am unable to log in to my home windows 200 domain over the internet from a computer on my campus network. (Logins over the internet succeed from networks outside my campus.)

A likely cause is that the campus firewall has disabled ports necessary to authenticate with my home domain controller and share files over the internet. I found a list of the default w2k ports here

http://support.microsoft.com/default...b;en-us;289241

What subset of these ports must be open to allow authentication and file sharing with a windows domain over the internet?

Thanks

Kerry

In item news:850941E5-2B9F-4A85-A964-(E-Mail Removed),
Kerry says...

> I am unable to log in to my home windows 200 domain over the internet from a
> computer on my campus network. (Logins over the internet succeed from
> networks outside my campus.)
>
> A likely cause is that the campus firewall has disabled ports necessary to
> authenticate with my home domain controller and share files over the
> internet. I found a list of the default w2k ports here:
>
> http://support.microsoft.com/default...b;en-us;289241.
>
> What subset of these ports must be open to allow authentication and file
> sharing with a windows domain over the internet?
>
> Thanks,
>
> Kerry

Uh... You may want to close that up with a firewall and use a VPN connection.
Your description indicates (to me at least) that your server is hanging out on
the internet unprotected. The ports you need are highly vulnerable to attack
across the internet.


--
Regards,

Michael Holzemer
No email replies please - reply in newsgroup

Learn script faster by searching here
http://www.microsoft.com/technet/com...r/default.mspx

On Sat, 10 Apr 2004 13:21:02 -0700, "Kerry"
<(E-Mail Removed)> wrote:

>I am unable to log in to my home windows 200 domain over the internet from a computer on my campus network. (Logins over the internet succeed from networks outside my campus.)
>
>A likely cause is that the campus firewall has disabled ports necessary to authenticate with my home domain controller and share files over the internet. I found a list of the default w2k ports here:
>
>http://support.microsoft.com/default...b;en-us;289241.
>
>What subset of these ports must be open to allow authentication and file sharing with a windows domain over the internet?

137-139, 445 and possibly the Radius and/or Kerberos ports depending
on how you're authenticating. When you get these working, let me know
the IP, I need a good system to store WaReZ and Pr0n on as well as use
to get to your campus network so I can launch my death ray...

In case you missed the sarcasm, you *really* don't want to do this and
I'm betting the campus network team is way too smart to let you try.

Jeff

[I posted a revised version of this reply as a new forum thread.

Gentlemen

Thank you for the thoughful reply to my question regarding internet access to my home w2k domain. I am gaining a better understanding of the significant internet security issues pertaining to windows 2000 systems and intend to "lockdown" the domain with a firewall before adding any sensitive resources

However, the question remains. How do I securely transfer files to and from this home domain from an internet connection located within my secured campus network? Basic FTP is not an option due to its lack of security. VPN sounds like a possible solution. However, after configuring VPN on the server and client again I was unable to connect from the campus internet connection. I suspect a VPN connection too requires permission of some sort from the campus network administrator

At this point, I would just like to get a "big picture" idea of the options available to me. To sum up: I am connecting from within a secured campus network. The network permits at least standard internet traffic. From this connection I would like to securely transfer files to and from a windows domain located in my home. For example, I would like to open a file that is shared on the domain, edit the file, then save it back to the domain. Based on my experience and the replies to my earlier posts, I am growing increasingly discouraged that this is possible at all.

I have no difficulty establishing remote desktop sessions with my home domain from the campus internet connection. This leads me to think there must be *some* secure way to transfer files over that same connection

Thanks again

Kerry

Asked and answered in another group. Don't multi-post.

Jeff

On Sun, 11 Apr 2004 14:01:06 -0700, "Kerry"
<(E-Mail Removed)> wrote:

>[I posted a revised version of this reply as a new forum thread.]
>
>Gentlemen,
>
>Thank you for the thoughful reply to my question regarding internet access to my home w2k domain. I am gaining a better understanding of the significant internet security issues pertaining to windows 2000 systems and intend to "lockdown" the domain with a firewall before adding any sensitive resources.
>
>However, the question remains. How do I securely transfer files to and from this home domain from an internet connection located within my secured campus network? Basic FTP is not an option due to its lack of security. VPN sounds like a possible solution. However, after configuring VPN on the server and client again I was unable to connect from the campus internet connection. I suspect a VPN connection too requires permission of some sort from the campus network administrator.
>
>At this point, I would just like to get a "big picture" idea of the options available to me. To sum up: I am connecting from within a secured campus network. The network permits at least standard internet traffic. From this connection I would like to securely transfer files to and from a windows domain located in my home. For example, I would like to open a file that is shared on the domain, edit the file, then save it back to the domain. Based on my experience and the replies to my earlier posts, I am growing increasingly discouraged that this is possible at all.
>
>I have no difficulty establishing remote desktop sessions with my home domain from the campus internet connection. This leads me to think there must be *some* secure way to transfer files over that same connection.
>
>Thanks again,
>
>Kerry