View Full Version : Help needed to test connection.
webmaster
04-09-2003, 14:02
A member has been experiencing problems trying to connect to www.bsac.com . The problem seems to be a break in the internet connection with an onscreen "fatal error" message.
Has anyone else experienced this problem?
Could I ask you to help by making a test connection to www.bsac.com (from the link below if you like) and let me know if you experience any problems.
This will help us determine whether the problem is at the user or ISP end, or at our end.
Thanks for your help.
Mike
lynn jackson
04-09-2003, 14:36
It came up immediately for me. and I'm wrestling with a dodgy Pc at the mo.
It's probably his end with a modem/browser problem. Get him to ping your IP address...
A member has been experiencing problems trying to connect to www.bsac.com . The problem seems to be a break in the internet connection with an onscreen "fatal error" message.
Has anyone else experienced this problem?
Could I ask you to help by making a test connection to www.bsac.com (from the link below if you like) and let me know if you experience any problems.
This will help us determine whether the problem is at the user or ISP end, or at our end.
Thanks for your help.
Mike
works fine for me.
Stu.
Tony Dwyer
04-09-2003, 15:42
Came up fine for me. I'm linked via a laptop with a wireless network connection to a LAN connected to a broadband modem via a router.
It seems ok to me.
Keith Lawrence(BSAC)
04-09-2003, 18:13
Works fine from here Mike. I'm getting 20ms pings, DNS is resolving fine and I'm 15 hops away on a tracert!
It could be either a local or an ISP problem at the users end. But it's worth asking if they've got the file c:\windows\system32\msblast.exe on their PC, that can cause the symptoms being described - just tell them to remove the Blaster virus and all should be well :-)
Keith L
> This will help us determine whether the problem is at the user
> or ISP end, or at our end.
Try getting him to connect to <a href="http://217.206.220.236/" >http://217.206.220.236/</a> - that will rule out any DNS issues. Mind you, I'd expected to see a BSAC page there - but no matter; what's important is whether or not he sees anything. If he does - he can contact the server. That, then, would make it a DNS issue (and there are ways around that if his ISP won't fix it).
If there's no joy from the above then there's some sort of connection problem - we'd need to know a bit more about his configuration (i.e. is he behind a firewall?) before making any real suggestions, although a ping is always a good test (d236 does reply to pings).
It's probably worth checking the Apache logs as well to see if we're seeing any traffic from his IP address.
HTH
Vic.
john bache
07-09-2003, 23:29
Works for me.
vBulletin v3.5.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.