Dlink 614+ SSID problem Help needed

My network works fine with SSID broadcast disabled. The problem I need to
resolve is when I reboot my desktop computer using a Dlink DWL-122 with SSID
disabled I can not get back on the network. I check the logs and the router
Dlink 614+ thinks I'm an intruder (SYN Flood Attack Detect). I've entered
the correct WEP and SSID. If I enable broadcasting the SSID the computer
recognizes the network and I'm fine. Then I have to go in a disable again.
My laptop and kids computer work fine after reboot when SSID is disabled.
What am I doing wrong? Anyone have a simple answer? Thanks in advance.

What method are you using to connect when the SSID broadcast is turned off?
Did you fill out a profile with SSID and other parameters, and click
connect, did you go into the config dialog and enter SSID/etc. and click
connect, or was the SSID displayed in your site list, so you could just
doubleclick it?

The reason I ask is that it sounds like the SSID that is sent in the failure
case is wrong. When you click on a sitelist entry, it's generally guaranteed
that the right SSID, WEP, etc. are used, because these are retrieved from an
associated profile that should be correct because it was created after a
successful connection.

If you retype SSID, etc., there's always an opportunity for something to go
wrong.

A SYN attack normally would refer to a denial-of-service attack in which you
are flooded with SYN packets, each of which attempts to establish a new TCP
connection, tying up memory resources, until you run out of memory and
croak. But I've also seen cases on my DLink router where this diagnostic
shows up when a client adapter is merely trying to associate with the
network, but it's got the wrong SSID, or the wrong WEP key, and no SYN
packets were ever sent.

"Jay Japka" <(E-Mail Removed)> wrote in message
news:%sEWb.23991$(E-Mail Removed). com...
> My network works fine with SSID broadcast disabled. The problem I need to
> resolve is when I reboot my desktop computer using a Dlink DWL-122 with
SSID
> disabled I can not get back on the network. I check the logs and the
router
> Dlink 614+ thinks I'm an intruder (SYN Flood Attack Detect). I've entered
> the correct WEP and SSID. If I enable broadcasting the SSID the computer
> recognizes the network and I'm fine. Then I have to go in a disable
again.
> My laptop and kids computer work fine after reboot when SSID is disabled.
> What am I doing wrong? Anyone have a simple answer? Thanks in advance.
>
>

The SSID was displayed on my list (the only one) and I double click and
still make no connection. I tried the other ways as well without success
till I turned broadcast on again it then reconizes the network and
everything is fine. Then I return to the router turn off broadcasting and
everything works again. Go figure. Thanks


> What method are you using to connect when the SSID broadcast is turned
off?
> Did you fill out a profile with SSID and other parameters, and click
> connect,
Yes I tried that.
did you go into the config dialog and enter SSID/etc. and click
> connect,
Yes I also tried that.
or was the SSID displayed in your site list, so you could just
> doubleclick it?
Yes and this is what I typically would do with my laptop.
>
> The reason I ask is that it sounds like the SSID that is sent in the
failure
> case is wrong. When you click on a sitelist entry, it's generally
guaranteed
> that the right SSID, WEP, etc. are used, because these are retrieved from
an
> associated profile that should be correct because it was created after a
> successful connection.
>
> If you retype SSID, etc., there's always an opportunity for something to
go
> wrong.
>
> A SYN attack normally would refer to a denial-of-service attack in which
you
> are flooded with SYN packets, each of which attempts to establish a new
TCP
> connection, tying up memory resources, until you run out of memory and
> croak. But I've also seen cases on my DLink router where this diagnostic
> shows up when a client adapter is merely trying to associate with the
> network, but it's got the wrong SSID, or the wrong WEP key, and no SYN
> packets were ever sent.
>
> "Jay Japka" <(E-Mail Removed)> wrote in message
> news:%sEWb.23991$(E-Mail Removed). com...
> > My network works fine with SSID broadcast disabled. The problem I need
to
> > resolve is when I reboot my desktop computer using a Dlink DWL-122 with
> SSID
> > disabled I can not get back on the network. I check the logs and the
> router
> > Dlink 614+ thinks I'm an intruder (SYN Flood Attack Detect). I've
entered
> > the correct WEP and SSID. If I enable broadcasting the SSID the
computer
> > recognizes the network and I'm fine. Then I have to go in a disable
> again.
> > My laptop and kids computer work fine after reboot when SSID is
disabled.
> > What am I doing wrong? Anyone have a simple answer? Thanks in advance.
> >
> >
>
>

