Re: Remote connection problems

This is a confusing aspect of the tool. If the TCP/IP Properties, Protocol 
tab has Listen All as Yes, then the individual settings for IP1 and IP2 are 
not necessary. If you want to make do different things, you must first 
change Listen All to No, and then change the IP settings.
And since one of the IP addresses is the loopback adapter 127.0.0.1, which 
isn't visible over the network, you can ignore that. So right now, it sounds 
like you are listening on dynamic ports and it is currently listening on 
port 2414. If you stop and restart SQL Server, it might come up on a 
different port. If that's a problem, remove the 0 from TCP Dynamic Ports, 
and pick a port number you like, and then restart SQL Server.
Sorry this is confusing. SP1 will have some new wording in the help topic to 
try and clarify this. (No, I don't know when SP1 will be released. <g>)
-- 
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.

<frederic.nourry@xxxxxxxxx> wrote in message 
news:1138768634.322274.24780@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thanks Rick
>
> looking at the event viewer I found that the server is listening to
> 2414
>
> change to server,2414 worked fine
>
> i noticed that, that is the port configured under IPAll, dynamic ports
> in server configuration manager
>
> shouldn't i change the port for ip1 and ip2 ?
>
> thanks now i can work
> 


.

Relevant Pages

  • Re: IIS, SQL 2000 & XPs Firewall
    ... Queries to the Data Engine must go to the port that SQL Server is listening ... More info: How to: Configure a Windows Firewall for Database Engine Access ...
    (microsoft.public.sqlserver.connect)
  • Re: Connecting to DB with Static IP over the internet
    ... port and dmz was forward to the incorect internal ip address:) ... and any other ms sql server related ports on the server. ... item on the connection string. ... is listening, I do netstat -a and it does list that it is being listened ...
    (microsoft.public.sqlserver.setup)
  • Re: Server not listening on 1433
    ... sql server may be listening in a different port. ... >>> Server error log. ...
    (microsoft.public.sqlserver.setup)
  • Re: Blocking UDP Port 1434
    ... You can configure SQL Server ... >>> planning to block UDP Port 1434 on all gateways. ... >>> the sql instance is listening on can be re-assigned, ...
    (microsoft.public.sqlserver.server)
  • Re: Best Plan of action for 2 forest.......
    ... PortQry reports the status of a port in one of the following ways: ... ..LISTENING This response indicates that a process is listening on the target ...
    (microsoft.public.windows.server.active_directory)
Loading