Question : Cannot RDP to server after DSL modem was replaced

A client was not happy with the DSL speed and had ATT replace the DSL modem with an upgraded version. They have a WIndows Server 2008 Standard (x86) and a Linksys BEFSR81 router. I have been able to connect to their server via RDP by connecting to their public IP address (port 3389 is redirected to the server IP). I realize this is not the optimal setup, but that is another story...
So, after ATT installed the new modem, I was no longer able to RDP to the server from outside the network. Remote Access works fine within the network.
Nothing on the router has changed. The Gateway and Public IP addresses are the same as they were with the old router. When they run WhatIsMyIP.com, it returns the IP address that I use to RDP to the network (as it did before).
I am not sure if it is an ATT issue, a router issue or a server issue. An frankly, I am not sure what steps to follow in order to troubleshoot this. ATT is giving the client the run around, saying that the client has to connect to the modem and configure it to open port 3389, but I have not heard of that before. I have always had the provider configure the modoem from their site.

ANy thoughts or ideas would be greatly appreciated.

Answer : Cannot RDP to server after DSL modem was replaced

I am SERIOUSLY PISSED!!! I posted a long answer and somehow it didn't submit... GRRR GRRRR GRRRR Stupid Stupid ISPs n STUPID page Implementations.... no way to recover what you have written.. GRRR GRRRR

Now coming to the answer.

Hi apollo7,

Quality of my answer will drop a little now[maybe or maybe not... you know you can never be as good as the first time :(]

Reference link : http://crm.georged.id.au/post/2008/02/16/Filtering-lookup-data-in-CRM-4.aspx

Steps :

1. Take Backup of :

- C:\Program Files\Microsoft Dynamics CRM\CRMWeb\Products\ProductPriceLevel\edit.aspx
- C:\Program Files\Microsoft Dynamics CRM\CRMWeb\_controls\lookup\lookupsingle.aspx

2. In C:\Program Files\Microsoft Dynamics CRM\CRMWeb\Products\ProductPriceLevel\edit.aspx

add first code snippet as shown in the beginning of the function window.onload

3. In C:\Program Files\Microsoft Dynamics CRM\CRMWeb\_controls\lookup\lookupsingle.aspx

add second code snippet at the end of the file

This one will take some time 'cause we might have to tune it further. But this approach should get us the desired results.

And just so you know this one is a totally unsupported one.

Regards,
Chinmay

                       
         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:

           
           
             C:\Program Files\Microsoft Dynamics CRM\CRMWeb\Products\ProductPriceLevel\edit.aspx
function window.onload()
{
//---------------Price List Hack -------------------
var field = crmForm.all.pricelevelid; 
{ 
    // Ensure that search box is not visible in a lookup dialog
    field.lookupbrowse = 1; 
    
    // Pass fetch xml through search value parameter 
    field.AddParam("search", 
     "<fetch mapping='logical'><entity name='businessunit'>" 
    + "<filter><condition attribute='businessunitid' operator='eq' value='" 
    + crmForm.all.<<the field that holds businessunitid>>
    + "' /></filter></entity></fetch>"); 
}

//---------------Price List Hack -------------------

 C:\Program Files\Microsoft Dynamics CRM\CRMWeb\_controls\lookup\lookupsingle.aspx

<script runat="server"> 

protected override void OnLoad( EventArgs e ) 
{ 
      base.OnLoad(e); 
      crmGrid.PreRender += new EventHandler( crmgrid_PreRender ); 
} 

void crmgrid_PreRender( object sender , EventArgs e ) 
{
    // As we don't want to break any other lookups, ensure that we use workaround only if
    // search parameter set to fetch xml.
    if (crmGrid.Parameters["search"] != null && crmGrid.Parameters["search"].StartsWith("<fetch")) 
    { 
        crmGrid.Parameters.Add("fetchxml", crmGrid.Parameters["search"]);  

        // searchvalue needs to be removed as it's typically set to a wildcard '*' 
        crmGrid.Parameters.Remove("searchvalue");  

        // Icing on a cake - ensure that user cannot create new contact outside of the account
        // and then select it.
        this._showNewButton = false; 
    } 
} 

</script>

           
         