[BarNunBoi]

I am having a huge problem! Clients can't access my website for some reason. When they try to access it from IE they get IE can't display this website. Its weird because I can access the site from home and from work! What could be the problem here!!??

[jimblumberg]

What browser are you using to view your site? If you are using IE is it the same version as your clients?

Jim

[no2pencil]

Without knowing the url, it's difficult to replicate the situation.

[BarNunBoi]

Personally I use Chrome.....one client contacted me and said that he tried all browsers and wasn't able to connect to the server.

This post has been edited by BarNunBoi: 13 August 2012 - 12:42 PM

[BarNunBoi]

This is what I get when pinging from http://www.his.com/cgi-bin/ping?


FROM www.his.com TO xxxxxxxxxx
PING xxxxxxxxxxx (xxxxxxxxx): 56 data bytes

--- xxxxxxxxxxxxxx ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

This post has been edited by BarNunBoi: 13 August 2012 - 06:45 PM

[no2pencil]

Traceroute dies off at hop #13 :

Quote

11 bb-dllstx37-jx9-01-ae0.core.centurytel.net (206.51.69.57) 257.529 ms 261.898 ms 295.584 ms
12 206.51.81.1 (206.51.81.1) 110.319 ms 76.562 ms 249.063 ms
13 tx-74-5-125-150.sta.embarqhsd.net (74.5.125.150) 249.092 ms 249.154 ms 249.218 ms
14 * * *

[BarNunBoi]

@Pencil do you have the whole list so I can see it..everytime I do a tracert from my machine I get request timed out.....also does this mean that the problem is not on the local server? Sorry Im asking so many questions....I am not an Network Admin!

This post has been edited by BarNunBoi: 13 August 2012 - 01:24 PM

[no2pencil]

BarNunBoi, on 13 August 2012 - 04:13 PM, said:

@Pencil do you have the whole list so I can see it..everytime I do a tracert from my machine I get request timed out.....

The problem is that it's timing out. Where do you see the timouts? Right away, or after a few hops?

BarNunBoi, on 13 August 2012 - 04:13 PM, said:

also does this mean that the problem is not on the local server?

This depends on where you see the timeouts.

A larger question would be, who is in charge of your network? They should be notified, & they can troubleshoot further. Even if we knew what was wrong, we can't fix it remotely.

[BarNunBoi]

It times out immediately when I do a tracert and a ping

[no2pencil]

Then likely the problem is within your building. I would suggest power cycling any routers, switches, hubs, or other networking equipment.

Again, you really should have the networking guys present when you are troubleshooting this.

I'm curious what happens when you try a traceroute to a known working source, like google.com?

[BarNunBoi]

when I do a ping to google I get replys and after 4-5 seconds the box closes!

[BarNunBoi]

Question: if my trace-rt dies at hop 13 and the connection never reaches me does that mean that the problem I am experiencing is external?

[no2pencil]

The hop number alone does not give insight to the issue. It only provides the last known good hop. If the last hop was your isp, then the problem is likely with their equipment, or internal.

If not, you can call your isp & provide to them the information & see if they will help diagnose.

[BarNunBoi]

Hey guys,
I have a quick question. I am responsible from up keeping a legacy website for my job and for some reason people can't get to it from outside our local network! With that said, I am totally new to ASP.NET. My question is...is there anything in ASP.NET config files that could keep people from outside my network from getting in? I have looked through the config files and couldn't find anything. Also I have did tracert's and pinged the website. I get request timed out when I pinged. Also when I do I tracert....one of the hops stops short of getting to my location. Any input would be greatly appreciated! Thanks!!

[rgfirefly24]

there are so many reasons why outside people can't get to your site. IIS Could not be configured right, the server you setup the website on is not accessable from outside. There are more, but I can't think of them offhand. As far as from your website itself, unless you have explicitly stated <deny users="*" /> in the <authorization> section of <system.web> then it shouldn't be effecting it.

This post has been edited by rgfirefly24: 24 September 2012 - 07:10 AM