Looks right to me. I would guess your issue in testing is the router doesn't support the loop back. Ive had this in the past, though I've not tried on this model router so cant comment on that.
If you like, I'll test a telnet from here . PM me the IP address to use, dont broadcast it here, if you want me to check for you. I wont be logging in, don't need to do that, so you wont be exposing anything to me in case you're worried about that.
Are you specifying the port number in the connection string? If not, because you are using a named instance the client will query the server for the port number the instance is on. It does this through the SQL Browser over port 1434.
That gives you two options:
Open up port 1434 like you have for port 1433 and confirm you have the SQL Browser service running
Modify your connection string to include the port number. This is done by adding ",1433" to the servername less the quotes
Update for everyone else reading this thread: Last night i confirmed with kiwis that he has the port forwarding set up correctly and can telnet into his IP address over port 1433 - so no firewalls or anything blocking connectivity. I believe the issue is now elsewhere (e.g. on the client PC).
You've listed yet another IP address. If you've done that to mask the true IP address on the forums then fair enough, but if this is a new host you have to go through the hassle of verifying the 3 scenarios again earlier in this thread.
Assuming the IP address hasn't changed from the one I tested last night everything you can set up is set up correctly. You need to look into the errorlogs of each machine in question now to determine what is wrong. For example; does the sql error log show a login failure? If it does its probably a case of the wrong password. If you dont see anything then the client isn't getting to sql server so the problem is further up the chain. My suspicion is that the issue is now on your friends PC/connection somewhere (eg his/her firewall) as we were able to verify everything else last night. If their ISP blocks traffic on 1433 you'll have to find a port they do allow (e.g. 80) and map 80 to 1433 in the port forwarding (and of course updating your connection string).
First thing I'd try is getting your friend to telnet to your ip address on port 1433 and see if connects or times out. If it times out something is stopping it. If it connects the problem is elsewhere.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
