Cannot access site from one machine

About 24 hours ago, I started getting ftp errors when uploading to a site but I could browse it. Now the site is totally inaccessable from my development machine.

All other sites I go to are ok. I can also FTP to other sites.

Other machines on the same DSL router can access it using Win98SE SE.

Also the development machine [Win8SE] can be dual booted into Win XP and then can access the site, so it's not hardware.

I've run Adaware to check for Spyware, I did get some spyware for a day last week, but it's clear today.

and I have the latest Norton Antivirus.

 

How old is the site?

Have you done a DNS transfer for it recently?

Are the machines in the same location?

Try clearing your cache.

 

What FTP program are you using. I have had that problem with 2 - SmartFTP and WS FTP PRO 9.

I switched to Cute and have not had a problem.

 

Site was created Sep 13. DNS was done within 2 days of that.

Browser cache was cleared. Powered off the computer, DSL modem and router, Switched ports on the router. Checked the Hosts file.

Problem occurs with IE, Opera, and FireFox.

Ping on the URL fails, the machine that's three feet away and plugged into the same router pings it ok. Both are resolving to the same IP address.

Do a reverse lookup on my machines auto assigned IP address and both are the same.

CLTR+ALT+DEl all apps, except the minimum.

My whole day is now shot. Some days I just hate this work.

 

Does it work if you type in the ip?

 

If I do a tracert - I get through 20 hops then it starts timing out from 21 to 30

The weird thing is on the other - the ok machine the tracert gets to hop 20 and is at 63.241.142.122 and times out on 21, then completes ok on hop 22.

The site is cool-sites-project.com at Godaddy.com.

Maybe one machine is more sensitive to timeouts than the other.





`

 

Try changing your hosts file.

Maybe that will do it (Weird one, but worth a try I guess)...

 

I've changed the hosts file no help

I've pulled and replace the NIC in case there was a timing issue. Still no good.

 

Shit man. I haven't got a clue then...

Does your ISP do any kind of weird caching at their end?

It all seems pretty screwy to me ????!?!?!

 

1. Did you install any software just before getting the problem?

2. Change your MTU (max transmission unit) I had a similar weird prob. it was a problem with a broken switch at the ISP that was fragmenting packets but it took me several weeks to get them to listen to me, so in the mean time I lowered the MTU on the machines so they would work. It is just slightly less efficient as the packet size is smaller, and it uses more packets.

On Win98 the reg key is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VxD\MSTCP\Parameters
(I think)
add a DWORD GlobalMaxTcpWindowSize
and set it to 576 decimal

If you want to test this out before changing the reg key, (probably a good idea) ping an internet server, sending a larger load and forbidding fragmentation.

ping x.x.x.x -l 1500 -f
and start lowering 1500 until you don't get the "packet must be fragmented" message
and set the MTU to that. (I had to set it to 576)

You might also want to search the ms knowledge base. I have not done this with 98 or 98SE just 2000 & XP

BTW what results do you get with a ping like I showed it above?

 

It appears there were/are two different problems going on. The site was hosted with GoDaddy, and it seems over the last few days they were doing some DNS changes that affected customers. This would explain why I couldn't get to the site at all for a while.

In addition there are indications of a hardware problems at some point along the tracert, the problem point belongs to AT&T and goDaddy told me to call them. However, they said, that GoDaddy is an AT&T customer, and it appears that Godaddy should take care of it since it's probably on their premises

At this point I get lots of timeouts when uploading site changes.

 

Thanks for letting us know...

That one was a real head scratcher...

 

Hmmm, what I don't understand is that supposedly you couldn't access the site from one computer, but from another on the same LAN, you could. This does not point to any problem at Godaddy or AT&T.

Anyways... Is the problem now fixed?

 

As far as accessing the site from two computers on the same router - I've seen this before when a site was new, and DNS propagation had not completed - I don't understand it, but supposedly each computer sonehow gets a different DNS server. Anyway that problem is fixed.

The timeout problem is not. It only shows when uploading files, where timeouts are going to be more sensitive. I have to now get on the phone again, and try try and figure who takes the responsibilty.

I'm getting this - for anyone who might know better how to interpret it.

Tracing route to cool-sites-project.com [64.202.167.122]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.30
2 2790 ms 2402 ms 2355 ms HSE-Toronto-ppp174856.sympatico.ca [64.229.69.1]
3 3048 ms 2409 ms 2386 ms 64.230.244.130
4 2396 ms 2367 ms 2375 ms core4-toronto63-Gigabite4-1.in.bellnexxia.net [206.108.107.181]
5 2391 ms 2369 ms 2400 ms 64.230.242.118
6 2428 ms * 2724 ms if-7-0.core2.Scarborough.Teleglobe.net [207.45.198.1]
7 * 2724 ms 2438 ms if-4-0.core1.Scarborough.Teleglobe.net [207.45.222.205]
8 * 2692 ms 2440 ms if-8-0.core2.NewYork.Teleglobe.net [64.86.80.221]
9 2467 ms 2446 ms 2428 ms if-3-0.core1.NewYork.Teleglobe.net [207.45.223.177]
10 * 2389 ms 2440 ms SURFnet-NYY-gw.Teleglobe.net [207.45.196.130]
11 2336 ms 2460 ms 2425 ms tbr1-p010401.n54ny.ip.att.net [12.123.3.57]
12 2087 ms 2841 ms 2663 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.2]
13 2800 ms * 3347 ms tbr2-cl2.cgcil.ip.att.net [12.122.9.134]
14 * * * Request timed out.
15 2670 ms 2392 ms 2421 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
16 2496 ms * 2843 ms gbr2-p30.phmaz.ip.att.net [12.122.2.106]
17 2529 ms * * gar2-p370.phmaz.ip.att.net [12.123.142.49]
18 2468 ms * 2960 ms mdf1-gsr12-1-pos-7-0.phx1.attens.net [12.122.255.230]
19 2564 ms * 2649 ms mdf1-bi8k-1-eth-1-1.phx1.attens.net [63.241.128.250]
20 * 2842 ms * 63.241.142.122
21 * * * Request timed out.
22 2664 ms * 2740 ms cool-sites-project.com [64.202.167.122]

Trace complete.

It always times out on hop #21 - if it's really bad, I get multiple timeouts at hop 21, and it never connects

 

Some thoughts in random order:

1. Are you getting the timeout problems from all machines on your LAN?
2. Have you tried a variety of FTP programs for uploading?
3. What is the status of pinging? If you send a large load (-l) and tell it to keep pinging forever (-t) how long will it go untill getting a packet that times out?
4. When you traceroute, is it always the same node -- ie right before reaching cool sites proj? or is it always some other node that you can id from ip addy?
5. Back to pinging, if you send a large load with ping and it times out, but if you send a small load and it doesn't time out, that could tell us that a node (switch etc) could be rejecting larger packets (which most likely are being used for file uploads).

 

Now you know why I'm NOT a network tech. I'll stick to web design and development, thank you.