Post reply

server stopped listening for connections

  • August 13, 2005 at 1:52 am

    #90586

    i'v set up an sql server 2000 (sp4) instance on a dedicated server. for a long time it has been working normally, accepting connections from both localhost and from across the internet. i am the only administrator. it is running on a windows 2003 standard box.

    now it only accepts connections from localhost (and the websites hosted there), even though in network configuration it says TCP/IP is enabled (and i set it to port 1443).

    when i do a portscan with nmap, it does not show port 1443 as being open.

    when i telnet to that port, it gives me a blank interface for a minute then disconnects (as apposed to saying failed to connect if no service is there).

    i'v also tried changing the port sql server listens on, to see if maybe i had two programs overlapping or something, but that didn't help.

    i'v been up and down the properties tabs but don't see any place that would restrict connections only to localhost.

    any debugging methods or help of any kind would be much appreciated.

  • August 14, 2005 at 2:38 am

    #582059

    Hi

    here is an article about XP firewall setting, but its also good for win2003.

    http://support.microsoft.com/default.aspx?scid=kb;en-us;308127

    try it.

    yoav.

  • August 15, 2005 at 9:33 am

    #582208

    Does netstat -a show the port as open?

  • August 17, 2005 at 5:53 am

    #582727

    i checked to make sure it wasn't windows firewall.

    nestat -a shows that the computer is listening on that port.

    does it matter what port it is?

    **edit

    also, my client computer is running on windows 2003 std, with mdac version 2.8 MTR

  • August 20, 2005 at 12:19 am

    #583739

    i got ethereal (winpcap) to capture network traffic. the last captured packet is repeated 3 times going out on UDP to port ms-sql-m (1434), which i assume is the named instance decider / connection listening port?

    this is the data section of that packet (9 bytes):

    0000 00 40 05 24 19 2f 00 60 94 23 38 78 08 00 45 00 .@.$./.` .#8x..E.

    0010 00 25 21 8a 00 00 80 11 85 8f c0 a8 00 a0 48 24 .%!..... ......H$

    0020 8a 42 0b 6e 05 9a 00 11 73 ee 04 50 43 54 53 51 .B.n.... s..PCTSQ

    0030 4c 31 00 L1.

    my named instance is PCTSQL1... don't know what else to do with that.

    how could i traceroute the path of these packets to see how far they get? maybe my isp or the NOC has a firewall.

    it's probably a UDP timeout or something, maybe the sql server is distracted =/

    got crunk juice?@#*! what the dumb is going on here?

    **edit

    i'v got a freebsd box and windows boxes to use for whatever tools anyone can think of

    and just making sure, for the server field i'd put mydomain.com\PCTSQL1 if my named instance is PCTSQL1?

  • August 20, 2005 at 12:59 am

    #583740

    traffic history:

    ping comes back from the correct ip address, DNS and ping reply success.

    then i send out NBNS (netbios to port 137) packets, then a TCP packet to port microsoft-ds (445). i did a portscan with nmap and both those were found open.

    after that only two packets come back, both from north carolina (??) as SYN (ping?) request and reply. probably not related..

    so this means that after the DNS resolves to the right IP, then it get's no response for a netbios server name?

    maybe my isp is blocking netbios traffic to stop virii? those bastards!@# guess i should call them..

    then those 3 packets mentioned in the earlier post.

  • August 20, 2005 at 8:38 pm

    #583772

    http://support.cox.com/sdccommon/asp/contentredirect.asp?sprt_cid=643ad749-1a58-4824-9d1c-8cd5579e132a

    .... well there you go.... blocked by the isp

    thanks for the help everyone

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply