This tells me that you're on a "private" network (the 192.168.x.x stuff). Some ISPs do that, some don't... so, I can't do an nslookup off of your DNS servers because they're on the "inside" of your ISP's network.


Try the nslookup stuff I mentioned earlier.

While this Microsoft scan is running I am not able to access the router, after the scan is done I should be able to reboot the router and log in to get the rest of the info. You know the sad thing is that I am a level 2 IT guy with my company, only one level higher and I hold a 4 year degree in puter science but I get stumped on this kind of thing. My degree came in 82 long before this kind of stuff was around and I guess i have gotten lazy. I will re-post in a few hours. Thanks.

here is the server ip 74.47.101.112 nslookup points to frontier and when i look up thehulltruth it points to 67.201.16.17 still can't ping it. ????

OK I got it, it was the router firewall, I disabled and left the windows firewall on. Thanks for your help.

good to hear you got it working... my opinion is that you want to diagnose the hardware/router firewall and turn that back on.

I agree, I leave it on except when access that site and will call tech support monday.

Hey brent, here is what the firewall is saying,

TCP packet fragmented - 67.201.16.17:10555 -> 74.47.101.112:25185 len=732 id=32768

10/12/2008 06:40:24 MST E |Firewall |D:19:0 TCP 67.201.16.17:80 -> 192.168.254.3:4078 len=52 id=32768 DF=0 MF=0 byte-off=0

10/12/2008 07:32:25 MST E |Attack Detected |TCP packet fragmented - 67.201.16.17:25968 -> 74.47.101.112:25953 len=732 id=32768

Does this mean anything to you. This is what happens when I reinable the firewall and try to access tht.

Hmm... getting beyond my limits. But it looks like that was a web request, right? And not a ping? BTW, THT doesn't appear to respond to pings--I can't ping it either but I can get there in my browser.

I found only a little something where another user on Frontiernet.net had some issues and people suggested it might be the firewall... but I'm not certain. Check with their support when you can.

FIXED!!!!!!!! used drtcp and adjusted my mtu to 1500 and all is good, thanks for looking at the problem.

you're hired! nicely done. and you're welcome...