>>So I have this customer that I installed and configured my software. I installed SQL server and configured it to accept remote connections. I installed a web app on a remote webserver that connects to the database on this server and reads the data in the database. Everything is working great, data is added by my WinForm app localy and data can be viewed by the Web app remotely.
>>
>>The customer decides that he needs a better/faster internet connection and contacts the DSL company. They upgrade his service and installes a new DSL modem. After the new DSL modem is installed the remote Web app can nolonger connect to the SQL Server and read the data. So I tell the customer he has to configure the DSL model to forward incomming remote requests on ports 1433 and 1434 to the correct computer on the local network just like we had to do with the old DSL modem. The interface on the new DSL is slightly different but still it is pretty intuitive. He tries to change the DSL modem settings but it still does not work. I ask him to contact his DSL modem company help line (they were not much help). I connect remotely and try to configure the DSL modem without any luck.
>>
>>Long story short, the only thing that changed was the DSL modem (and service). So it has to be the DSL modem configuration, correct?
>>
>>I am at a loss here. Any help is appreciated. I don't mind helping the customer by connecting to his computer through LogMeIn but I want to avoid having to go to Denver. It has to be something very simple.
>>
>>Thanks,
>>Einar
>
>
>On top off my head:
>Did the customer has the same IP address?

Yes, I forgot to mention that, the public IP address didn't change.

Are there any port scan tools I can use to find out what ports are open?

Einar