Jay Japka wrote:
> The SSID was displayed on my list (the only one) and I double click
> and still make no connection. I tried the other ways as well without
> success till I turned broadcast on again it then reconizes the
> network and everything is fine. Then I return to the router turn off
> broadcasting and everything works again. Go figure. Thanks
>
>
>> What method are you using to connect when the SSID broadcast is
>> turned off? Did you fill out a profile with SSID and other
>> parameters, and click connect,
> Yes I tried that.
> did you go into the config dialog and enter SSID/etc. and click
>> connect,
> Yes I also tried that.
> or was the SSID displayed in your site list, so you could just
>> doubleclick it?
> Yes and this is what I typically would do with my laptop.
>>
>> The reason I ask is that it sounds like the SSID that is sent in the
>> failure case is wrong. When you click on a sitelist entry, it's
>> generally guaranteed that the right SSID, WEP, etc. are used,
>> because these are retrieved from an associated profile that should
>> be correct because it was created after a successful connection.
>>
>> If you retype SSID, etc., there's always an opportunity for
>> something to go wrong.
>>
>> A SYN attack normally would refer to a denial-of-service attack in
>> which you are flooded with SYN packets, each of which attempts to
>> establish a new TCP connection, tying up memory resources, until you
>> run out of memory and croak. But I've also seen cases on my DLink
>> router where this diagnostic shows up when a client adapter is
>> merely trying to associate with the network, but it's got the wrong
>> SSID, or the wrong WEP key, and no SYN packets were ever sent.
>>
>> "Jay Japka" <(E-Mail Removed)> wrote in message
>> news:%sEWb.23991$(E-Mail Removed). com...
>>> My network works fine with SSID broadcast disabled. The problem I
>>> need to resolve is when I reboot my desktop computer using a Dlink
>>> DWL-122 with SSID disabled I can not get back on the network. I
>>> check the logs and the router Dlink 614+ thinks I'm an intruder
>>> (SYN Flood Attack Detect). I've entered the correct WEP and SSID.
>>> If I enable broadcasting the SSID the computer recognizes the
>>> network and I'm fine. Then I have to go in a disable again. My
>>> laptop and kids computer work fine after reboot when SSID is
>>> disabled. What am I doing wrong? Anyone have a simple answer?
>>> Thanks in advance.

I have not tried it myself, but another poster said that you can also
refresh the connection in Available Networks to update the SSID state.

Q

Thanks I'll give that a try.


"Quaoar" <(E-Mail Removed)> wrote in message
news:kcqdnefoE-4F-LHdRVn-(E-Mail Removed)...
> Jay Japka wrote:
> > The SSID was displayed on my list (the only one) and I double click
> > and still make no connection. I tried the other ways as well without
> > success till I turned broadcast on again it then reconizes the
> > network and everything is fine. Then I return to the router turn off
> > broadcasting and everything works again. Go figure. Thanks
> >
> >
> >> What method are you using to connect when the SSID broadcast is
> >> turned off? Did you fill out a profile with SSID and other
> >> parameters, and click connect,
> > Yes I tried that.
> > did you go into the config dialog and enter SSID/etc. and click
> >> connect,
> > Yes I also tried that.
> > or was the SSID displayed in your site list, so you could just
> >> doubleclick it?
> > Yes and this is what I typically would do with my laptop.
> >>
> >> The reason I ask is that it sounds like the SSID that is sent in the
> >> failure case is wrong. When you click on a sitelist entry, it's
> >> generally guaranteed that the right SSID, WEP, etc. are used,
> >> because these are retrieved from an associated profile that should
> >> be correct because it was created after a successful connection.
> >>
> >> If you retype SSID, etc., there's always an opportunity for
> >> something to go wrong.
> >>
> >> A SYN attack normally would refer to a denial-of-service attack in
> >> which you are flooded with SYN packets, each of which attempts to
> >> establish a new TCP connection, tying up memory resources, until you
> >> run out of memory and croak. But I've also seen cases on my DLink
> >> router where this diagnostic shows up when a client adapter is
> >> merely trying to associate with the network, but it's got the wrong
> >> SSID, or the wrong WEP key, and no SYN packets were ever sent.
> >>
> >> "Jay Japka" <(E-Mail Removed)> wrote in message
> >> news:%sEWb.23991$(E-Mail Removed). com...
> >>> My network works fine with SSID broadcast disabled. The problem I
> >>> need to resolve is when I reboot my desktop computer using a Dlink
> >>> DWL-122 with SSID disabled I can not get back on the network. I
> >>> check the logs and the router Dlink 614+ thinks I'm an intruder
> >>> (SYN Flood Attack Detect). I've entered the correct WEP and SSID.
> >>> If I enable broadcasting the SSID the computer recognizes the
> >>> network and I'm fine. Then I have to go in a disable again. My
> >>> laptop and kids computer work fine after reboot when SSID is
> >>> disabled. What am I doing wrong? Anyone have a simple answer?
> >>> Thanks in advance.
>
> I have not tried it myself, but another poster said that you can also
> refresh the connection in Available Networks to update the SSID state.
>
> Q
>
>