Post by: jepinto on September 20, 2003, 05:06:29 AM
6400/G3/400, OS 9.1-wired ethernet
Compaq-?-WinXP-wired ethernet
IBM 600LE-Win2000-wireless ethernet
The problems do not occur while connected directly to the modem, so it must be the router
Here's what I sent to TechSupport:
Unable to upload files (FTP), starts, gets roughly 10K uploaded and hangs. When forced to stop, get message "Server file error, transfer aborted, data connection closed." Have to close the window and make a new connection to find that the file name is there, but the file shows as 0K.
I'm doing this on the Mac. Updated the firmware as TechSupport suggested. Did a download on the Win2000 machine of the "311BRP_v1020n.zip" and updated the firmware again, just in case it was the Mac. Nope, still can't do an upload.
The Win XP machine is having trouble reaching certain sites in addition. The site giving the most trouble is http://www.gamesville.com. She can access the site, but when she tries to access the actual games, the browser "times out" and says it can't reach the site.
Basically the same thing is happening on the Mac trying to reach ebay. Getting to the site is not a problem, initially. The site comes up, but if I try to navigate past the first page, it goes into a loop, finally bringing up a message that the "document contained no data". Note A temporary work around has been acheived! If the browser is set to "not accept cookies" ebay pages load. 2nd Note This DOES not happen on other sites that require cookies, like TS, 'cause if it had the router would've been overboard a loooooong time ago. 'round here, "How far can one toss computers into the Gulf and how far do they sink?" is NOT a rhetorical question!. end note
The Win2000 machine is connected via wireless and is also having this "time out" problem. I've been trying to update to SP 4 for Win2000 for a week. It does the initial download, no problem, inspects the current config, does the archive, updates, the "The following error occurred while Service Pack 4 Setup attempted to download the Service Pack 4 files from the Internet: The server did not respond". Retrying does nothing.
Our service provider is Bellsouth. We have a Westell Wirespeed modem. The XP and Mac are connected via ethernet, the 2000 is wireless.
When I first set this up, the tech had me change the IP address to 192.168.0.1 because the default IP address 192.168.1.1 did not allow ANY internet connection.
The Wirespeed Dual Connect is accessed via http://192.168.1.254/ in my browser. Info for it
DSL-Up
Connection-Up
User ID-********
IP Address-68.18.248.217
IP Gateway-68.18.248.1
Primary DNS-205.152.46.254-sun00gnv.gnv.bellsouth.net
Secondary DNS-205.152.144.235-ns1.mia.bellsouth.net
Modem Info
Modem Name-WireSpeed Dual Connect
Model-A90-210030-04
Serial-03B405251013
Software Version-01.06.15
MAC Address-***********
Warranty Date-July 5, 2003
Local Network
Modem IP Address-192.168.1.254
Ethernet-connected
USB-locked
________________________________
Some of these same symptoms, i.e., not being able to surf ebay, not being able to "submit" web forms on sites like Spamcop (and now Trendware's help desk!) occured while connected to another router, but I blamed it on Direcway
That router was a D-link(?) connected and set up on a WinXP Home machine.
Post by: kelly on September 20, 2003, 08:47:49 AM
I am surprised about the use of 192.168.0.1 though.
That's a completely different Subnet assuming your Subnet mask is 255.255.255.0
Maybe something about Proxy?
Post by: jepinto on September 21, 2003, 06:41:22 AM
Post by: Diana on September 21, 2003, 06:25:08 PM
Sorry to have not seen this earlier. I wish I could help, but you've had so many problems with that router, I'm beginning to think maybe it's bad.
Kelly is right though, the IPs look really odd. Do you have DHCP enabled? What machine is providing that service...one of the Win machines or the router? Try turning DHCP off and hard coding each machine's IP, double checking your subnet mask. The router's internal IP will also have to be on the correct subnet.
After double checking the IP situation, the last thing to try if you haven't already, is enable Passive transfer mode from inside your FTP program and see if the connection will allow files to move.
Another thought that may be completely off the wall, but try disconnecting the Win2000 wireless machine and see if there is a way to shut down the wireless capabilities on the router. Then do the opposite and see if you can stop the ethernet, or just unplug all the cables, and see if the win2000 machine quits having problems. Start isolating everything you can until you only have one possible problem at a time.
If you really wanna get techy, you can use a packet capture program to see if you can determine what packets get in and out, and if some are lost. I'm not sure what you could run on the Mac, but there is Ethereal for Windows. (and OS X) Remember I said techy now cause it's not just a matter of installing in and running...lots to learn and do. I mention it though 'cause you might wanna learn..
Might be easier to try another router.see ya
Post by: jepinto on September 21, 2003, 07:26:24 PM
The machines end up with IP addys of
192.168.0.2-Usually the Compaq since she gets in earlier
192.168.0.3 usually the Mac
192.168.0.4 is usually the laptop, as it does not get turned on every day, only if real estate programs need to run
I'll have to check the IP range and other parameters in the morning. The subnet mask of 255.255.255.0 looks right though.
Post by: Diana on September 21, 2003, 08:19:11 PM
yes, your netmask is correct for the IP range you're using. I wouldn't worry yet about hard coding IPs just yet. Try the isolation options first and see what happens.
see ya,
Post by: Diana on September 23, 2003, 06:01:37 AM
Any luck with the router?
Post by: jepinto on September 23, 2003, 07:56:28 AM
I am not impressed with Trendware's Tech Supportless.
I've even told them "on the machine" that I'm about to pull myself bald headed and that won't take long....and they haven't answered yet!
Post by: jepinto on September 23, 2003, 06:24:47 PM
QUOTE
the last thing to try if you haven't already, is enable Passive transfer mode from inside your FTP program and see if the connection will allow files to move.
WORKED!!!!Thank you! I can now FTP. Now if the "can't find the server" and other little messages will quit.....
Post by: jepinto on September 29, 2003, 07:13:54 PM
The router and the modem were set to different protocols, the modem to PPPoE, the router to DHCP. Both were trying to "make the connection".
Something to do with MTU and packets. The router was sending out 1500, the modem couldn't handle more than 1464, and the packets were fragmenting
We set the router to PPPoE and all WORKS
The "distinquishing symptom" was that the WAN IP address showing in the set up window for the router was a 192.168 number instead of a 68. number.
Post by: kelly on September 29, 2003, 09:15:13 PM
Gotta watch them MTUs.
http://www.pcwebopedia.com/TERM/M/MTU.html