Frontpage 2003 & Linksys Router/Firewall

[William]

Everytime I attempt to upload to a www site, my router
will drop and restart itself. If I'm surfing th web or
FTP'ing - it works fine. Only when I attempt an upload
will it reboot itself. I've tried to upgrade the Firmware
on the Linksys, but that doesn't seem to have any effect.
Linksys BEFSX41 Router/Firewall
Frontpage 2003
WinXP Pro

Can anyone Help...Please?

 

[David Berry]

Hi William. I have the same router and I'm not getting the problem you are.
I actually downgraded my firmware to 1.42.3 since some of the other updates
seemed flaky. Are you running any other firewall software? That could
cause an issue as well.

 

[William]

No, I'm running this straight through the router. I've
since tied to FTP upload, www upload, but both are cuasing
the router to restart... ugg

Do you know where the older Firmware is located?

Thank-You!!!

 

[David Berry]

I can't find the link to the old versions but I got it at www.dslreports.com

Which firmware version are you using? According to their knowledge base you
need the latest one for this problem. See:

http://www.linksys.com/support/top1...ing and uploading files using the BEFSX41.asp

There are more articles at http://www.linksys.com/support/top10faqs/BEFSX41/

 

[Fred]

Hey Billy

I would just disconnect the router temporarily and connect your computer straight to the internet and reconnect after you have published your sit

 

[Stefan B Rusynko]

That "work around" is like working in the stone ages




| Hey Billy,
|
| I would just disconnect the router temporarily and connect your computer straight to the internet and reconnect after you have
published your site
|

 

[Steve Easton]

Make sure the router is not set to block
"outbound" port 80 and port 21.

A common misconception is if IE will connect
FrontPage should too. However neither IE or any other
windows program except FrontPage use port 80 in
any way shape or form on a "Client" machine.

 

[Jim Cheshire]

Steve,

IE uses port 80 on the client to initiate a request on the default HTTP
port. For example, if you click the link in my tagline to my Web site, the
client will use port 80 to connect to my Web site. Assuming you are using
IE, after the response is received, the client will actually initiate future
communication on a random port.

It is true that you cannot assume that FrontPage can connect if IE can
connect, but it is not because of port usage. Instead, it is because there
is a lot going on when you connect with FrontPage that doesn't occur when
you browse with IE. For example, when you connect with FrontPage to a
Windows Web server, the server has to have the ability to execute shtml.dll.
If you are trying to connect as an author of the site, the server has to be
able to execute author.dll. The username and password you enter has to have
the correct permissions on files.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://sefp2003.frontpagelink.com

 

[Steve Easton]

Jim,

I humbly beg to differ on this.

( must say you host on a good server though,
14 simultaneous ports ) ;-)

I just ran a netstat trace immediately
after clicking the link to your site.
My machine didn't use port 80 outbound at all.

Also if a client machine has Yahoo IM installed and running
port 80 is claimed by yahoo for it's P2P file sharing
service. Running Yahoo Im will also cause the "there
is no server avalable at port 80" error in FP.!!!

protocol local remote
TCP 192.168.0.10:139 0.0.0.0:0 LISTENING
TCP 192.168.0.10:1174 12.155.117.8:80 TIME_WAIT
TCP 192.168.0.10:1179 12.155.117.8:80 TIME_WAIT
TCP 192.168.0.10:1187 12.155.117.8:80 TIME_WAIT
TCP 192.168.0.10:1200 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1201 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1202 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1203 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1204 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1205 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1206 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1207 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1208 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1209 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1210 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1211 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1212 207.182.248.22:80 ESTABLISHED
TCP 192.168.0.10:1213 207.182.248.22:80 ESTABLISHED

Regards
Steve

 

[Jim Cheshire]

Steve,

You are thinking inbound. Yahoo takes inbound port 80, and that prevents
you from opening a Web site located on a Web server running on the same
machine as the Yahoo IM program.

If you make a request for http://www.jimcoaddins.com, I guarantee you that
it will be on outbound port 80. Why? Because IIS on the Web server is
listening on port 80! If you don't send a request on port 80, the server
won't get it.

Think about it for a minute. As you said, Yahoo IM (in addition to others)
listens on port 80. Therefore, when you try and connect to a Web server on
that machine, FrontPage will tell you that there is no Web server on port
80. Why? Because unless you explicitly indicate otherwise, HTTP is going
to send a request on port 80. That's the way the protocol works.

I'm not sure what/how you captured your traffic data, but if it is
indicating that you are not making a request on outbound port 80, it is not
valid data. Your software may be indicating the src port and not the
destination port. Remember that I said that the response from the server
will be on a random port. That port is the src port and it is the port that
the client will listen on for the response. However, the request is sent on
the destination port 80.

I just captured a Netmon trace of a request for my Web site. Here's what
happened:

