locked
DirectAccess connections after changing external IP:s on UAG RRS feed

  • General discussion

  • Hi guys,

    I moved a production UAG to new IP:s last night. My testmachine was able to connect to the network after first connecting a PPTP VPN and running gpupdate. But my question is how about the ones on the outside that don't know of or don't have VPN access without contacting a helpdesk. The dns da.company.com is used for HTTPS access so in theory shouldn't the clients access it by IP-HTTPS, connect, update GPO and after that everything sould be fine and dandy. Atleast in theory.

    Looking att eventlog I see a lot of clients loging in on the server byt DA Web Monitoring only shows one session active, the test machine.

    Looking at TMG logs I found a lot of theese,

    Log type: Firewall service 
    Status: An ingoing packet was dropped because its destination address does not exist on the system, and no appropriate forwarding interface exists.  
    Rule: None - see Result Code 
    Source: External (fe80::b87d:2d73:f9cb:c85f:546) 
    Destination: External (ff02::1:2:547) 
    Protocol: Unidentified IP Traffic (UDP:547) 
    

    Does anyone have an idea if this could be related to the issues? I've ran the Network wizard after the change to correct the IP:s, as I said, the one client I have was able to connect after a gpudate via PPTP VPN.


    MCITP Server Administrator
    MCTS Configuration Manager
    MCTS Operations Manager
    Blog: http://www.nixadmins.net
    Saturday, November 12, 2011 7:32 PM

All replies