You got me in trouble at work

[Deleted member 30853]

Right, it appears my works IP address has been blocked at this end. When it was blocked, access was blocked to the main "Ready to Go" and the "SMB" for at least three other people as well as me.

As regards my remarks over on FTB, yes I can bypass the IP block if I want - that is evident as I'm still posting during the day. However, when you deploy an IP address block you also affect other people and that is not fair on them. So let's have the IP address block lifted if not for my benefit, for the other posters that have been affected as they don't deserve to be punished for anything I've said or done.

Work has become aware that something is wrong and I've been ticked off by my IT department as a result.

Ian

 

[RTGAdmin]

We don't do IP blocks - so I think you will find it is your IT department that are blocking us in the 1st place!

 

[Deleted member 30853]

We don't do IP blocks - so I think you will find it is your IT department that are blocking us in the 1st place!

Nah, it's a timeout that is definitely coming from the Ready to Go end mate from the message on the screen. If it was our end, there'd be a big message saying my employer had blocked the website and my IP had been reported to IT Admin in Texas. I'll do a screengrab at work if you want.

IT became aware as others complained to IT they couldn't access here on a lunchtime and they said they hadn't blocked it. Our IT don't even block Facebook or Twitter. Only the porn is blocked.

As it was, IT just gave me grief for being a Mackem.[DOUBLEPOST=1397048979][/DOUBLEPOST]To add to the above, a TRACERT trace shows the block NOT to be my company's host server.

The trace is halted on reaching UKFAST.NET in Manchester. My company's server is in Norway.

 

[PTR]

By the way, the devices after ukfast.net simply don't respond to echo requests:

Tracing route to readytogo.net [159.253.212.32]
over a maximum of 30 hops:

1 40 ms 99 ms 100 ms [My LAN]
2 65 ms 59 ms 30 ms [My ISP switches and routers]
]
3 38 ms 38 ms 38 ms [My ISP switches and routers]
2]
4 39 ms 41 ms 36 ms [My ISP switches and routers]
5 39 ms 37 ms 38 ms [My ISP switches and routers]
6 37 ms 37 ms 37 ms [My ISP switches and routers]
7 37 ms 37 ms 39 ms 195.99.126.138
8 * * * Request timed out.
9 43 ms 45 ms 42 ms mcr-ifl-c1k1-te1-0-0.ukfast.net.uk [37.220.95.17
]
10 45 ms 43 ms 44 ms 37.220.95.34.srvlist.ukfast.net [37.220.95.34]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18

Just because you're not getting the "This site is blocked" page, doesn't mean they haven't simply added a block to a certain IP or site on the Proxy or ISA server.

 

[Roger]

correct, tracert and pings will always end at the UKFAST firewalls, long before our server - I see the same.

It is possible for an ip block to be added automatically on the server firewall, but that will only happen if there have been multiple attempts to hack into the server from that IP address. Message board failed logons etc do not count as a hack, so it would only be failed attempts to logon to control panels, ssh etc.

Unless someone in your company is attempting to hack into the server this would not happen.