Arson, I sent you a pm yesterday, could be a temporary solution.

What you're saying about the achewood site responding to a ping sort of makes sense I think. Your network can 'see' achewood but asking for its webpages calls the silly filter into play and that sends down its 'you're blocked, fool' message to annoy, instead of lovely achewood funnies.

I think there's a DNS problem somewhere in your company's network/on your local computer so electrical just can't be found as its name can't be resolved to its address.

You could try to clear out your machine's dns entries: >run>cmd>ipconfig /flushdns
then try EA again.

If this doesn't work, can you do a run>cmd>ipconfig /all to check what DNS server your computer/company is using? I'm guessing it'll be an internal (company based) one.

If you can adjust the network connections on your computer (control panel> network connections>local area connection -right click>properties>TCP/IP>properties> use the following DNS server) you could try an external one to see if this would let you connect.

I've used open DNS' before but there are a few here:
http://theos.in/windows-xp/free-fast-pu ... rver-list/

Of course if you can't get in to network connections properties then that's knackered.

Sorry for the waffle.

ssakmule wrote:Arson, I sent you a pm yesterday, could be a temporary solution.

Thank you for that idea - I have found one so far that I can still use,
although it renders me read-only (can't do a login = can't post)

chuckles wrote:I think there's a DNS problem somewhere in your company's network/on your local computer so electrical just can't be found as its name can't be resolved to its address.

Actually, I think that part works OK:

C:\>nslookup electrical.com
Server: xoxox01.us.myworkplace.com
Address: 10.5.12.16

Non-authoritative answer:
Name: electrical.com
Address: 70.47.38.85

But even if I just ping the numeric IP address:

C:\>ping 70.47.38.85

Pinging 70.47.38.85 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 70.47.38.85:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

chuckles wrote:You could try to clear out your machine's dns entries: >run>cmd>ipconfig /flushdns
then try EA again.

Unfortunately, that did not seem to work...

chuckles wrote:If this doesn't work, can you do a run>cmd>ipconfig /all to check what DNS server your computer/company is using? I'm guessing it'll be an internal (company based) one.

Yep. Internal.

chuckles wrote:If you can adjust the network connections on your computer (control panel> network connections>local area connection -right click>properties>TCP/IP>properties> use the following DNS server) you could try an external one to see if this would let you connect.

I've used open DNS' before but there are a few here:
http://theos.in/windows-xp/free-fast-pu ... rver-list/

I tried the first few in the list, but then I couldn't get to any sites at all, so I set it back to 'Obtain DNS server address automatically'... will try to play with this some more tomorrow - thanks for the ideas.

BadComrade wrote:Get a new job.

I know, it's about that time.

HA. I am posting this from work.

So apparently when I use the "on-call" wireless card, there is NO bullshit browser cock-blocking, etc.

What a fucking joke. So here's the new plan - if I need to do something 'extra-curricular' during my lunch break or whatever, then it's time to fire up the wireless card and help them burn up their minutes. Fuckers.

Arson Smith wrote:HA. I am posting this from work.

So apparently when I use the "on-call" wireless card, there is NO bullshit browser cock-blocking, etc.

What a fucking joke. So here's the new plan - if I need to do something 'extra-curricular' during my lunch break or whatever, then it's time to fire up the wireless card and help them burn up their minutes. Fuckers.

I bet the wireless card doesn't go through the Cyberoam firewall, either, huh? Try the traceroute and ping and such with it, note the differences.