I am curious: How do you do security updates, etc., on a no longer support
O/S?
--
-----
Tom Pepper Willett
Microsoft MVP - FrontPage
-----
| No problem. Now I understand the "95 is alive" thing.
Windows 95?
|
| --
| Jim Cheshire
| Jimco Add-ins
| Add-ins for FrontPage 2000-2003
|
http://www.jimcoaddins.com
| ===============================
| Co-author of Special Edition
| Using Microsoft FrontPage 2003
|
|
| | > Agreed. All one needs to do to see that effect
| > is open a web site, then open a DOS or CMD window
| > and type netstat -an and press enter to see the different port
| > "responses"
| >
| > Ill try to explain better what I'm trying to say later.
| > Gotta run for awhile.
| >
| > Thanks again for the help yesterday.
| >
| > --
| > 95isalive
| > This site is best viewed...............
| > ..........................with a computer
| > | > > I'm only speaking about when you are using the wininet stack, Steve.
I
| > know
| > > nothing about SimpleServer and whether or not it uses wininet.
Wininet
| > does
| > > NOT respond on the same port that initiated the request.
| > >
| > > --
| > > Jim Cheshire
| > > Jimco Add-ins
| > > Add-ins for FrontPage 2000-2003
| > >
http://www.jimcoaddins.com
| > > ===============================
| > > Co-author of Special Edition
| > > Using Microsoft FrontPage 2003
| > >
| > >
| > > | > > > Jim I'm not sure I agree. I think port 80 blocking
| > > > by an ISP works both ways, as it keeps the "file sharers"
| > > > from using their machines as file servers, ( aka network servers )
| > > > by using a program such as SimpleServer.
| > > > ( the one I was using the other night when I asked for the port
| check )
| > > >
| > > > Remember this is from the guy still beating his head against the
wall
| > > > with Win95, FP98 and Apache ;-)
| > > > --
| > > > 95isalive
| > > > This site is best viewed...............
| > > > ..........................with a computer
| > > > | > > > > It will always use port 80 outbound unless you specify otherwise.
| The
| > > > only
| > > > > time that an ISP blocking port 80 should cause a problem would be
if
| > > > you're
| > > > > trying to publish TO your machine from outside of your network.
| > > > >
| > > > > --
| > > > > Jim Cheshire
| > > > > Jimco Add-ins
| > > > > Add-ins for FrontPage 2000-2003
| > > > >
http://www.jimcoaddins.com
| > > > > ===============================
| > > > > Co-author of Special Edition
| > > > > Using Microsoft FrontPage 2003
| > > > >
| > > > >
| > > > > | > > > > > Correct me if I'm all wet here, but if
| > > > > > the local machine is "mapped" to query outbound
| > > > > > via a different port, isn't FP still going to address port 80
| > > > > > at / on the server??
| > > > > >
| > > > > > In other words, I don't mean
www.domain.com:80 or 81etc
| > > > > > I mean setting the machine so that FP uses port xx outbound
| > > > > > I might not be explaining this very well, but you can set a
| program
| > > > > > to "send" via a specific "local" port.
| > > > > >
| > > > > > --
| > > > > > 95isalive
| > > > > > This site is best viewed...............
| > > > > > ..........................with a computer
| > > > > > | > > > > > > FrontPage 2000+ shouldn't have this issue. FrontPage 98 uses
| the
| > > old
| > > > > > > Vermeer HTTP stack which will still try to use port 80 inbound
| > from
| > > > the
| > > > > > > server. FrontPage 2000+ uses wininet HTTP stack which will
| switch
| > > the
| > > > > > port.
| > > > > > > The only time that port 80 is used is for outbound initially.
| > > > > > >
| > > > > > > FYI, HTTP can use any port you'd like. If you configure the
Web
| > > site
| > > > to
| > > > > > use
| > > > > > > the port, it will work, but it has to be configured on the
| server
| > > > first.
| > > > > > > After that, you just enter in the URL in FrontPage's publish
| > dialog
| > > as
| > > > > > > follows:
| > > > > > >
| > > > > > >
http://www.site.com:####
| > > > > > >
| > > > > > > So if the port you change it to is 85, it would be:
| > > > > > >
| > > > > > >
http://www.site.com:85
| > > > > > >
| > > > > > > --
| > > > > > > Jim Cheshire
| > > > > > > Jimco Add-ins
| > > > > > > Add-ins for FrontPage 2000-2003
| > > > > > >
http://www.jimcoaddins.com
| > > > > > > ===============================
| > > > > > > Co-author of Special Edition
| > > > > > > Using Microsoft FrontPage 2003
| > > > > > >
| > > > > > >
| > > > > > > | > > > > > > > FP98 has ( or should I say had ) the ability
| > > > > > > > to change the port FP uses by using the server wizard.
| > > > > > > > I don't see this feature in FP2002. However, have you tried
| > > > > > > > configuring FP to use a proxy, you can assign a different
port
| > > that
| > > > > way.
| > > > > > > > Just make sure it is an http compatible port. I believe the
| > next
| > > > > > > > http compatible port is 591.
| > > > > > > >
| > > > > > > > There is a list of port assignments / uses here:
| > > > > > > >
http://lists.gpick.com/portlist/portlist.htm
| > > > > > > > ( courtesy of Dave Stockbridge )
| > > > > > > >
| > > > > > > > hth
| > > > > > > >
| > > > > > > >
| > > > > > > > --
| > > > > > > > 95isalive
| > > > > > > > This site is best viewed..................
| > > > > > > > ..............................with a computer
| > > > > > > > | > > > > > > > Charter blocks port 80 and I am not sure but I think that
| > > > > > > > frontpage uses port 80 to upload to a site. I called
| > > > > > > > Charter and they don't know if they can unblock that port
| > > > > > > > for me. I would hate to use my dialup to upload to my
| > > > > > > > site, anybody know a way around this problem.
| > > > > > > >
| > > > > > > >
| > > > > > >
| > > > > > >
| > > > > >
| > > > > >
| > > > >
| > > > >
| > > >
| > > >
| > >
| > >
| >
| >
|
|
