Machine not accessing a domain

[garethEds]

Evening 'awl,

 

I have an issue with a machine I am trying to sort out the other side of the country. The machine is connected to a BT Business Broadband account and is running Windows 7. It has full unfiltered internet access.

 

The domain this machine is trying to access is Radiant Physiotherapy and/or it's .co.uk namesake.

 

I know the website is working as I can access it from every other computer I try. The machine accesses any other website without any issues.

 

I have access to the web server hosting the radiant websites and there are no ipblocks listed. According to the owner, this happened yesterday. The only change he has made is an attempt to setup Outlook 2007 by himself.

 

I'm stumped so any advice would be welcome.

 

Cheers

 

Gareth

[kmount]

Can you ping the hostname for the site and return the correct IP?

[garethEds]

I can ping Radiant Physiotherapy and it resolves the IP address.

 

The pings timeout - although saying that it's timing out here as well yet the website is working

 

Gareth

[kmount]

It resolves the correct IP yes? (91.204.208.41)

 

Try and telnet Radiant Physiotherapy 80 and see if that connects.

 

(Sigh, windows 7, probably won't have telnet available)

 

No proxy configured? Firewalls that can be turned off? Alternative browser?

[garethEds]

I don't think the browser is the issue because none of the mail applications can connect to mail.radiantphysiotherapy.com or .co.uk either.

 

I'll try telnet now

 

Hmmm - he did also have Google Chrome installed as well. Wonder if that did anything.

 

GJE

[glennda]

I can ping Radiant Physiotherapy and it resolves the IP address.

 

The pings timeout - although saying that it's timing out here as well yet the website is working

 

Gareth

 

I would assume the servers are sitting behind a firewall which does not respond to pings. Which browser is the person trying to use?

 

could it be something stupid like it give up trying to connect if the computer cannot ping/ or send some kind of packet to the address (never seen this before/or a setting to do it) but you know what windows is like!

[garethEds]

It cannot be DNS 'cos everything is resolving. Firefox will not see it either.

 

I wonder if his BT Business Router has an issue with it. Anyone dealt with one of these before?

 

Gareth

[glennda]

Have you tried a tracert? see how far you get before it fails to connect? I can get to 77.75.104.70 (synergyworks something but the url was to long to write out in full!)

[kmount]

Everything may resolve either way that doesn't mean the IP is correct. (for example if you use opendns or ntl's dns servers with their helpful guessing it will return an IP regardless)

 

A traceroute is a good idea, and it could very well be the BT router but if its just these sites that seems a little unusual.

 

Please confirm the IP is correct.

[glennda]

second time round i have made it to 78.86.40.1 which is a Bethere address

 

check the ip address of linuxweb1.veloxserv.co.uk resolves to the same address (nmap provided it as the host server name)

Edited May 20, 2010 by glennda

[kmount]

My trace stops at a router in synergyworks.co.uk which probably right before the subsequent host(s) ignoring icmp.

 

The key here is to check that the IP is correct as I've previously given (and yes, its the same as linuxweb1.veloxserv.co.uk) and to see if telnet can reach it (to rule out any app specific hackery)

[Messa]

How do Gareth, have PM'd you.

 

I think we sorted this the other day for you, although your not a direct customer I obviously want you to get this sorted!

[kmount]

What was the issue then?

[garethEds]

How do Gareth, have PM'd you.

 

I think we sorted this the other day for you, although your not a direct customer I obviously want you to get this sorted!

 

Yes it has been sorted. If this was because of something you did then I thank you.

 

@kim - I believe the address of the router had been blacklisted, but Craig might be able to confirm or deny this.

 

GJE

[kmount]

Ah....

[Messa]

The address had been blacklisted on our firewall this is usually due to, to many failed login attempts or similar...

 

Glad it's all working again for you Gareth

Edited May 22, 2010 by Messa