WRT300N Stopped accepting wireless connections

I have a WRT300N, and last night, my roommates lost wireless connection. Our SSID still shows up in the site survey, with excellent strength, but the router has apparently stopped accepting wireless connections.
We have reset the router twice, reset to factory defaults, upgraded the firmware, reconfigured the wireless setup and they still cannot connect. Even when we turned off security, the connection process just times out.
It seems to me like the router is broadcasting the SSID, but the part that "listens" for incoming connections is broken.
What could be wrong? The router is only about 6 months old.

Hi... it seems to be a weird issue after firmware upgrade it should resolved the problem... anyways logon to router's setup page, try changing radio band to wide 40 Mhz, wide channel to 9, standard channel to 11, go to advanced wireless settings and reduce beacon interval to 50, fragmentation and RTS threshold to 2304 and setup WPA wireless security check whether it works or not and let me know...

Similar Messages

  • Stopped accepting wireless connections

    Over night (sometime between 5:17AM and 8:30 AM CST) my Time Capsule (firmware version 7.3.2, model MB277LL/A) simply stopped allowing wireless connections. The problem was solved by rebooting (power cycling) the TC, but I give a detailed report below in case someone sees something similar or actually understands what the cause of the problem was.
    During the problem, the TC continued to work fine over the wired network. This included, Time Machine backups, logging to my syslog server, and everything else one might expect. It also continued to advertise the SSID wirelessly. But attempts to join the (WPA, shared private key) network failed.
    I first noted the failure with my iPhone, which I worked on rebooting and such, but later saw that every wireless device in the house failed to connect with some sort of timeout. Again, the wireless network was seen, but all connections failed early on. (I think that it was before authentication. The error on the iPhone was "couldn't connect to network ewd" and the error from a Macbook was "... Timeout", but it happened very quickly). Also the syslog logs from the TC didn't report any failed log in attempts (but did continue to report things like time (ntp) adjustments so it was logging properly).
    I checked the configuration using AirPort Utility.app and everything looked fine. Display light was also solid green (I even asked someone in the house with normal color vision to confirm that). Finally, I just gave up and power-cycled the thing, which seems to have resolved the problem.
    Note that it hadn't been off since I installed the UPS that it is on (about four months ago). It was warm, but not excessively.
    One bit of speculation may have been with channel selection. I noticed that the signal this morning was also registered as weaker than typical. Also there appears to be a new wireless hub in the neighborhood (with no password). Finally, before the reboot the TC was using channel 6 while after the reboot it is using channel 9.

    I never meant this to be a question. But I didn't notice the "unmark as a question" button until well after my 15 minutes were up.
    As I said, rebooting the TC fixed the problem. I'm still curious about what happened, but it probably shouldn't be listed as an open question for forum statistics.

  • HELP!  Gateway stops accepting new connections

    Config: PS6.1 on Solaris 9 (Sparc), seperate gateway on Solaris 9 (Sparc) The PS6.1 was migrated from a PS3.0 installation, The machines are V240 with 2GB RAM and 4GB swap.
    I start the GW with: ./S43gateway -n default start debug
    Several minutes after startup (it varies from 1 to 40) I get the following message:
    Class Name: com.sun.portal.rproxy.rewriter.services.idsame.IDSAMEDataServiceStub04/02/2004 07:29:07:823 PM CST: Thread[Thread-14,5,main]
    ERROR: RemoteHandler : ERROR on remote machineAfter a while, something will trigger the following set of messages and that's when the gateway stops accepting new connections.
    ESessionMsg caught exception when reading:
    java.io.EOFException
            at java.io.DataInputStream.readFully(DataInputStream.java:153)
            at com.sun.portal.netlet.econnection.ESessionMsg.readMsg(ESessionMsg.java:24)
            at com.sun.portal.netlet.eproxy.EProxyConnection$ESessionThread.run(EProxyConnection.java:114)
            at com.sun.portal.util.ThreadPoolThread.run(GWThreadPool.java:109)
    java.lang.OutOfMemoryError
            <<no stack trace available>>The OutOfMemoryError will keep coming out for a while, why it stops, I don't know. When this does happen, the java process is only using about 220MB of RAM and only about 10 users are logged-in.
    This was working fine until we changed the IP of the gateway and moved its ethernet connection to "outside" the firewall. I re-installed the gateway software to make sure I didn't miss anything other than platform.conf. I have the webproxy enabled for the bookmarks channel and that is working. I have holes in the firewall for the proxy, LDAP and HTTPS ports.
    Any ideas?
    Thanks,
    Roger S.

    The gateway has to be tuned substantially to get good performance.
    The tuning needs to be based on your load
    e.g how many netlet connections, how many concurrent users you expected to handle etc ..
    the default min heap size and max heap size need to change it. You can go upto a max of 2 Gb but I would recommend starting with a smaller heap size of 500 M and see how your performance goes.
    The min and max heap size should always be the same for better performance. If your using netlets then you have to change the thread parameter. Each netlet connection uses two threads so if your using a large number of netlet connections then your thread count needs to 500 at a minimum to support 200 concurrent netlet sessions. Increasing the thread pool will also use more memory as each thread uses a min of 512 K of memory. The thread stack size needs to be set to 128 K.
    These are the initial things to start with, you can also set jvm option -verbose:gc to enable gc logs. This will show memory usage.
    These are good things to start with ..

  • Cisco 1811W stopped allowing wireless connection of domain laptops

    I have a Cisco 1811W that after several years in service suddenly stopped allowing any wireless connection to laptops on the domain. It allows hard wired connections and devices that are just using the wireless hot spot like iPads and Iphones but not devices on the domain. These same laptops connect wirelessly without issue at our other facilities which use the same hardware.
    Here is the config file...
    Here is the config file of the router in question...
    router#show run
    Building configuration...
    Current configuration : 11776 bytes
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec localtime show-timezone year
    service password-encryption
    hostname xxx
    boot-start-marker
    boot-end-marker
    logging message-counter syslog
    logging buffered 4096
    no logging console
    enable secret 5 xxxx
    aaa new-model
    aaa authentication login default local
    aaa authorization exec default local
    aaa session-id common
    crypto pki trustpoint TP-self-signed-1083484987
    enrollment selfsigned
    subject-name cn=IOS-Self-Signed-Certificate-1083484987
    revocation-check none
    rsakeypair TP-self-signed-xxxx
    dot11 syslog
    dot11 ssid xxxx
    vlan 44
    authentication open
    authentication key-management wpa
    wpa-psk ascii 7
    dot11 ssid xxxx
    vlan 144
    authentication open
    authentication key-management wpa
    guest-mode
    wpa-psk ascii 7
    ip source-route
    no ip dhcp use vrf connected
    ip dhcp excluded-address xxx.xxx.xxx.xxx
    ip dhcp excluded-address xxx.xxx.xxx.xxx
    ip dhcp excluded-address xxx.xxx.xxx.xxx
    ip dhcp pool xxx-LAN
    networkxxx.xxx.xxx.xxx 255.255.255.0
    domain-name xxxx
    dns-server xxx.xxx.xxx.xxx
    default-router xxx.xxx.xxx.xxx
    lease 0 2
    ip dhcp pool VLAN44
    network xxx.xxx.xxx.xxx 255.255.255.0
    default-router xxx.xxx.xxx.xxx
    domain-name xxxx
    dns-server xxx.xxx.xxx.xxx
    lease 4
    ip dhcp pool VLAN144
    network xxx.xxx.xxx.xxx 255.255.255.0
    default-router xxx.xxx.xxx.xxx
    domain-name xxxx
    dns-server 12.127.16.67 12.127.16.68
    lease 4
    ip cef
    ip domain name xxxx
    ip name-server xxx.xxx.xxx.xxx
    ip name-server xxx.xxx.xxx.xxx
    ip inspect tcp reassembly queue length 24
    ip inspect name IPFW tcp timeout 3600
    ip inspect name IPFW udp timeout 15
    ip inspect name IPFW ftp
    ip inspect name IPFW realaudio
    ip inspect name IPFW smtp
    ip inspect name IPFW h323
    ip inspect name IPFW ftps
    ip inspect name IPFW http
    ip inspect name IPFW https
    ip inspect name IPFW icmp
    ip inspect name IPFW imap
    ip inspect name IPFW imaps
    ip inspect name IPFW irc
    ip inspect name IPFW ircs
    ip inspect name IPFW ntp
    ip inspect name IPFW pop3
    ip inspect name IPFW pop3s
    ip inspect name IPFW radius
    ip inspect name IPFW sip
    ip inspect name IPFW sip-tls
    ip inspect name IPFW ssh
    ip inspect name IPFW telnet
    ip inspect name IPFW telnets
    ip inspect name IPFW vdolive
    ip inspect name IPFW webster
    ip inspect name IPFW dns
    no ipv6 cef
    multilink bundle-name authenticated
    password encryption aes
    file prompt quiet
    username admin password n
    username laneadmin password n
    crypto isakmp policy 1
    encr aes
    authentication pre-share
    group 2
    crypto isakmp policy 2
    encr 3des
    authentication pre-share
    group 2
    crypto isakmp key 5122662533fedcbabcdef address 12.97.225.232
    crypto isakmp key 5122662533fedcbabcdef address 12.97.224.120
    crypto isakmp key 5122662533fedcbabcdef address 12.97.225.152
    crypto isakmp key 5122662533fedcbabcdef address 12.97.230.154
    crypto isakmp key 5122662533fedcbabcdef address 12.97.225.226
    crypto ipsec security-association lifetime seconds 28800
    crypto ipsec transform-set ESP-AES256-SHA esp-aes 256 esp-sha-hmac
    crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
    crypto ipsec transform-set ESP-AES256-SHA-LZO esp-aes 256 esp-sha-hmac comp-lzs
    crypto ipsec df-bit clear
    crypto ipsec profile SITE-to-SITE-DMVPN-Profile
    set transform-set ESP-AES256-SHA
    crypto ipsec client ezvpn ezvpn-client
    connect auto
    mode client
    xauth userid mode interactive
    archive
    log config
    logging enable
    notify syslog contenttype plaintext
    hidekeys
    path scp://cisco:wrs-.o#d8Au8M@fs00/$h-$t
    write-memory
    ip ssh version 2
    bridge irb
    interface Loopback0
    ip address 1.1.1.5 255.255.255.252
    interface Tunnel0
    ip address xxx.xxx.xxx.xxx 255.255.255.0
    no ip redirects
    ip nhrp map xxx.xxx.xxx.xxx 12.97.230.154
    ip nhrp map multicast 12.97.230.154
    ip nhrp map xxx.xxx.xxx.xxx 12.97.225.226
    ip nhrp map multicast 12.97.225.226
    ip nhrp network-id 1
    ip nhrp nhs xxx.xxx.xxx.xxx
    ip nhrp nhs xxx.xxx.xxx.xxx
    tunnel source 12.97.225.234
    tunnel mode gre multipoint
    tunnel protection ipsec profile SITE-to-SITE-DMVPN-Profile
    interface Dot11Radio0
    no ip address
    no dot11 extension aironet
    encryption vlan 44 mode ciphers tkip
    encryption vlan 144 mode ciphers tkip
    ssid XXXX
    ssid XXX-guest
    speed basic-1.0 2.0 5.5 6.0 9.0 11.0 12.0 18.0 24.0 36.0 48.0 54.0
    channel 2437
    station-role root
    no cdp enable
    interface Dot11Radio0.44
    encapsulation dot1Q 44
    bridge-group 44
    bridge-group 44 subscriber-loop-control
    bridge-group 44 spanning-disabled
    bridge-group 44 block-unknown-source
    no bridge-group 44 source-learning
    no bridge-group 44 unicast-flooding
    interface Dot11Radio0.144
    encapsulation dot1Q 144
    bridge-group 144
    bridge-group 144 subscriber-loop-control
    bridge-group 144 spanning-disabled
    bridge-group 144 block-unknown-source
    no bridge-group 144 source-learning
    no bridge-group 144 unicast-flooding
    interface Dot11Radio1
    no ip address
    speed basic-6.0 9.0 basic-12.0 18.0 basic-24.0 36.0 48.0 54.0
    station-role root
    interface FastEthernet0
    description 604 AT&T static IP
    ip address 12.97.225.234 255.255.255.248
    ip access-group IPFW-ACL-outside-A in
    no ip redirects
    no ip proxy-arp
    ip nat outside
    ip inspect IPFW out
    ip virtual-reassembly
    duplex auto
    speed auto
    interface FastEthernet1
    no ip address
    shutdown
    duplex auto
    speed auto
    interface FastEthernet2
    switchport access vlan 4
    spanning-tree portfast
    interface FastEthernet3
    description phone system
    switchport access vlan 4
    spanning-tree portfast
    interface FastEthernet4
    switchport access vlan 4
    spanning-tree portfast
    interface FastEthernet5
    switchport access vlan 4
    spanning-tree portfast
    interface FastEthernet6
    switchport access vlan 4
    spanning-tree portfast
    interface FastEthernet7
    switchport access vlan 4
    spanning-tree portfast
    interface FastEthernet8
    switchport access vlan 4
    spanning-tree portfast
    interface FastEthernet9
    description switchport uplink
    switchport access vlan 4
    interface Vlan1
    no ip address
    interface Vlan4
    ip address xxx.xxx.xxx.xxx 255.255.255.0
    no ip redirects
    no ip proxy-arp
    ip nat inside
    ip virtual-reassembly
    ip tcp adjust-mss 1200
    ip policy route-map NONAT-LAN
    interface Vlan5
    no ip address
    interface Vlan10
    no ip address
    interface Vlan44
    description nnn private WLAN
    no ip address
    ip nat inside
    ip virtual-reassembly
    ip policy route-map NONAT-LAN
    bridge-group 44
    bridge-group 44 spanning-disabled
    interface Vlan144
    description nnn Guest WLAN
    no ip address
    ip nat inside
    ip virtual-reassembly
    ip policy route-map NONAT-LAN
    bridge-group 144
    bridge-group 144 spanning-disabled
    interface Async1
    no ip address
    encapsulation slip
    interface BVI44
    description Bridge to nnn private WLAN
    ip address xxx.xxx.xxx.xxx 255.255.255.0
    ip nat inside
    ip virtual-reassembly
    interface BVI144
    description Bridge to nnn Guest WLAN
    ip address xxx.xxx.xxx.xxx 255.255.255.0
    ip nat inside
    ip virtual-reassembly
    router eigrp 1
    network xxx.xxx.xxx.xxx
    network xxx.xxx.xxx.xxx
    no auto-summary
    ip forward-protocol nd
    ip route 0.0.0.0 0.0.0.0 12.97.225.233
    no ip http server
    no ip http secure-server
    ip nat inside source list NAT-ACL interface FastEthernet0 overload
    ip nat inside source static tcp xxx.xxx.xxx.xxx 22 interface FastEthernet0 22222
    ip nat inside source route-map NO-NAT interface FastEthernet0 overload
    ip access-list standard VTY-ACL
    permit 192.168.0.0 0.0.63.255
    ip access-list extended IPFW-ACL-outside
    permit udp any any eq isakmp
    permit udp any eq isakmp any
    permit esp any any
    permit tcp any host 12.97.225.234 eq 23232
    permit icmp any any administratively-prohibited
    permit icmp any any echo-reply
    permit icmp any any packet-too-big
    permit icmp any any time-exceeded
    permit icmp any any traceroute
    deny ip any any
    ip access-list extended IPFW-ACL-outside-A
    permit tcp any host 12.97.225.234 eq 22222
    permit udp any any eq isakmp
    permit udp any eq isakmp any
    permit esp any any
    permit tcp any host 12.97.225.234 eq 23232
    permit icmp any any administratively-prohibited
    permit icmp any any echo-reply
    permit icmp any any packet-too-big
    permit icmp any any time-exceeded
    permit icmp any any traceroute
    deny ip any any
    ip access-list extended NAT-ACL
    deny ip 192.168.4.0 0.0.0.255 192.168.3.0 0.0.0.255
    deny ip 192.168.4.0 0.0.0.255 192.168.5.0 0.0.0.255
    deny ip 192.168.4.0 0.0.0.255 192.168.2.0 0.0.0.255
    deny ip 192.168.4.0 0.0.0.255 192.168.0.0 0.0.0.255
    permit ip 192.168.4.0 0.0.0.255 any
    deny ip 192.168.44.0 0.0.0.255 192.168.1.0 0.0.0.255
    deny ip 192.168.44.0 0.0.0.255 192.168.2.0 0.0.0.255
    deny ip 192.168.44.0 0.0.0.255 192.168.3.0 0.0.0.255
    deny ip 192.168.44.0 0.0.0.255 192.168.0.0 0.0.0.255
    deny ip 192.168.44.0 0.0.0.255 192.168.5.0 0.0.0.255
    permit ip 192.168.44.0 0.0.0.255 any
    deny ip 192.168.144.0 0.0.0.255 192.168.1.0 0.0.0.255
    deny ip 192.168.144.0 0.0.0.255 192.168.2.0 0.0.0.255
    deny ip 192.168.144.0 0.0.0.255 192.168.3.0 0.0.0.255
    deny ip 192.168.144.0 0.0.0.255 192.168.0.0 0.0.0.255
    deny ip 192.168.144.0 0.0.0.255 192.168.5.0 0.0.0.255
    permit ip 192.168.144.0 0.0.0.255 any
    ip access-list extended NONAT-LAN-RETURNING-ACL
    permit ip 192.168.4.0 0.0.0.255 192.168.3.0 0.0.0.255
    permit ip 192.168.4.0 0.0.0.255 192.168.5.0 0.0.0.255
    permit ip 192.168.4.0 0.0.0.255 192.168.2.0 0.0.0.255
    permit ip 192.168.4.0 0.0.0.255 192.168.0.0 0.0.0.255
    permit ip 192.168.44.0 0.0.0.255 192.168.3.0 0.0.0.255
    permit ip 192.168.44.0 0.0.0.255 192.168.5.0 0.0.0.255
    permit ip 192.168.44.0 0.0.0.255 192.168.2.0 0.0.0.255
    permit ip 192.168.44.0 0.0.0.255 192.168.0.0 0.0.0.255
    permit ip 192.168.144.0 0.0.0.255 192.168.3.0 0.0.0.255
    permit ip 192.168.144.0 0.0.0.255 192.168.5.0 0.0.0.255
    permit ip 192.168.144.0 0.0.0.255 192.168.2.0 0.0.0.255
    permit ip 192.168.144.0 0.0.0.255 192.168.0.0 0.0.0.255
    ip access-list extended VTY-ACL-A
    deny ip 192.168.160.0 0.0.0.255 any
    permit ip 192.168.44.0 0.0.0.255 any
    permit ip 192.168.144.0 0.0.0.255 any
    permit ip 192.168.0.0 0.0.0.255 any
    permit ip 192.168.1.0 0.0.0.255 any
    permit ip 192.168.2.0 0.0.0.255 any
    permit ip 192.168.3.0 0.0.0.255 any
    permit ip 192.168.4.0 0.0.0.255 any
    permit ip 192.168.5.0 0.0.0.255 any
    permit tcp any any eq 22
    deny ip any any
    logging trap notifications
    logging source-interface Vlan5
    logging 192.168.0.225
    route-map NONAT-LAN permit 10
    match ip address NONAT-LAN-RETURNING-ACL
    set interface Loopback0
    route-map NO-NAT permit 10
    match ip address NAT-ACL
    snmp-server community XXXsnmppub RO
    control-plane
    bridge 44 route ip
    bridge 144 route ip
    banner login ^C
    Unauthorized access is prohibited and will be monitored and prosecuted.
    If you are not explicitly authorized to access this device, you must
    disconnect now.
    ^C
    banner motd ^C
    Unauthorized access is prohibited and will be monitored and prosecuted.
    If you are not explicitly authorized to access this device, you must
    disconnect now.
    ^C
    line con 0
    line 1
    modem InOut
    stopbits 1
    speed 115200
    flowcontrol hardware
    line aux 0
    line vty 0 4
    access-class VTY-ACL-A in
    password 7 nnn
    transport input ssh
    line vty 5 15
    webvpn gateway webgateway
    ssl trustpoint TP-self-signed-1083484987
    no inservice
    webvpn gateway sslvpn.xxx
    hostname www.nnn
    ssl trustpoint TP-self-signed-1083484987
    inservice
    end
    router#

    It was a two fold problem.  There is another stronger Wi-Fi signal that exists at the facility from another entity on a different domain that the two laptops were trying to associate to in lieu of the network signal from our 1811.  This could only be seen while watching the Intel wireless Proset app NOT the Windows wireless management app.  Then by deleting all other old Wi-Fi networks listed in the Intel Proset app except ours it connected.  Also set devices to never connect to the other signal.  This was not an issue when I brought the laptop to another faciIity without a competing Wi-Fi signal becuase they would connect using the strongest and ONLY Wi-Fi network signal which was ours.

  • WAP4410N stops accepting wireless clients

    I have two WAP4410N. One of he accesspoints is connected to our wired LAN, called by now AP1. The other accesspoint is connected to the first accesspoint by WDS (Client mode) called now by AP2. I have upgraded both accesspoints to firmware 2.0.4.2. Both accesspoints are set to the same SSID and channel (6) and are set to mixed mode (B/G/N). After I two weeks they started to fail. When I connect to AP1 I don't reveive an IP-address of our DHCP server from our LAN. I'm able to connect to AP1 from our LAN. When I SSH to the box and I do an dmesg command, I see the following messages:
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    I'm still testing these devices and I hope I can use these devices in our production environment,which is not possible with these errors and outages.
    I can't connect to AP2 right now. I think the whole wireless interface isn't working anymore, unless I power off/power on the box. But it's hard testing when it works ok for two weeks and then stops.
    Message was edited by: Sander Cornelissen

    After your advice I did a factory reset of both AP's. From 17 october until today it worked fine. Today it crashed and the connection to the device isn't usable.
    In the dmesg, from the SSH console to the AP, I did notice the following text:
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    Going to erase from sector 00000085 to 00000086..
    erasing bf7e0000...
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
    I have to power off and power on again to make the device work.

  • WRT54Gv2 - Router suddenly won't accept wireless connections

    When using my internet this morning it suddenly stopped working on wireless. The internet still works through ethernet.
    I have downloaded the firmware but I cannot install it as I cannot connect to the admin page for the router.
    Following is the results from ipconfig. I have tried accessing the page on both 192.168.1.1 and 86.21.24.1 and neither works.
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : SiS 900 PCI Fast Ethernet Adapter
    Physical Address. . . . . . . . . : xx-xx-xx-xx-xx
    Dhcp Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IP Address. . . . . . . . . . . . : 86.21.25.231
    Subnet Mask . . . . . . . . . . . : 255.255.252.0
    Default Gateway . . . . . . . . . : 86.21.24.1
    DHCP Server . . . . . . . . . . . : 62.252.0.21
    DNS Servers . . . . . . . . . . . : 194.168.4.100
    194.168.8.100
    NetBIOS over Tcpip. . . . . . . . : Disabled
    Lease Obtained. . . . . . . . . . : 07 September 2007 13:37:55
    Lease Expires . . . . . . . . . . : 14 September 2007 12:43:17
    Ethernet adapter Wireless Network Connection:
    Media State . . . . . . . . . . . : Media disconnected
    Description . . . . . . . . . . . : Wireless-G Notebook Adapter
    Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
    I have tried resetting the router but it does not seem to return to the factory settings. Not entirely sure what to do.
    Thanks in advance for any help.

    Thanks for the suggestion!
    Done that and now it does this:
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : tom
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . . . . : Yes
    WINS Proxy Enabled. . . . . . . . : No
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : SiS 900 PCI Fast Ethernet Adapter
    Physical Address. . . . . . . . . : 00-40-D0-47-4C-E8
    Dhcp Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Autoconfiguration IP Address. . . : 169.254.150.107
    Subnet Mask . . . . . . . . . . . : 255.255.0.0
    Default Gateway . . . . . . . . . :
    Ethernet adapter Wireless Network Connection:
    Media State . . . . . . . . . . . : Media disconnected
    Description . . . . . . . . . . . : Wireless-G Notebook Adapter
    Physical Address. . . . . . . . . : 00-0C-41-C7-62-70
    Still can't access the web-based setup page on any ip.
    Thanks again for any help.

  • SQL Server Express 2008 no longer accepting remote connections

    Last night our SQL Server Express 2008 (running on Windows 2003 server) stopped accepting remote connections. 
    1. We restarted the SQL Server -- no resolution.
    2. We rebooted the host Windows 2003 server - no resolution.
    3. telnet localhost 1433: says Could not open connection to the host on port 1433... connection failed.
    4. netstat -an indicates that the server is not listening on port 1433
    5. SQL Server Network Configuration -> Protocols for SQLEXPRESS2008A -> (properties) -> TCP-IP (enabled), Listen All (yes)
    6. SQL Native Client 10.0 Configuration -> Client Protocols -> (properties) TCP-IP (enabled), Default port (1433)
    Fragment from the server error log:
    2014-03-26 08:50:41.09 Server      A self-generated certificate was successfully loaded for encryption.
    2014-03-26 08:50:41.11 Server      Server is listening on [ 'any' <ipv4> 1026].
    2014-03-26 08:50:41.11 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS2008A ].
    2014-03-26 08:50:41.11 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS2008A\sql\query ].
    2014-03-26 08:50:41.11 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the
    trace flag 7806. This is an informational message only. No user action is required.
    2014-03-26 08:50:41.11 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
    to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2014-03-26 08:50:41.11 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014-03-26 08:50:41.29 spid10s     Clearing tempdb database.
    2014-03-26 08:50:41.89 spid10s     Starting up database 'tempdb'.
    2014-03-26 08:50:42.09 spid13s     The Service Broker protocol transport is disabled or not configured.
    2014-03-26 08:50:42.09 spid13s     The Database Mirroring protocol transport is disabled or not configured.
    2014-03-26 08:50:42.14 spid13s     Service Broker manager has started.
    2014-03-26 08:50:42.14 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2014-03-26 08:50:53.48 spid51      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    2014-03-26 08:50:53.48 spid51      Using 'xpstar.dll' version '2007.100.1600' to execute extended stored procedure 'xp_enumerrorlogs'. This is an informational message only; no user action is required.
    2014-03-26 08:51:35.68 spid54      Starting up database 'Web TimeSheet2'.
    2014-03-26 08:51:38.47 spid54      Recovery is writing a checkpoint in database 'Web TimeSheet2' (6). This is an informational message only. No user action is required.
    Note: the lines referring to xpstar.dll is new after this porblem.  Previous logs do not have this,Any help will be appreciated.

    Hi,
    >>Server is listening on [ 'any' <ipv4> 1026].
    Your sql server is not listening on default port 1433 but on 1026.When you connect to instance like hostname\instancename you should specify post no also.
    like hostname\instancename ,1026
    Can you try this.Makes sure TCP/IP and named pipes protocol is enabled
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Wireless connection between D-Link WiFi router and Time capsule stopped working

    We have an ISP provided D-Link wireless router (DIR-615) to which we wirelessly connected our 2Tb Time Capsule for back up and to connect a USB printer to out network. This worked perfectly for 3 1/2 years, until about a month ago, when the time capsule suddenly decided to go "off line". ie we could no longer access it or the printer via our wireless network. We had changed nothing - just one day it stopped working.
    We tried to get it back online with no success. As the 2Tb Time Capsule was almost 7 years old and had had some HDD issues in the passed, we figured it had got old and died and that it was time to replace it; so we bought a new 3Tb Time Capsule, thinking this would get everything back to normal.
    However much as we tried, we were also unable to get the new 3Tb Time Capsule to connect wirelessly to the D-Link wireless router. The Airport Utility did not show the D-Link wireless router or its wireless network, although we were (and are) able to see it in Systems Preferences>Networks from all our multiple devises. This in itself seemed odd. No matter what we tried, the Airport Utility would not find the D-Link wireless router and hence we could not add the 3Tb Time Capsule to the existing wireless network.
    At the end of the day we got fed up with trying to add the 3Tb Time Capsule to the D-Link wireless network, and connected it via a LAN cable to the D-Link router instead. We then set it up as its own network. Worked gerat. Having done that we thought maybe the old 2Tb Time Capsule might not have been the problem after all, so we tried extending our new 3Tb Time Capsule wireless network using the 2Tb Time Capsule wirelessly. This worked perfectly! And we are now almost back to what we wanted.
    So although we have a work around, this means now have 2 separate wireless networks as opposed to the original single wireless network where everything talked to everything else.
    Can anyone shed any light on any of the following:-
    1. Why the original wireless network connection between the D-Link router and the 2Tb Time Capsule just stopped working? Was there some software change from Apple that "decided" D-Link wireless routers were no longer secure; and therefore the TCs could no longer connect to them?
    2. Why it was not possible to extend the existing D-Link wireless network using the the new 3Tb Time Capsule?
    3. Is there is anyway that we can get back to a single wireless network based around the D-Link wireless router as the primary router connecting to the modem, where the 2 Time Capsules connect as "wireless satellite base stations"?

    1. Why the original wireless network connection between the D-Link router and the 2Tb Time Capsule just stopped working? Was there some software change from Apple that "decided" D-Link wireless routers were no longer secure; and therefore the TCs could no longer connect to them?
    A firmware update to the TC came along and you agreed to it without perhaps even noticing.. it then smashed your setup because Apple do not recommend the setup you were using and it is very poor.
    2. Why it was not possible to extend the existing D-Link wireless network using the the new 3Tb Time Capsule?
    Because it is such a poor setup that Apple have taken away your ability to choose it unless you know exactly what you are doing.
    3. Is there is anyway that we can get back to a single wireless network based around the D-Link wireless router as the primary router connecting to the modem, where the 2 Time Capsules connect as "wireless satellite base stations"?
    Yes, this I can help you with.
    I have several ways around the problem.. but the first one is.. why use the DIR-615 at all.. it is not a modem.. it is a very ordinary bottom end, poor single band slow wireless router.
    Why don't you simply remove the DIR-615 from the network completely.. plug whatever it is the ISP supplies you.. an ethernet connection from whatever that modem is you mentioned into the WAN port of the Time Capsule. And use the TC in some router mode.. same as the DIR-615 was setup.. dhcp or pppoe or whatever.. I doubt the TC cannot match it.
    If you have issues please post a few screenshots from the DIR-615 to show how it is setup from the WAN side.. and as long as you are given the username and password or whatever the ISP uses to authenticate then chuck out the DIR-615.
    Tell me if that is a goer.. if not we can work out a few other methods..
    eg. Simply turn off the wireless in the DIR-615. It is poor cf the TC and there is no need for it.. with the TC in bridge only use the TC for wireless as well as wireless extend with your old TC.
    Or setup roaming network where everything uses the same SSID.
    Then you will have one wireless network. And it won't matter what as long as it connects.. although IMHO this is not right as the TC is such a superior router now you are wasting your new TC.

  • FMS 3.0 stops accepting connections after 1-3 days, restart required

    Hi,
    We have a custom application that is running on FMS. Server is dedicated  just for fms, there is only one application running on the server, with  more instances, average traffic is 3-15 simultaneous users. The problem  is, server suddenly stops accepting connections (after 1-3 days from  restart), from this point it is impossible to connect to any instance,  and fms server must be restarted. When the server crashes, the admin  console can see all open instances, can close instances, can restart  fms. There is nothing logged, that would explain this sudden failure.
    Second problem is, cores are connected and disconnected too often,  causing client to reconnect (takes 2-5 seconds).
    Do you have any idea what is causing these problems?
    Hardware: 4 x quadcore Intel(R) Xeon(R) CPU E7440 @ 2.40GHz, 32 GB ram
    OS: CentOS release 5.3 (Final), kernel: 2.6.18-128.4.1.el5
    cpu and mem usage: 1-5% max
    FMS:
    version: Adobe Flash Media Server 3.0.1 r123
    license: valid, unlimited
    configuration: default, changed in Application.xml:
        <AutoCloseIdleClients enable="true">
    - just communication throught objects, strings, int, shared objects
    - no streaming used
    - Mbits in/out: 50/350 (48 hours from restart)
    - Msgs in/out/drop: 4.000.000/21.000.000/0 (48 hours from restart)
    - no problems with connection, no lags
    LOGS:
    admin.log
    #Fields: date    time    x-pid    x-status    x-ctx    x-comment
    2009-10-07    00:03:30    4816    (i)2581242    Core (8684) disconnected :  _defaultRoot_:_defaultVHost_:::_1.    -
    2009-10-07    00:03:31    4816    (i)2581241    Connection to admin received.    -
    2009-10-07    00:03:31    4816    (i)2581243    Connection from core 10772 received.    -
    2009-10-07    00:03:31    4816    (i)2581244    Connection from core 10772 accepted.    -
    ... repeating (10 minutes - 1 hour period)
    master.log
    #Fields: date    time    x-pid    x-status    x-ctx    x-comment
    2009-10-07    00:03:31    24962    (i)2581223    Core (8684) is no longer active.    -
    2009-10-07    00:03:31    24962    (w)2581256    Core (8684)  _defaultRoot_:_defaultVHost_:::_1 experienced 1 failure[s]!    -
    2009-10-07    00:03:31    24962    (i)2581221    Core (10772) started, arguments :  -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1"  -conf "./conf/Server.xml" -name "_defaultRoot_:_defaultVHost_:::_1".    -
    ... repeating (10 minutes - 1 hour period)
    edge.log
    #Fields: date    time    x-pid    x-status    x-ctx    x-comment
    2009-10-07    00:03:08    24982    (w)2641213    Connection rejected by server.  Reason : [ Server.Reject ] : (_defaultRoot_, _defaultVHost_) :  Application (doodletoostats) is not defined.    -
    2009-10-07    00:03:30    24982    (i)2581250    Edge disconnected from core (8684).    -
    2009-10-07    00:03:31    24982    (i)2581252    Registering core (10772).    -
    ... repeating (1 - 3 hours period)
    core.log
    #Fields: date    time    x-pid    x-status    x-ctx    x-comment
    2009-10-07    00:03:31    10772    (i)2581237    Starting admin app on core (10772).    -
    2009-10-07    00:03:31    10772    (i)2581238    Core (10772) connecting to admin.    -
    2009-10-07    00:03:31    10772    (i)2581231    Core (10772) connected to admin.    -
    2009-10-07    00:03:31    10772    (i)2581234    Core (10772) connection to admin  accepted.    -
    2009-10-07    00:03:31    10772    (i)2581246    Core (10772) sending register cmd  to edge.    -
    2009-10-07    00:54:22    11329    (i)2581247    Core (11329) disconnected from edge.    -
    2009-10-07    00:54:22    11329    (i)2581233    Core (11329) disconnecting from  admin.    -
    ... repeating

    We have seen similar issues and the best work around is to have your clients connect on alternate cores/servers. The way to accomplish this really depends on your type of application.

  • Safari is not connecting to internet on my iPad.  Says "could not open the page becuase the server stopped responding."  Everything else that updates over wireless connection is working fine.  Get same response on any site I try to visit.  Need Help!

    Safari is not connecting to internet on my iPad.  Says "could not open the page becuase the server stopped responding."  Everything else that updates over wireless connection is working fine.  Get same response on any site I try to visit.  Need Help!

    I am having identical problem on my iPhone 4 running iOS6.  Did NOT experience this issue prior to upgrade.

  • Wrt300n wireless connection

    I have a new wrt300n
    I set up wireless connection with psk-personal security mode.
    During a session of 2 hours i had 4 times a connection loss on my laptop with windows xp. When i rescanned for wireless networks my wireless network was still visible and I could log-in again.
    Signal strength is maximum.
    What can be the cause of this?
    wired the connetion never drops.
    http://squee.nl

    http://forums.linksys.com/linksys/board/message?board.id=Wireless_Routers&message.id=32631
    If you're using WPA Personal with TKIP, change it to AES. There's a bug in the firmware. This is a workaround.

  • WRT300N V1.1 - Firmw v1.51.2 - Problems to get wireless connection after long idle time

    Hello,
    I have a WRT300N, v1.1 with latest firmware available (v1.51.2).
    I've been experiencing a strange problem:
    1. After long idle time (router is on, no devices are using it wirelessly), no device can get a wireless connection;
    2. I have tried using different OSes (Windows XP SP2, Windows Vista, and Symbian OS);
    3. Wireline connection to a FE port works (if I plug a device using the cable, I can get an IP address and navigate to the internet).
    4. If power reset it (WRT300N), I can get wireless connections working again.
    Is this a known issue?
    Thanks, Gustavo

    Well as you are able to go online from your Hardwired Computer, then i think you need to make some changes on the Wireless Part of your Router. Follow this settings on your Router, i think this might solve the problem.
    Open an Internet Explorer browser page on your wired computer(desktop).In the address bar type - 192.168.1.1 and press Enter...Leave Username blank & in Password use admin in lower case...
    For Wireless Settings, please do the following : -
    Click on the Wireless tab
    - Here select manual configuration...Wireless Network mode should be mixed...
    - Provide a unique name in the Wireless Network Name (SSID) box in order to differentiate your network from your neighbours network...
    - Set the Radio Band to Wide-40MHz and change the Wide channel to 9 and Standard Channel to 11-2.462GHz...Wireless SSID broadcast should be Enabled and then click on save settings...
    Please make a note of Wireless Network Name (SSID) as this is the Network Identifier...
    For Wireless Security : -
    Click on the Sub tab under Wireless > Wireless Security...
    Change the Wireless security mode to WPA, For Encryption, select AES...For Passphrase input your desired WPA Key. For example , MySecretKey , This will serve as your network key whenever you connect to your wireless network. Do NOT give this key to anyone.
    NOTE : Passphrase should be more that 8 characters...
    Click on Advanced Wireless Settings
    Change the Beacon Interval to 50 >>Change the Fragmentation Threshold to 2304 Change the RTS Threshold to 2307 >>Click on "Save Settings"...
    Now see if you can locate your Wireless Network and attempt to connect...

  • WRT300N - wireless connections -- intermittent problems

    I just purchased a WRT300N router and have my desktop PC wired into one of the ports but then are running three separate laptops via wireless.  Both my IBM laptop and my Dell laptop continue to run into problems keeping the internet connection as the wireless connection is dropped periodically throughout the day (every 20-30 minutes).  Any suggestions?  

    Hi!try changing the radio band of your router to wide...wide channel to7 and standard channel to 9.Also on the advance wireless settings of the router change DTIM to 3..beacon interval to 50 and rts threshold 2305..fragmentation threshold:2304...hopefully that will solve ur problem..ciao!

  • Make server stop accepting connections for some condition

    I have a server accepting connections from clients. We don't know in advance how many clients to accept so the server just keeps accepting connections in an infinite loop:
    for( int i = 0; ; ++i)
      server.accept();What needs to happen is some condition has occurred and the server should stop accepting connections. i.e.
    for( int i = 0; stop_accepting_connections == false; ++i)
      server.accept();
    System.out.println( "No longer accepting connection.");Essentially some external event (actually the first accepted client thread) will set stop_accepting_connections to true and break the loop.
    Problem is even when I break out of the loop clients are still accepted. I'm thinking this is caused by server.accept() being a blocking call and even though we've jumped out of the loop the last server.accept() call is still blocking and listening for a single client. I've tried 2 clients connecting when we've broken out of the loop and only the 1st one is accepted, the second just waits.
    1. Is there any way to really stop listening when the condition is set (i.e. how to kill the last blocking accept())? I don't want 1 last trailing client.
    2. For the rejected clients, how do I stop it from just waiting i.e. print some error msg and let it end?

    Problem is even when I break out of the loop clients are still accepted. I'm thinking this is caused by server.accept() being a blocking call and even though we've jumped out of the loop the last server.accept() call is still blocking and listening for a single client.No, it's caused by the TCP 'backlog' queue, which pre-accepts connections even before you call accept().
    1. Is there any way to really stop listening when the condition is set (i.e. how to kill the last blocking accept())?Close the ServerSocket. The thread blocked in accept() will get a SocketException: socket closed, which you should trap and proceed acordingly on. At this point you probably just want to exit the accept() thread.
    2. For the rejected clients, how do I stop it from just waiting i.e. print some error msg and let it end?See above. Any clients which are in the backlog queue will get some kind of SocketException or IOException, probably 'connection reset'.

  • Wireless connection stops and starts using Mountain Lion

    Since installing ML a few days ago, my wireless connection isn't stable for about the first five minutes after waking from sleep mode ... the process is:
    - wake from sleep mode
    - wait about 10 seconds for icon to reflect wireless signal
    - click on a website to open
    - wireless signal starts searching and finds nothing
    - click on network diagnostics
    - signal returns
    - try to open website again
    - same problem occurs
    This seems to last a few minutes but once the connection finally takes, I'm able to access the website and others ...
    This is occurring with a brand new (mid 2012) MacBook Pro 13"

    Yup, same here. I see this in multiple locations, so its not the router.

Maybe you are looking for