Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


touchring

Member
  • Content Count

    5
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About touchring

Profile Information

  • OS
    Server 2008 x86
  1. Hi, i'm offering some SMS (SMPP) service from my Win 2003 server to my clients (over the Internet), which i need to redirect to the actual SMPP server (also via the Internet). The traffic will be 2-way. My clients will be connecting to my server instead of directly to the actual server providing the service. Can this be done? Glad for any pointer.
  2. Firstly, I'm not sure if this is the right place to post my question. I need to implement 2 factor authentication for my Windows logon and would like to know if a GINA STUB can fulfill my requirement or do I need to write the entire GINA DLL? I read there are risks in implementing the whole GINA so I will like to avoid that. The flow: 1. Initial Authentication: The user enters the username and password on the logon screen, the logon credentials are then used to authenticate against a remote authentication server. -------------------------------------------------------------------------- "Please enter your Username and domain password" USERNAME: [ ] PASSWORD: [ ] -------------------------------------------------------------------------- Alternatively, the credentials can also be used to logon to Windows or AD (as in the usual process), but I should be able to intercept and prevent the user from actually logging in whether or not the credentials have been successfully authenticated - this is because another set of logon credentials (2nd factor) must be submitted before finally allowing access. 2. 2nd Factor: If the first authentication fails, the user is presented with the failure message returned by the remote authentication server, and the first logon screen is presented again. On success, an OTP or one-time-pass-word will be sent to the user, and the user is then presented with another logon screen which looks like the following. The user enters the username and OTP. -------------------------------------------------------------------------- "Please enter the OTP which you have received" USERNAME: [ ] OTP: [ ] -------------------------------------------------------------------------- The logon credentials will then be submitted to the authentication server again. If the OTP is correct, the user will be allowed to logon to the machine for real and i should be able to log this event. If OTP authentication fails, the user is presented with the failure message returned by the remote authentication server, and the following logon screen is presented: -------------------------------------------------------------------------- "Sorry, you have enter the wrong OTP, please enter the OTP again or enter your domain password to generate another OTP" USERNAME: [ ] OTP/PASSWORD: [ ] -------------------------------------------------------------------------- Note: Yes, I know that Windows 2008 and Vista uses a the new CP method, but I'll need to implement GINA for Windows 2003 Servers. I thought I'll implement CP after that, hopefully I can reuse as much of the code as possible. Any suggestions you be much appreciated.
  3. Hi, I'm posed a question in my study course for Active Directory and hope someone can help me. Assuming the following: SMTP Mail Server A Name: mailserver1.domain.com IP Address: 192.168.0.10 SMTP Mail Server B Name: mailserver2.domain.com IP Address: 192.168.0.11 Mail Server A is the primary server, while Mail Server B is the secondary mail server. My users will send emails that find their way to SMTP Mail Server A by using the recipient format: emailusername@mailserver1.domain.com. In the event that SMTP Mail Server A goes down, I want SMTP Mail Server B to replace SMTP Mail Server A. This should be done by a VB or C++ program (written by me) that runs on SMTP Mail Server B. I figure that I can do this by just changing the computer name on Mail Server B from mailserver2.domain.com to mailserver1.domain.com, or should I change IP address instead? Will this pose a problem to AD authentication or registration? What happens if Mail Server A recovers? Will appreciate any pointers.
×
×
  • Create New...