Hi all, Our current Call Manager 4.x servers are creaking under their age, and we are looking at replacing this either with a new Cisco telephony system or a completely new system altogether. The system has to use IP as the connection to the handsets, as we don't want to add in more cables. Has anyone any experience in deploying a new Call manager setup, or a similar telephony system, and how was the accessibility? Thanks. Andrew.
Asterisk / freeswich is not a bad way to go... I've also had good luck with the Sylantro gear if you have to spend money. Thanks Scott ----- Original Message ----- From: "Andrew Hodgson" <andrew@hodgsonfamily.org> To: "Blind sysadmins list" <blind-sysadmins@lists.hodgsonfamily.org> Sent: Tuesday, January 12, 2010 3:01 PM Subject: [Blind-sysadmins] Telephony systems Hi all, Our current Call Manager 4.x servers are creaking under their age, and we are looking at replacing this either with a new Cisco telephony system or a completely new system altogether. The system has to use IP as the connection to the handsets, as we don't want to add in more cables. Has anyone any experience in deploying a new Call manager setup, or a similar telephony system, and how was the accessibility? Thanks. Andrew. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/mailman/listinfo/blind-sysadmins
I have a friend who set up his asterisk system to take the subject line of an email address, pass it to festival to create a sound file, and then send the sound file out via asterisk as a phone message. In other words, he can have his asterisk system call his cell phone and read him the subject line of an email message. So, if for example, he gets an email from a system monitoring program like nagios, it calls his cell phone. ----- Original Message ----- From: "Scott Granados" <scott@granados-llc.net> To: "Blind sysadmins list" <blind-sysadmins@lists.hodgsonfamily.org> Sent: Tuesday, January 12, 2010 5:36 PM Subject: Re: [Blind-sysadmins] Telephony systems
Asterisk / freeswich is not a bad way to go...
I've also had good luck with the Sylantro gear if you have to spend money.
Thanks Scott
----- Original Message ----- From: "Andrew Hodgson" <andrew@hodgsonfamily.org> To: "Blind sysadmins list" <blind-sysadmins@lists.hodgsonfamily.org> Sent: Tuesday, January 12, 2010 3:01 PM Subject: [Blind-sysadmins] Telephony systems
Hi all,
Our current Call Manager 4.x servers are creaking under their age, and we are looking at replacing this either with a new Cisco telephony system or a completely new system altogether. The system has to use IP as the connection to the handsets, as we don't want to add in more cables.
Has anyone any experience in deploying a new Call manager setup, or a similar telephony system, and how was the accessibility?
Thanks. Andrew. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/mailman/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/mailman/listinfo/blind-sysadmins
Asterisk is good that way, you can do all sorts of cool tricks like that since you're just managing channels and everything is a channel to something else. I'm thinking of doing an experiment and switching over to all video phones at home / have a few at work and using some of the decent SIP packages out there to video call from my netbook. All I need is a flying car (maybe a Molllar car) and I'll be well on my way to realizing my Jetsons lifestyle I was promised by cartoons all these years. Actually I think it sounds like a fun learning excersize. I want to also play with the SIP support in windows mobile and try to build my own Asterisk switch that manages my life / I route all my communications through. ----- Original Message ----- From: "John G. Heim" <jheim@math.wisc.edu> To: "Blind sysadmins list" <blind-sysadmins@lists.hodgsonfamily.org> Sent: Wednesday, January 13, 2010 7:03 AM Subject: Re: [Blind-sysadmins] Telephony systems I have a friend who set up his asterisk system to take the subject line of an email address, pass it to festival to create a sound file, and then send the sound file out via asterisk as a phone message. In other words, he can have his asterisk system call his cell phone and read him the subject line of an email message. So, if for example, he gets an email from a system monitoring program like nagios, it calls his cell phone. ----- Original Message ----- From: "Scott Granados" <scott@granados-llc.net> To: "Blind sysadmins list" <blind-sysadmins@lists.hodgsonfamily.org> Sent: Tuesday, January 12, 2010 5:36 PM Subject: Re: [Blind-sysadmins] Telephony systems
Asterisk / freeswich is not a bad way to go...
I've also had good luck with the Sylantro gear if you have to spend money.
Thanks Scott
----- Original Message ----- From: "Andrew Hodgson" <andrew@hodgsonfamily.org> To: "Blind sysadmins list" <blind-sysadmins@lists.hodgsonfamily.org> Sent: Tuesday, January 12, 2010 3:01 PM Subject: [Blind-sysadmins] Telephony systems
Hi all,
Our current Call Manager 4.x servers are creaking under their age, and we are looking at replacing this either with a new Cisco telephony system or a completely new system altogether. The system has to use IP as the connection to the handsets, as we don't want to add in more cables.
Has anyone any experience in deploying a new Call manager setup, or a similar telephony system, and how was the accessibility?
Thanks. Andrew. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/mailman/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/mailman/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/mailman/listinfo/blind-sysadmins
Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie
Hi Darragh: On the first problem, there are a few ways I've worked around this. With a Windows 7 RDP client RDPing to a Windows Server 2008R2 machine, all the login information is asked for on the client end before the connection is even made. You can force this on earlier connections by checking the show more box, and then entering a username and password. I also have just memorized the steps, for example, on Windows Server 2003, once the connection is made, alt+u username, alt+p password, enter works. Sometimes you need to do enter, alt+u username, alt+p password, enter if you have a login banner like we do on some of our machines. Windows Server 2008, not 2008R2, can be more difficult because the usernames appearing on the login screen can vary, but in that case you can force the client to ask for credentials, and most of the time if it's a server you and only you log into, your name will be the default. On the second problem, I use Window-Eyes, not JAWS, so can't comment accept to say I've not seen this abnormally, AKA no more in an RDP session than I'd see it on a standard console session, so I'd guess it's a JAWS issue. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 6:47 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Access using remote desktop. Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hi Darragh: On the first problem, there are a few ways I've worked around this. With a Windows 7 RDP client RDPing to a Windows Server 2008R2 machine, all the login information is asked for on the client end before the connection is even made. You can force this on earlier connections by checking the show more box, and then entering a username and password. I also have just memorized the steps, for example, on Windows Server 2003, once the connection is made, alt+u username, alt+p password, enter works. Sometimes you need to do enter, alt+u username, alt+p password, enter if you have a login banner like we do on some of our machines. Windows Server 2008, not 2008R2, can be more difficult because the usernames appearing on the login screen can vary, but in that case you can force the client to ask for credentials, and most of the time if it's a server you and only you log into, your name will be the default. On the second problem, I use Window-Eyes, not JAWS, so can't comment accept to say I've not seen this abnormally, AKA no more in an RDP session than I'd see it on a standard console session, so I'd guess it's a JAWS issue. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 6:47 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Access using remote desktop. Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Your definitly right, You can fource the log information to be provided before the remote desktop session starts however for reading remote errors it would be great to have a screen running. I know that's not possible at the moment though. Specifically, I was trying to access a test desktop with a newly created temporary test account in a specific OU. I had forgotten to give the user remote desktop access permissions so I was getting an error on the remote end. If jaws had read that error it would have saved me a lot of time. Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie From: Ryan Shugart <rshugart@pcisys.net> To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Date: 12/07/2011 14:25 Subject: Re: [Blind-sysadmins] Access using remote desktop. Sent by: blind-sysadmins-bounces@lists.hodgsonfamily.org Hi Darragh: On the first problem, there are a few ways I've worked around this. With a Windows 7 RDP client RDPing to a Windows Server 2008R2 machine, all the login information is asked for on the client end before the connection is even made. You can force this on earlier connections by checking the show more box, and then entering a username and password. I also have just memorized the steps, for example, on Windows Server 2003, once the connection is made, alt+u username, alt+p password, enter works. Sometimes you need to do enter, alt+u username, alt+p password, enter if you have a login banner like we do on some of our machines. Windows Server 2008, not 2008R2, can be more difficult because the usernames appearing on the login screen can vary, but in that case you can force the client to ask for credentials, and most of the time if it's a server you and only you log into, your name will be the default. On the second problem, I use Window-Eyes, not JAWS, so can't comment accept to say I've not seen this abnormally, AKA no more in an RDP session than I'd see it on a standard console session, so I'd guess it's a JAWS issue. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [ mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 6:47 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Access using remote desktop. Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Your definitly right, You can fource the log information to be provided before the remote desktop session starts however for reading remote errors it would be great to have a screen running. I know that's not possible at the moment though. Specifically, I was trying to access a test desktop with a newly created temporary test account in a specific OU. I had forgotten to give the user remote desktop access permissions so I was getting an error on the remote end. If jaws had read that error it would have saved me a lot of time. Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie From: Ryan Shugart <rshugart@pcisys.net> To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Date: 12/07/2011 14:25 Subject: Re: [Blind-sysadmins] Access using remote desktop. Sent by: blind-sysadmins-bounces@lists.hodgsonfamily.org Hi Darragh: On the first problem, there are a few ways I've worked around this. With a Windows 7 RDP client RDPing to a Windows Server 2008R2 machine, all the login information is asked for on the client end before the connection is even made. You can force this on earlier connections by checking the show more box, and then entering a username and password. I also have just memorized the steps, for example, on Windows Server 2003, once the connection is made, alt+u username, alt+p password, enter works. Sometimes you need to do enter, alt+u username, alt+p password, enter if you have a login banner like we do on some of our machines. Windows Server 2008, not 2008R2, can be more difficult because the usernames appearing on the login screen can vary, but in that case you can force the client to ask for credentials, and most of the time if it's a server you and only you log into, your name will be the default. On the second problem, I use Window-Eyes, not JAWS, so can't comment accept to say I've not seen this abnormally, AKA no more in an RDP session than I'd see it on a standard console session, so I'd guess it's a JAWS issue. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [ mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 6:47 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Access using remote desktop. Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
You're right, it's a big bummer we can't get that kind of information. My own personal example is with password expirations. We have several template base images where the local administrator password you're supposed to use to log onto the machine to do the setup before joining it to the domain has expired. It's a real pain, and sometimes the easiest approach is to just get a friendly pair of eyes to walk me through the process. Still very annoying though. One thing that might be worth trying, although this will totally depend on your network connectivity and how your machines are set up, is to try running Narrator. It gives me horrible performance over RDP, but I have gotten it to work from time to time. By default, sound is turned off on server versions of Windows, I turn the audio services on when I build templates for things like this, and they can also be enabled through GPOs. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 7:30 AM To: Blind sysadmins list Cc: blind-sysadmins-bounces@lists.hodgsonfamily.org Subject: Re: [Blind-sysadmins] Access using remote desktop. Your definitly right, You can fource the log information to be provided before the remote desktop session starts however for reading remote errors it would be great to have a screen running. I know that's not possible at the moment though. Specifically, I was trying to access a test desktop with a newly created temporary test account in a specific OU. I had forgotten to give the user remote desktop access permissions so I was getting an error on the remote end. If jaws had read that error it would have saved me a lot of time. Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie From: Ryan Shugart <rshugart@pcisys.net> To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Date: 12/07/2011 14:25 Subject: Re: [Blind-sysadmins] Access using remote desktop. Sent by: blind-sysadmins-bounces@lists.hodgsonfamily.org Hi Darragh: On the first problem, there are a few ways I've worked around this. With a Windows 7 RDP client RDPing to a Windows Server 2008R2 machine, all the login information is asked for on the client end before the connection is even made. You can force this on earlier connections by checking the show more box, and then entering a username and password. I also have just memorized the steps, for example, on Windows Server 2003, once the connection is made, alt+u username, alt+p password, enter works. Sometimes you need to do enter, alt+u username, alt+p password, enter if you have a login banner like we do on some of our machines. Windows Server 2008, not 2008R2, can be more difficult because the usernames appearing on the login screen can vary, but in that case you can force the client to ask for credentials, and most of the time if it's a server you and only you log into, your name will be the default. On the second problem, I use Window-Eyes, not JAWS, so can't comment accept to say I've not seen this abnormally, AKA no more in an RDP session than I'd see it on a standard console session, so I'd guess it's a JAWS issue. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [ mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 6:47 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Access using remote desktop. Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
You're right, it's a big bummer we can't get that kind of information. My own personal example is with password expirations. We have several template base images where the local administrator password you're supposed to use to log onto the machine to do the setup before joining it to the domain has expired. It's a real pain, and sometimes the easiest approach is to just get a friendly pair of eyes to walk me through the process. Still very annoying though. One thing that might be worth trying, although this will totally depend on your network connectivity and how your machines are set up, is to try running Narrator. It gives me horrible performance over RDP, but I have gotten it to work from time to time. By default, sound is turned off on server versions of Windows, I turn the audio services on when I build templates for things like this, and they can also be enabled through GPOs. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 7:30 AM To: Blind sysadmins list Cc: blind-sysadmins-bounces@lists.hodgsonfamily.org Subject: Re: [Blind-sysadmins] Access using remote desktop. Your definitly right, You can fource the log information to be provided before the remote desktop session starts however for reading remote errors it would be great to have a screen running. I know that's not possible at the moment though. Specifically, I was trying to access a test desktop with a newly created temporary test account in a specific OU. I had forgotten to give the user remote desktop access permissions so I was getting an error on the remote end. If jaws had read that error it would have saved me a lot of time. Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie From: Ryan Shugart <rshugart@pcisys.net> To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Date: 12/07/2011 14:25 Subject: Re: [Blind-sysadmins] Access using remote desktop. Sent by: blind-sysadmins-bounces@lists.hodgsonfamily.org Hi Darragh: On the first problem, there are a few ways I've worked around this. With a Windows 7 RDP client RDPing to a Windows Server 2008R2 machine, all the login information is asked for on the client end before the connection is even made. You can force this on earlier connections by checking the show more box, and then entering a username and password. I also have just memorized the steps, for example, on Windows Server 2003, once the connection is made, alt+u username, alt+p password, enter works. Sometimes you need to do enter, alt+u username, alt+p password, enter if you have a login banner like we do on some of our machines. Windows Server 2008, not 2008R2, can be more difficult because the usernames appearing on the login screen can vary, but in that case you can force the client to ask for credentials, and most of the time if it's a server you and only you log into, your name will be the default. On the second problem, I use Window-Eyes, not JAWS, so can't comment accept to say I've not seen this abnormally, AKA no more in an RDP session than I'd see it on a standard console session, so I'd guess it's a JAWS issue. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [ mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 6:47 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Access using remote desktop. Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Very true. Narator is possibly an option. Hadn't thought of that. I wonder if windows u will work inside an RDP session before log in though.... Worth trying out. Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie From: Ryan Shugart <rshugart@pcisys.net> To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Date: 12/07/2011 15:44 Subject: Re: [Blind-sysadmins] Access using remote desktop. Sent by: blind-sysadmins-bounces@lists.hodgsonfamily.org You're right, it's a big bummer we can't get that kind of information. My own personal example is with password expirations. We have several template base images where the local administrator password you're supposed to use to log onto the machine to do the setup before joining it to the domain has expired. It's a real pain, and sometimes the easiest approach is to just get a friendly pair of eyes to walk me through the process. Still very annoying though. One thing that might be worth trying, although this will totally depend on your network connectivity and how your machines are set up, is to try running Narrator. It gives me horrible performance over RDP, but I have gotten it to work from time to time. By default, sound is turned off on server versions of Windows, I turn the audio services on when I build templates for things like this, and they can also be enabled through GPOs. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [ mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 7:30 AM To: Blind sysadmins list Cc: blind-sysadmins-bounces@lists.hodgsonfamily.org Subject: Re: [Blind-sysadmins] Access using remote desktop. Your definitly right, You can fource the log information to be provided before the remote desktop session starts however for reading remote errors it would be great to have a screen running. I know that's not possible at the moment though. Specifically, I was trying to access a test desktop with a newly created temporary test account in a specific OU. I had forgotten to give the user remote desktop access permissions so I was getting an error on the remote end. If jaws had read that error it would have saved me a lot of time. Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie From: Ryan Shugart <rshugart@pcisys.net> To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Date: 12/07/2011 14:25 Subject: Re: [Blind-sysadmins] Access using remote desktop. Sent by: blind-sysadmins-bounces@lists.hodgsonfamily.org Hi Darragh: On the first problem, there are a few ways I've worked around this. With a Windows 7 RDP client RDPing to a Windows Server 2008R2 machine, all the login information is asked for on the client end before the connection is even made. You can force this on earlier connections by checking the show more box, and then entering a username and password. I also have just memorized the steps, for example, on Windows Server 2003, once the connection is made, alt+u username, alt+p password, enter works. Sometimes you need to do enter, alt+u username, alt+p password, enter if you have a login banner like we do on some of our machines. Windows Server 2008, not 2008R2, can be more difficult because the usernames appearing on the login screen can vary, but in that case you can force the client to ask for credentials, and most of the time if it's a server you and only you log into, your name will be the default. On the second problem, I use Window-Eyes, not JAWS, so can't comment accept to say I've not seen this abnormally, AKA no more in an RDP session than I'd see it on a standard console session, so I'd guess it's a JAWS issue. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [ mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 6:47 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Access using remote desktop. Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Very true. Narator is possibly an option. Hadn't thought of that. I wonder if windows u will work inside an RDP session before log in though.... Worth trying out. Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie From: Ryan Shugart <rshugart@pcisys.net> To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Date: 12/07/2011 15:44 Subject: Re: [Blind-sysadmins] Access using remote desktop. Sent by: blind-sysadmins-bounces@lists.hodgsonfamily.org You're right, it's a big bummer we can't get that kind of information. My own personal example is with password expirations. We have several template base images where the local administrator password you're supposed to use to log onto the machine to do the setup before joining it to the domain has expired. It's a real pain, and sometimes the easiest approach is to just get a friendly pair of eyes to walk me through the process. Still very annoying though. One thing that might be worth trying, although this will totally depend on your network connectivity and how your machines are set up, is to try running Narrator. It gives me horrible performance over RDP, but I have gotten it to work from time to time. By default, sound is turned off on server versions of Windows, I turn the audio services on when I build templates for things like this, and they can also be enabled through GPOs. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [ mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 7:30 AM To: Blind sysadmins list Cc: blind-sysadmins-bounces@lists.hodgsonfamily.org Subject: Re: [Blind-sysadmins] Access using remote desktop. Your definitly right, You can fource the log information to be provided before the remote desktop session starts however for reading remote errors it would be great to have a screen running. I know that's not possible at the moment though. Specifically, I was trying to access a test desktop with a newly created temporary test account in a specific OU. I had forgotten to give the user remote desktop access permissions so I was getting an error on the remote end. If jaws had read that error it would have saved me a lot of time. Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie From: Ryan Shugart <rshugart@pcisys.net> To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Date: 12/07/2011 14:25 Subject: Re: [Blind-sysadmins] Access using remote desktop. Sent by: blind-sysadmins-bounces@lists.hodgsonfamily.org Hi Darragh: On the first problem, there are a few ways I've worked around this. With a Windows 7 RDP client RDPing to a Windows Server 2008R2 machine, all the login information is asked for on the client end before the connection is even made. You can force this on earlier connections by checking the show more box, and then entering a username and password. I also have just memorized the steps, for example, on Windows Server 2003, once the connection is made, alt+u username, alt+p password, enter works. Sometimes you need to do enter, alt+u username, alt+p password, enter if you have a login banner like we do on some of our machines. Windows Server 2008, not 2008R2, can be more difficult because the usernames appearing on the login screen can vary, but in that case you can force the client to ask for credentials, and most of the time if it's a server you and only you log into, your name will be the default. On the second problem, I use Window-Eyes, not JAWS, so can't comment accept to say I've not seen this abnormally, AKA no more in an RDP session than I'd see it on a standard console session, so I'd guess it's a JAWS issue. Ryan -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [ mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Tuesday, July 12, 2011 6:47 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Access using remote desktop. Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Greetings, I have 2 problems when using remote desktop. I'm assuming most if not all of you have these problems as well however in case you have a work-around I thought I'd post here. The first problem is I am unable to read the log in screen for any version of Windows when accessing it using remote desktop. This means that If trying to switch users in Windows 2008 or I get a log in error in Windows 2003 I am unable to read it. I'm using the Jaws screen reader. I don't expect that there's a work-around for this. Do any of you have a way of reading log in errors when accessing a system using remote desktop? The next problem is something I've been reporting for years. It was fixed for a while around Jaws 9 or 10 however it's back again. In fairness, I'm not totally convinced it's an issue caused by Jaws any more. The alt or control keys seem to stick when using a remote desktop. For example, after pressing alt tab a few times then pressing alt F4 you might find that if you press the letter e, alt is still pressed even though on the physical keyboard it's not pressed at all. I have spoken to people in FS right from Eric to the tech support people. They seem unable to reproduce the problem or unable to resolve it. I however can reproduce it in seconds on any system I use. I have also experienced this problem when using tandem. Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie
Sorry, my questions are usually much more targeted at enterprise environments but this morning I'm thinking about my home set up. I've downsized a lot recently. From running Hyper-V on two dedicated 2900's and 2950's and PFSense on a dedicated appliance I've gone to running just one Linux server on a cut down Asus system. I had to do it for a number of reasons but basically, it was becoming too difficult to manage and do everything else as well. I'm encountering a limitation of my newly purchased Belkin router. It's an N600 and for various reasons it doesn't support any variant of DDWRT. external services are running fine thanks to it's port forwarding / virtual servers or what ever terminology it wants to use. So, on the internet I can access systems on port 80 or 443 etc. The problem is that inside the network, I cannot access these systems. I know that DNS etc is working fine because if I ping one of the hostnames it resolves to the public IP but if I try to access the system using http for example the traffic never gets to the server. I'm assuming it's getting stuck at the router side. The router is likely not forwarding traffic origionating from an internal address back through the router to the internal server. Weird ay? Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie
What you are talking about is known as hairpin nat. the expectation is that packets leave the local machines, go through to the router, then take a hairpin turn and get redirected back inside the network to the internal hosts. there are 3 ways of handling this as it should be noted that many router models do not support hairpin nat. The first filthy method is to alias www.whatever to internal ip addresses using hosts files c:\windows\system32\drivers\etc\hosts and do it on all the internal boxes. This means packets never hit the router so you don't need the hairpin nat at all. Googling might give you a way to turn on hairpin nat in the modem but this is unlikely. the 3rd method is to have internal and external dns, with the internal dns mapping the ips to internal machines and the external having the real stuff in it. this can be done with views on a copy of bind if your Linux box has it or something else. Hope this helps. I'm looking at dd-wrt myself but frankly the do this do this and do this but don't do this or you'll brick your router has me a bit scared especially as i'm running wrt54gs v1.1 devices for my testing. I know I can do hairpin nat on my Mikrotik however I have to add specific rules to the firewall to make it happen, messy. regards, Kerry. On 18/01/2012 7:13 PM, Darragh OHeiligh wrote:
Sorry, my questions are usually much more targeted at enterprise environments but this morning I'm thinking about my home set up.
I've downsized a lot recently. From running Hyper-V on two dedicated 2900's and 2950's and PFSense on a dedicated appliance I've gone to running just one Linux server on a cut down Asus system.
I had to do it for a number of reasons but basically, it was becoming too difficult to manage and do everything else as well.
I'm encountering a limitation of my newly purchased Belkin router. It's an N600 and for various reasons it doesn't support any variant of DDWRT.
external services are running fine thanks to it's port forwarding / virtual servers or what ever terminology it wants to use. So, on the internet I can access systems on port 80 or 443 etc.
The problem is that inside the network, I cannot access these systems. I know that DNS etc is working fine because if I ping one of the hostnames it resolves to the public IP but if I try to access the system using http for example the traffic never gets to the server. I'm assuming it's getting stuck at the router side. The router is likely not forwarding traffic origionating from an internal address back through the router to the internal server.
Weird ay?
Any ideas?
Thanks
Regards
Darragh Ó Héiligh Fujitsu
Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hi, Ah yes remember this terminology now, I was able to configure something similar on the ASA I have here using messy rules. Andrew. -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kerry Hoath Sent: 18 January 2012 11:37 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Routing on a Belkin router. What you are talking about is known as hairpin nat. the expectation is that packets leave the local machines, go through to the router, then take a hairpin turn and get redirected back inside the network to the internal hosts. there are 3 ways of handling this as it should be noted that many router models do not support hairpin nat. The first filthy method is to alias www.whatever to internal ip addresses using hosts files c:\windows\system32\drivers\etc\hosts and do it on all the internal boxes. This means packets never hit the router so you don't need the hairpin nat at all. Googling might give you a way to turn on hairpin nat in the modem but this is unlikely. the 3rd method is to have internal and external dns, with the internal dns mapping the ips to internal machines and the external having the real stuff in it. this can be done with views on a copy of bind if your Linux box has it or something else. Hope this helps. I'm looking at dd-wrt myself but frankly the do this do this and do this but don't do this or you'll brick your router has me a bit scared especially as i'm running wrt54gs v1.1 devices for my testing. I know I can do hairpin nat on my Mikrotik however I have to add specific rules to the firewall to make it happen, messy. regards, Kerry. On 18/01/2012 7:13 PM, Darragh OHeiligh wrote:
Sorry, my questions are usually much more targeted at enterprise environments but this morning I'm thinking about my home set up.
I've downsized a lot recently. From running Hyper-V on two dedicated 2900's and 2950's and PFSense on a dedicated appliance I've gone to running just one Linux server on a cut down Asus system.
I had to do it for a number of reasons but basically, it was becoming too difficult to manage and do everything else as well.
I'm encountering a limitation of my newly purchased Belkin router. It's an N600 and for various reasons it doesn't support any variant of DDWRT.
external services are running fine thanks to it's port forwarding / virtual servers or what ever terminology it wants to use. So, on the internet I can access systems on port 80 or 443 etc.
The problem is that inside the network, I cannot access these systems. I know that DNS etc is working fine because if I ping one of the hostnames it resolves to the public IP but if I try to access the system using http for example the traffic never gets to the server. I'm assuming it's getting stuck at the router side. The router is likely not forwarding traffic origionating from an internal address back through the router to the internal server.
Weird ay?
Any ideas?
Thanks
Regards
Darragh Ó Héiligh Fujitsu
Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hi, Ah yes remember this terminology now, I was able to configure something similar on the ASA I have here using messy rules. Andrew. -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kerry Hoath Sent: 18 January 2012 11:37 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Routing on a Belkin router. What you are talking about is known as hairpin nat. the expectation is that packets leave the local machines, go through to the router, then take a hairpin turn and get redirected back inside the network to the internal hosts. there are 3 ways of handling this as it should be noted that many router models do not support hairpin nat. The first filthy method is to alias www.whatever to internal ip addresses using hosts files c:\windows\system32\drivers\etc\hosts and do it on all the internal boxes. This means packets never hit the router so you don't need the hairpin nat at all. Googling might give you a way to turn on hairpin nat in the modem but this is unlikely. the 3rd method is to have internal and external dns, with the internal dns mapping the ips to internal machines and the external having the real stuff in it. this can be done with views on a copy of bind if your Linux box has it or something else. Hope this helps. I'm looking at dd-wrt myself but frankly the do this do this and do this but don't do this or you'll brick your router has me a bit scared especially as i'm running wrt54gs v1.1 devices for my testing. I know I can do hairpin nat on my Mikrotik however I have to add specific rules to the firewall to make it happen, messy. regards, Kerry. On 18/01/2012 7:13 PM, Darragh OHeiligh wrote:
Sorry, my questions are usually much more targeted at enterprise environments but this morning I'm thinking about my home set up.
I've downsized a lot recently. From running Hyper-V on two dedicated 2900's and 2950's and PFSense on a dedicated appliance I've gone to running just one Linux server on a cut down Asus system.
I had to do it for a number of reasons but basically, it was becoming too difficult to manage and do everything else as well.
I'm encountering a limitation of my newly purchased Belkin router. It's an N600 and for various reasons it doesn't support any variant of DDWRT.
external services are running fine thanks to it's port forwarding / virtual servers or what ever terminology it wants to use. So, on the internet I can access systems on port 80 or 443 etc.
The problem is that inside the network, I cannot access these systems. I know that DNS etc is working fine because if I ping one of the hostnames it resolves to the public IP but if I try to access the system using http for example the traffic never gets to the server. I'm assuming it's getting stuck at the router side. The router is likely not forwarding traffic origionating from an internal address back through the router to the internal server.
Weird ay?
Any ideas?
Thanks
Regards
Darragh Ó Héiligh Fujitsu
Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hi, I went through the same downsize exercise as you a few months back, including going with a cheaper ISP which provided me with a stock router which also exhibited this behaviour. I put up with it for a while, then had to upgrade to a Netgear router primarily because I wanted 1GB Ethernet ports, but as a side effect of doing this, I got to be able to go to servers on the inside via the external address. When I go through the router like this to get a connection, the web logs are showing the traffic as coming through the router's internal IP address, so it is obviously deliberately re-routing the traffic. I couldn't see any way of doing this in the cheaper Thomson router I was given by my ISP, but conversely, there is no way to switch the feature off in the Netgear either. Thanks. Andrew. -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: 18 January 2012 11:14 To: Blind sysadmins list Subject: [Blind-sysadmins] Routing on a Belkin router. Sorry, my questions are usually much more targeted at enterprise environments but this morning I'm thinking about my home set up. I've downsized a lot recently. From running Hyper-V on two dedicated 2900's and 2950's and PFSense on a dedicated appliance I've gone to running just one Linux server on a cut down Asus system. I had to do it for a number of reasons but basically, it was becoming too difficult to manage and do everything else as well. I'm encountering a limitation of my newly purchased Belkin router. It's an N600 and for various reasons it doesn't support any variant of DDWRT. external services are running fine thanks to it's port forwarding / virtual servers or what ever terminology it wants to use. So, on the internet I can access systems on port 80 or 443 etc. The problem is that inside the network, I cannot access these systems. I know that DNS etc is working fine because if I ping one of the hostnames it resolves to the public IP but if I try to access the system using http for example the traffic never gets to the server. I'm assuming it's getting stuck at the router side. The router is likely not forwarding traffic origionating from an internal address back through the router to the internal server. Weird ay? Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hi, I went through the same downsize exercise as you a few months back, including going with a cheaper ISP which provided me with a stock router which also exhibited this behaviour. I put up with it for a while, then had to upgrade to a Netgear router primarily because I wanted 1GB Ethernet ports, but as a side effect of doing this, I got to be able to go to servers on the inside via the external address. When I go through the router like this to get a connection, the web logs are showing the traffic as coming through the router's internal IP address, so it is obviously deliberately re-routing the traffic. I couldn't see any way of doing this in the cheaper Thomson router I was given by my ISP, but conversely, there is no way to switch the feature off in the Netgear either. Thanks. Andrew. -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: 18 January 2012 11:14 To: Blind sysadmins list Subject: [Blind-sysadmins] Routing on a Belkin router. Sorry, my questions are usually much more targeted at enterprise environments but this morning I'm thinking about my home set up. I've downsized a lot recently. From running Hyper-V on two dedicated 2900's and 2950's and PFSense on a dedicated appliance I've gone to running just one Linux server on a cut down Asus system. I had to do it for a number of reasons but basically, it was becoming too difficult to manage and do everything else as well. I'm encountering a limitation of my newly purchased Belkin router. It's an N600 and for various reasons it doesn't support any variant of DDWRT. external services are running fine thanks to it's port forwarding / virtual servers or what ever terminology it wants to use. So, on the internet I can access systems on port 80 or 443 etc. The problem is that inside the network, I cannot access these systems. I know that DNS etc is working fine because if I ping one of the hostnames it resolves to the public IP but if I try to access the system using http for example the traffic never gets to the server. I'm assuming it's getting stuck at the router side. The router is likely not forwarding traffic origionating from an internal address back through the router to the internal server. Weird ay? Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Isn't this an example of split DNS? Normally I would have a DNS server running on the LAN with a forward lookup zone that will resolve a name to an *internal* address. I am not familiar with that router but have never seen a DNS server built into a cheaper router that could handle this correctly. Frank -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Wednesday, January 18, 2012 6:14 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Routing on a Belkin router. Sorry, my questions are usually much more targeted at enterprise environments but this morning I'm thinking about my home set up. I've downsized a lot recently. From running Hyper-V on two dedicated 2900's and 2950's and PFSense on a dedicated appliance I've gone to running just one Linux server on a cut down Asus system. I had to do it for a number of reasons but basically, it was becoming too difficult to manage and do everything else as well. I'm encountering a limitation of my newly purchased Belkin router. It's an N600 and for various reasons it doesn't support any variant of DDWRT. external services are running fine thanks to it's port forwarding / virtual servers or what ever terminology it wants to use. So, on the internet I can access systems on port 80 or 443 etc. The problem is that inside the network, I cannot access these systems. I know that DNS etc is working fine because if I ping one of the hostnames it resolves to the public IP but if I try to access the system using http for example the traffic never gets to the server. I'm assuming it's getting stuck at the router side. The router is likely not forwarding traffic origionating from an internal address back through the router to the internal server. Weird ay? Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Isn't this an example of split DNS? Normally I would have a DNS server running on the LAN with a forward lookup zone that will resolve a name to an *internal* address. I am not familiar with that router but have never seen a DNS server built into a cheaper router that could handle this correctly. Frank -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Wednesday, January 18, 2012 6:14 AM To: Blind sysadmins list Subject: [Blind-sysadmins] Routing on a Belkin router. Sorry, my questions are usually much more targeted at enterprise environments but this morning I'm thinking about my home set up. I've downsized a lot recently. From running Hyper-V on two dedicated 2900's and 2950's and PFSense on a dedicated appliance I've gone to running just one Linux server on a cut down Asus system. I had to do it for a number of reasons but basically, it was becoming too difficult to manage and do everything else as well. I'm encountering a limitation of my newly purchased Belkin router. It's an N600 and for various reasons it doesn't support any variant of DDWRT. external services are running fine thanks to it's port forwarding / virtual servers or what ever terminology it wants to use. So, on the internet I can access systems on port 80 or 443 etc. The problem is that inside the network, I cannot access these systems. I know that DNS etc is working fine because if I ping one of the hostnames it resolves to the public IP but if I try to access the system using http for example the traffic never gets to the server. I'm assuming it's getting stuck at the router side. The router is likely not forwarding traffic origionating from an internal address back through the router to the internal server. Weird ay? Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Sorry, my questions are usually much more targeted at enterprise environments but this morning I'm thinking about my home set up. I've downsized a lot recently. From running Hyper-V on two dedicated 2900's and 2950's and PFSense on a dedicated appliance I've gone to running just one Linux server on a cut down Asus system. I had to do it for a number of reasons but basically, it was becoming too difficult to manage and do everything else as well. I'm encountering a limitation of my newly purchased Belkin router. It's an N600 and for various reasons it doesn't support any variant of DDWRT. external services are running fine thanks to it's port forwarding / virtual servers or what ever terminology it wants to use. So, on the internet I can access systems on port 80 or 443 etc. The problem is that inside the network, I cannot access these systems. I know that DNS etc is working fine because if I ping one of the hostnames it resolves to the public IP but if I try to access the system using http for example the traffic never gets to the server. I'm assuming it's getting stuck at the router side. The router is likely not forwarding traffic origionating from an internal address back through the router to the internal server. Weird ay? Any ideas? Thanks Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie
Hello, I know one or two of you here use Nagios. I tried that but unfortunately this is very much a point and click type company so the thought's of editing conf files fills management with fear and dred. we have SCOM here and they like it a lot. I get about 256 messages a week that are absolutely useless but hey, if management are happy then I'm happy. I was just wondering if anyone who uses SCOM has customized it to send out any nice alerts? Do you have SMS or any phone integration? What about TTS? Is there anything i can do to make this useful? I have it set up so that it displays a few dashboards on a big screen in this office but although management like the security of nice colourful images, I think a dodgy toaster would probably be more interesting from my perspective. Any thought's welcome. Darragh
Hello, I know one or two of you here use Nagios. I tried that but unfortunately this is very much a point and click type company so the thought's of editing conf files fills management with fear and dred. we have SCOM here and they like it a lot. I get about 256 messages a week that are absolutely useless but hey, if management are happy then I'm happy. I was just wondering if anyone who uses SCOM has customized it to send out any nice alerts? Do you have SMS or any phone integration? What about TTS? Is there anything i can do to make this useful? I have it set up so that it displays a few dashboards on a big screen in this office but although management like the security of nice colourful images, I think a dodgy toaster would probably be more interesting from my perspective. Any thought's welcome. Darragh
Are the alerts not relevant, or non-actionable? For non-actionable alerts, tune them in scom to email only, and not send SMS alerts. If the alert is not relevant, then perhaps the severity should be informational or disabled. A lot of the work in any monitoring system is tuning, and anything that comes up should be addressed so that you don't get alerted over and over again for things you don't need to respond to. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Monday, September 17, 2012 7:04 AM To: Blind sysadmins list Subject: [Blind-sysadmins] SCOM notifications. Hello, I know one or two of you here use Nagios. I tried that but unfortunately this is very much a point and click type company so the thought's of editing conf files fills management with fear and dred. we have SCOM here and they like it a lot. I get about 256 messages a week that are absolutely useless but hey, if management are happy then I'm happy. I was just wondering if anyone who uses SCOM has customized it to send out any nice alerts? Do you have SMS or any phone integration? What about TTS? Is there anything i can do to make this useful? I have it set up so that it displays a few dashboards on a big screen in this office but although management like the security of nice colourful images, I think a dodgy toaster would probably be more interesting from my perspective. Any thought's welcome. Darragh _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Hello, For the past year I have been working hard at trying to get Mcafee to make the web interface for their secure line of products accessible. This has not getting very far however I am now at a stage where I have direct contact with the product manager for the Secure web product. I have a way to go yet but I thought I'd send the list a quick mail with what has been the most promising update in twelve months. If you have any suggestions as to what I should do next I'm certainly open to them. This seems like an empty promis to me. No timelines, no definitive plans and a lot of talking in circles. Quoted mail begins: While the remarks made in context of this matter, are correct in regards to the Java technology being able to utilize the accessible assistance tools of Swing, I was assured by my engineering team that it would still not be fully supporting usage of the product in an accessible manner, which renders the decision to go with Java obviously problematic in the regard. I understand that you and especially the people affected by this are seeing this a decrease of functionality in capabilities in the product and I apologize for not respecting this fact. The question is, how did this happen? When we stated development of the new version, we didn't claim at all that Webwasher (historic name of the product) was supporting any technology that would allow screen readers or other tools to be used to administered the UI. Essentially it was a drop off from the HTML based technology we used back then. When the project started back in 2005, we first thought about continuing with a HTML/Javascript based frontend, whereas the AJAX technologies back in these days didn't deliver enough horse power to be used in conjunction with the product underlying capabilities. The decision to use Java was due to the fact that we could use client-side preprocessing of data to just feed that back to the backend and relief the backend from some operations – and Java was the only technology that could do that. In 2010, when 7 was released, the world had changed and the Ajax tools were much more powerful, so were the browsers, however we couldn't change the UI to something else, as this would have been dramatic delay. Having said, all this, the next question is, what are the plans? As we are not in a position to simply inject the assistive technology that Swing provides below a 2 years timeframe, we have taken a different approach. While we understand that the current UI is powerful and flexible and allows customer to do what they want, we also are aware of the fact that due to the freedom it provides, it limits certain customers, who are looking for an easy UI. We have started a priority initiative to create something that is called "Common UI". The commonality is in regards to the product using the UI – these are targeted to the Web products (appliance and SaaS), the emails products (appliance and SaaS) as well as the network security products in a later step. The key focus of this UI lies in easiness and plugin-less browser integration. The request to support assistive technology has been conveyed to the team in charge, which falls into the overall usability initiative that is embedded into this project. Mail ends: Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie Oireachtas email policy and disclaimer. http://www.oireachtas.ie/parliament/about/oireachtasemailpolicyanddisclaimer... Beartas ríomhphoist an Oireachtais agus séanadh. http://www.oireachtas.ie/parliament/ga/eolas/beartasriomhphoistanoireachtais...
Hello, For the past year I have been working hard at trying to get Mcafee to make the web interface for their secure line of products accessible. This has not getting very far however I am now at a stage where I have direct contact with the product manager for the Secure web product. I have a way to go yet but I thought I'd send the list a quick mail with what has been the most promising update in twelve months. If you have any suggestions as to what I should do next I'm certainly open to them. This seems like an empty promis to me. No timelines, no definitive plans and a lot of talking in circles. Quoted mail begins: While the remarks made in context of this matter, are correct in regards to the Java technology being able to utilize the accessible assistance tools of Swing, I was assured by my engineering team that it would still not be fully supporting usage of the product in an accessible manner, which renders the decision to go with Java obviously problematic in the regard. I understand that you and especially the people affected by this are seeing this a decrease of functionality in capabilities in the product and I apologize for not respecting this fact. The question is, how did this happen? When we stated development of the new version, we didn't claim at all that Webwasher (historic name of the product) was supporting any technology that would allow screen readers or other tools to be used to administered the UI. Essentially it was a drop off from the HTML based technology we used back then. When the project started back in 2005, we first thought about continuing with a HTML/Javascript based frontend, whereas the AJAX technologies back in these days didn't deliver enough horse power to be used in conjunction with the product underlying capabilities. The decision to use Java was due to the fact that we could use client-side preprocessing of data to just feed that back to the backend and relief the backend from some operations – and Java was the only technology that could do that. In 2010, when 7 was released, the world had changed and the Ajax tools were much more powerful, so were the browsers, however we couldn't change the UI to something else, as this would have been dramatic delay. Having said, all this, the next question is, what are the plans? As we are not in a position to simply inject the assistive technology that Swing provides below a 2 years timeframe, we have taken a different approach. While we understand that the current UI is powerful and flexible and allows customer to do what they want, we also are aware of the fact that due to the freedom it provides, it limits certain customers, who are looking for an easy UI. We have started a priority initiative to create something that is called "Common UI". The commonality is in regards to the product using the UI – these are targeted to the Web products (appliance and SaaS), the emails products (appliance and SaaS) as well as the network security products in a later step. The key focus of this UI lies in easiness and plugin-less browser integration. The request to support assistive technology has been conveyed to the team in charge, which falls into the overall usability initiative that is embedded into this project. Mail ends: Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie Oireachtas email policy and disclaimer. http://www.oireachtas.ie/parliament/about/oireachtasemailpolicyanddisclaimer... Beartas ríomhphoist an Oireachtais agus séanadh. http://www.oireachtas.ie/parliament/ga/eolas/beartasriomhphoistanoireachtais...
Darragh, Sounds like a bunch of talking in circles to me. That is one reason I don't use their products any more. I am sorry I don't have any suggestions for where this should go next. I think the problem is that we as visually persons do not have the clout to really inconvenience the company. Sorry, I'm not helpful. Greg B. Email: gbobo@woh.rr.com -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Wednesday, November 14, 2012 3:41 AM To: Blind sysadmins list Subject: [Blind-sysadmins] McAfee secure web. Hello, For the past year I have been working hard at trying to get Mcafee to make the web interface for their secure line of products accessible. This has not getting very far however I am now at a stage where I have direct contact with the product manager for the Secure web product. I have a way to go yet but I thought I'd send the list a quick mail with what has been the most promising update in twelve months. If you have any suggestions as to what I should do next I'm certainly open to them. This seems like an empty promis to me. No timelines, no definitive plans and a lot of talking in circles. Quoted mail begins: While the remarks made in context of this matter, are correct in regards to the Java technology being able to utilize the accessible assistance tools of Swing, I was assured by my engineering team that it would still not be fully supporting usage of the product in an accessible manner, which renders the decision to go with Java obviously problematic in the regard. I understand that you and especially the people affected by this are seeing this a decrease of functionality in capabilities in the product and I apologize for not respecting this fact. The question is, how did this happen? When we stated development of the new version, we didn't claim at all that Webwasher (historic name of the product) was supporting any technology that would allow screen readers or other tools to be used to administered the UI. Essentially it was a drop off from the HTML based technology we used back then. When the project started back in 2005, we first thought about continuing with a HTML/Javascript based frontend, whereas the AJAX technologies back in these days didn't deliver enough horse power to be used in conjunction with the product underlying capabilities. The decision to use Java was due to the fact that we could use client-side preprocessing of data to just feed that back to the backend and relief the backend from some operations – and Java was the only technology that could do that. In 2010, when 7 was released, the world had changed and the Ajax tools were much more powerful, so were the browsers, however we couldn't change the UI to something else, as this would have been dramatic delay. Having said, all this, the next question is, what are the plans? As we are not in a position to simply inject the assistive technology that Swing provides below a 2 years timeframe, we have taken a different approach. While we understand that the current UI is powerful and flexible and allows customer to do what they want, we also are aware of the fact that due to the freedom it provides, it limits certain customers, who are looking for an easy UI. We have started a priority initiative to create something that is called "Common UI". The commonality is in regards to the product using the UI – these are targeted to the Web products (appliance and SaaS), the emails products (appliance and SaaS) as well as the network security products in a later step. The key focus of this UI lies in easiness and plugin-less browser integration. The request to support assistive technology has been conveyed to the team in charge, which falls into the overall usability initiative that is embedded into this project. Mail ends: Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie Oireachtas email policy and disclaimer. http://www.oireachtas.ie/parliament/about/oireachtasemailpolicyanddisclaimer... Beartas ríomhphoist an Oireachtais agus séanadh. http://www.oireachtas.ie/parliament/ga/eolas/beartasriomhphoistanoireachtais... _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Oops I meant to say visually impaired persons. Greg B. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Wednesday, November 14, 2012 3:41 AM To: Blind sysadmins list Subject: [Blind-sysadmins] McAfee secure web. Hello, For the past year I have been working hard at trying to get Mcafee to make the web interface for their secure line of products accessible. This has not getting very far however I am now at a stage where I have direct contact with the product manager for the Secure web product. I have a way to go yet but I thought I'd send the list a quick mail with what has been the most promising update in twelve months. If you have any suggestions as to what I should do next I'm certainly open to them. This seems like an empty promis to me. No timelines, no definitive plans and a lot of talking in circles. Quoted mail begins: While the remarks made in context of this matter, are correct in regards to the Java technology being able to utilize the accessible assistance tools of Swing, I was assured by my engineering team that it would still not be fully supporting usage of the product in an accessible manner, which renders the decision to go with Java obviously problematic in the regard. I understand that you and especially the people affected by this are seeing this a decrease of functionality in capabilities in the product and I apologize for not respecting this fact. The question is, how did this happen? When we stated development of the new version, we didn't claim at all that Webwasher (historic name of the product) was supporting any technology that would allow screen readers or other tools to be used to administered the UI. Essentially it was a drop off from the HTML based technology we used back then. When the project started back in 2005, we first thought about continuing with a HTML/Javascript based frontend, whereas the AJAX technologies back in these days didn't deliver enough horse power to be used in conjunction with the product underlying capabilities. The decision to use Java was due to the fact that we could use client-side preprocessing of data to just feed that back to the backend and relief the backend from some operations – and Java was the only technology that could do that. In 2010, when 7 was released, the world had changed and the Ajax tools were much more powerful, so were the browsers, however we couldn't change the UI to something else, as this would have been dramatic delay. Having said, all this, the next question is, what are the plans? As we are not in a position to simply inject the assistive technology that Swing provides below a 2 years timeframe, we have taken a different approach. While we understand that the current UI is powerful and flexible and allows customer to do what they want, we also are aware of the fact that due to the freedom it provides, it limits certain customers, who are looking for an easy UI. We have started a priority initiative to create something that is called "Common UI". The commonality is in regards to the product using the UI – these are targeted to the Web products (appliance and SaaS), the emails products (appliance and SaaS) as well as the network security products in a later step. The key focus of this UI lies in easiness and plugin-less browser integration. The request to support assistive technology has been conveyed to the team in charge, which falls into the overall usability initiative that is embedded into this project. Mail ends: Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie Oireachtas email policy and disclaimer. http://www.oireachtas.ie/parliament/about/oireachtasemailpolicyanddisclaimer... Beartas ríomhphoist an Oireachtais agus séanadh. http://www.oireachtas.ie/parliament/ga/eolas/beartasriomhphoistanoireachtais... _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Would you like me to ask IAVIT's lawyer if there is anything to do? -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Darragh OHeiligh Sent: Wednesday, November 14, 2012 2:41 AM To: Blind sysadmins list Subject: [Blind-sysadmins] McAfee secure web. Hello, For the past year I have been working hard at trying to get Mcafee to make the web interface for their secure line of products accessible. This has not getting very far however I am now at a stage where I have direct contact with the product manager for the Secure web product. I have a way to go yet but I thought I'd send the list a quick mail with what has been the most promising update in twelve months. If you have any suggestions as to what I should do next I'm certainly open to them. This seems like an empty promis to me. No timelines, no definitive plans and a lot of talking in circles. Quoted mail begins: While the remarks made in context of this matter, are correct in regards to the Java technology being able to utilize the accessible assistance tools of Swing, I was assured by my engineering team that it would still not be fully supporting usage of the product in an accessible manner, which renders the decision to go with Java obviously problematic in the regard. I understand that you and especially the people affected by this are seeing this a decrease of functionality in capabilities in the product and I apologize for not respecting this fact. The question is, how did this happen? When we stated development of the new version, we didn't claim at all that Webwasher (historic name of the product) was supporting any technology that would allow screen readers or other tools to be used to administered the UI. Essentially it was a drop off from the HTML based technology we used back then. When the project started back in 2005, we first thought about continuing with a HTML/Javascript based frontend, whereas the AJAX technologies back in these days didn't deliver enough horse power to be used in conjunction with the product underlying capabilities. The decision to use Java was due to the fact that we could use client-side preprocessing of data to just feed that back to the backend and relief the backend from some operations – and Java was the only technology that could do that. In 2010, when 7 was released, the world had changed and the Ajax tools were much more powerful, so were the browsers, however we couldn't change the UI to something else, as this would have been dramatic delay. Having said, all this, the next question is, what are the plans? As we are not in a position to simply inject the assistive technology that Swing provides below a 2 years timeframe, we have taken a different approach. While we understand that the current UI is powerful and flexible and allows customer to do what they want, we also are aware of the fact that due to the freedom it provides, it limits certain customers, who are looking for an easy UI. We have started a priority initiative to create something that is called "Common UI". The commonality is in regards to the product using the UI – these are targeted to the Web products (appliance and SaaS), the emails products (appliance and SaaS) as well as the network security products in a later step. The key focus of this UI lies in easiness and plugin-less browser integration. The request to support assistive technology has been conveyed to the team in charge, which falls into the overall usability initiative that is embedded into this project. Mail ends: Regards Darragh Ó Héiligh Fujitsu Offices of the Houses of the Oireachtas, Fredrick Building, South Fredrick Street, Dublin2 Telephone: +353 (1) 618 3559 Email: darragh.oheiligh@oireachtas.ie Internet: http://www.oireachtas.ie Oireachtas email policy and disclaimer. http://www.oireachtas.ie/parliament/about/oireachtasemailpolicyanddisclaimer... Beartas ríomhphoist an Oireachtais agus séanadh. http://www.oireachtas.ie/parliament/ga/eolas/beartasriomhphoistanoireachtais... _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
participants (9)
-
Andrew Hodgson -
Darragh OHeiligh -
Frank Ventura -
Greg B. -
JoeY -
John G. Heim -
Kerry Hoath -
Ryan Shugart -
Scott Granados