You may also need port 135 - RPC end point mapper...
Try this: http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q179442 HTH Tres -----Original Message----- From: Mark Ng [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 11:38 AM To: 'Dante Mercurio'; Justin Silles; [EMAIL PROTECTED] Subject: RE: Windows networking ports You may also need to set up WINS between the two networks. Mark -----Original Message----- From: Dante Mercurio [mailto:[EMAIL PROTECTED]] Sent: 08 January 2002 14:20 To: Justin Silles; [EMAIL PROTECTED] Subject: RE: Windows networking ports If you are using Windows 2000, try opening up port 445 through the firewall also. Hope this helps, M. Dante Mercurio, CCNA, MCSE+I, CCSA Consulting Services Manager Continental Consulting Group, LLC www.ccgsecurity.com <http://www.ccgsecurity.com> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > -----Original Message----- > From: Justin Silles [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 07, 2002 10:32 AM > To: '[EMAIL PROTECTED]' > Subject: Windows networking ports > > > Hello All. > > Just trying to set up a way to map a drive through our > firewall (Internal to > DMZ) for special computers and special username/password > combo via NT authentication.... > > While doing so I swore that I just needed to open up ports > 137, 138 and 139 between the two PCs in order to map shares. > Is there one more port that I am missing (seems to me there > is)...or multiple ports...?? Do I need to specify that after > the initial connection there needs to be a subsequent > connection to a random port between 1024-65563? Again, I > just thought I needed 137-139. > > When tested on our non-live network we tried opening up a > huge hole across the internal to DMZ loop, just incase > another rule (computer-name or user) was not set proper. > Still did not work. > > Thanks in advance. I think I am just "having a case of the > Monday's" :) > > Justin M. Silles > [EMAIL PROTECTED] >
