Re: new network place and TCP port number
From: Doug Sherman [MVP] (dsherman_at_nospam.tampabay.rr.com)
Date: 11/06/04
- Next message: Vince C.: "Re: Name Lookup latency when resolving Internet names"
- Previous message: Doug Sherman [MVP]: "Re: NTOSKRNL.EXE missing or corrupt?"
- In reply to: mountaindog: "Re: new network place and TCP port number"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 6 Nov 2004 12:45:37 -0500
OK, don't really think this will work, but try:
1. Map TCP and UDP 445 to the internal address of the Win2k machine.
2. Use \\ExternalIPaddressofFirewall
See: http://support.microsoft.com/default.aspx?scid=kb;en-us;204279
Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
"mountaindog" <lhedrick@mountaindogs.net> wrote in message
news:ecXIhBCxEHA.908@TK2MSFTNGP11.phx.gbl...
> Doug,
>
> There is no hacker problem here. I should have mentioned that the Linux
> firewall will only forward connections requests from trusted IP source
> location. I did not mean to imply that this should ever be done without
> VPN or firewall.
>
> Yes, I am using Windows 2000 Pro. I do this all the time with Samba on
> Linux and Windows shared files but, only with data which does not need
> to be protected. I don't care if this data runs over the network in
> clear text. If a hacker wants to wast his/her time looking at my word
> docs, more power to them. I often use this as a substitute for ftp.
> Believe it or not I have clients who think filezilla is so complex they
> will not use it.
>
> This process works all the time. I just does not work in this instance
> because the ISP is blocking port 139. Port number reassignment is used
> by lots of services. I just want the client to be able to use a
> specific port which the firewall will forward to port 139 on the
> internal net.
>
> Thanks
>
> Doug Sherman [MVP] wrote:
>
> > If you had succeeded in doing this, every hacker in the world would be
your
> > new best friend.
> >
> > Assuming you are using Windows 2000 Professional, there are 3
conventional
> > ways to enable remote access to a shared folder:
> >
> > 1. VPN - see:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;257333
> >
> > 2. Web Server - see:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;308192
> >
> > 3. FTP Server - see: http://support.microsoft.com/kb/300662/EN-US/
> >
> > Doug Sherman
> > MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >
> > "mountaindog" <lhedrick@mountaindogs.net> wrote in message
> > news:%23cKdrIBxEHA.3668@tk2msftngp13.phx.gbl...
> >
> >>I have a windows 2000 system with a shared folder named share1. This
> >>system is behind a firewall. There are times when I wish to access this
> >> shared folder remotely. Unfortunately my ISP is blocking port 139.
> >>Is is possible to change the port number when the client connects? Like
> >>the way telnet does it
> >>
> >>telnet host 8989
> >>
> >>When creating the network placed I have tried the follow with no luck:
> >>
> >>\\host:8989\share1
> >>
> >>This would have been too easy.
> >>
> >>
> >>If anyone has a suggestion please let me know.
> >>
> >>Thanks in advance.
> >
> >
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.788 / Virus Database: 533 - Release Date: 11-1-2004
> >
> >
>
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.788 / Virus Database: 533 - Release Date: 11-1-2004
- Next message: Vince C.: "Re: Name Lookup latency when resolving Internet names"
- Previous message: Doug Sherman [MVP]: "Re: NTOSKRNL.EXE missing or corrupt?"
- In reply to: mountaindog: "Re: new network place and TCP port number"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