GET REQUEST src: 3287 dst: 80
RESPONSE src: 80 dst: 3287
GET src: 3290 dst: 80
RESPONSE src: 80 dst: 3290

This continues on until the page is loaded. In this case, you can see that
the client initiates the request on outbound port 80. The inbound port is
3287. The Web server then sends a response from the source port 80 to the
destination port 3287. 3287 is the current INBOUND port for the client, but
the outbound port is still set to 80 and always must be because that's the
port the server is listening on.

Next the client makes another request on port 80. It sets the src port to
3290 which just tells the server to send the response to that port. The
server on port 80 sends the response to 3290. The next request (not shown
here) from the client changes the port again and it continues on.

This is why people have trouble when they try to answer the question "which
inbound port do I need to open on my firewall so that I can use FrontPage?"
The answer is "every port between 1024 and 5000." Those are the ports that
Wininet (the Microsoft HTTP stack) is going to set as an inbound port for
responses. However, if requesting data from a Web server over the default
HTTP port, the destination port (the port on which the client sends the
request) will be port 80.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://sefp2003.frontpagelink.com

 

[Jim Cheshire]

Oh, I see you ran netstat. Netstat shows you inbound port numbers. It
tells you the port that the client will listen on for the response, not the
port that the request was sent TO.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://sefp2003.frontpagelink.com

 

[Jim Cheshire]

And one more thing. You indicate that my server has 14 simultaneous ports.
That's not really what's going on. What you are seeing there is the client
machine changing the src port. The server then sends the reponse to the
dest port specified by the client. This is the random port change I talked
about. All of this is controlled by the client machine, not the server.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://sefp2003.frontpagelink.com

 

[Steve Easton]

Jim,

I'm still not convinced and here's why:
as you listed below, and as I interpret this:

GET REQUEST src: 3287 dst: 80 Client to server request

RESPONSE src: 80 dst: 3287 Server to client response, which

makes
the source port, port 80 from the server to the client

GET src: 3290 dst: 80 Client to server request
RESPONSE src: 80 dst: 3290 Same as line 2 above.

Also, you can run an application on a client machine that "locks" port
80 and still access the internet.
An outbound http request can come from any client port, but always
queries port 80 at a server because 80 is the default http port.

Try this, enter the following at a command prompt:
netstat 2 -an >c:\log.txt
and press enter.
it will write a text log to C:\ and append/update it every two seconds
Open a few sites and then check the log and see if the
machine uses port 80 outbound. Mine doesn't.

You have to use control C in the cmd window to stop the function.
Also the file gets quite large quite fast.

Regards

Steve

 

[Jim Cheshire]

Steve,

I think you're confusing inbound and outbound. Think of it this way.

The server is listening on port 80.
The client MUST send a request on outbound port 80 in order to hit the
server listening on port 80.

It's really as simple as that. If the client sent its request on a port
other than 80, the server wouldn't get the request because it's listening on
port 80.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://sefp2003.frontpagelink.com

 

[Steve Easton]

Thanks Jim.

I'm doing some "digging" to see where I got my wires crossed.!!

Steve

 

[Jim Cheshire]

I think you're just confusing inbound and outbound. Outbound is port 80.
Inbound is whatever the client sets the SRC to on the request. A Wininet
client (such as IE or FrontPage) will set the SRC to a random port between
1024 and 5000 in my experience.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://sefp2003.frontpagelink.com

 

[Steve Easton]

I agree outbound on a / from a server is port 80.
I "think" that the request from a client machine to a server
is ( can be ) from any port in the range you mentioned below
and what directs it to the servers' port 80 is that the http
header is by default routed to port 80 by the tcp/ip stack.
Just as https is routed to port 443 on a server

Something else that adds to *My confusion* is
that I can launch a server program such as simpleserver,
which "claims/uses" port 80, load a web into it, start it, send you
my IP address in http://xxx.xxx.xxx.xx format so you can click it and
open the web and then I can still surf the net with my machine with the
server
program running and port 80 basically "locked up"

I've used this to let clients preview webs before publishing.

Am I making sense. ( or should I say any more sense than before )
;-)

 

[Jim Cheshire]

Steve,

What causes the response to go to a different port is the SRC attribute in
the header. That's correct. However, the outgoing port is port 80. The
traffic is sent on port 80 outbound to the server. I guarantee it. I have
reviewed literally thousands of traces using Network Monitor. I've had many
discussions with the Wininet guys at Microsoft, and during the days when I
troubleshot FrontPage Server Extensions for a living, I was well-versed in
the HTTP stack and how it works.

Having a Web server (or any other software) listening on port 80 on your
machine does not affect your ability to send outgoing information on port
80.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://sefp2003.frontpagelink.com

 

[Steve Easton]

click..... the light bulb is lit. ;-)

Thanks for the "education"

Regards

Steve.