Changing Network SSID Blocks Incoming Mails To My Inbox?

I set up a home wifi network using a D-link boradband router and lavet the
SSID as default. Everything runs smoothly, no problem with incoming and
outgoing mails.

On 26the Dec I changed my network SSID to a specific name. Now, while i can
still send outgoing mails, my incoming mails from 26 Dec onwards are all
stranded in the mail server and could not come into my inbox. I am using
Outlook Express ver. 6. I realised this when someone told me to check my
pop3.log file and sure enough all incoming mails are stuck in the server and
cannot come in. However i can still receive incomg mails sent from within
the network.

Is it because the SSID has been changed and some related settings need to be
changed at the same time? Or is it the mail quota on the server is full? Can
someone help? TIA

On Sat, 1 Jan 2005 06:40:33 +0800, <(E-Mail Removed)> wrote:

>I set up a home wifi network using a D-link boradband router and lavet the
>SSID as default. Everything runs smoothly, no problem with incoming and
>outgoing mails.
>
>On 26the Dec I changed my network SSID to a specific name. Now, while i can
>still send outgoing mails, my incoming mails from 26 Dec onwards are all
>stranded in the mail server and could not come into my inbox. I am using
>Outlook Express ver. 6. I realised this when someone told me to check my
>pop3.log file and sure enough all incoming mails are stuck in the server and
>cannot come in. However i can still receive incomg mails sent from within
>the network.
>
>Is it because the SSID has been changed and some related settings need to be
>changed at the same time? Or is it the mail quota on the server is full? Can
>someone help? TIA
>
>
I could be wrong, but the SSID is simply the name of your wireless
network. (service set ID) I've changed my SSID several times over
the years and have yet to experience a mishap because of the change.
Therefore, your changing of the SSID should not interfere with
anything. To be on the safe side, when you changed the SSID in your
route/AP settings, did you enter the new SSID into the card's
configuration menu?

Doug Jamal wrote:
> On Sat, 1 Jan 2005 06:40:33 +0800, <(E-Mail Removed)> wrote:
>
>> I set up a home wifi network using a D-link boradband router and
>> lavet the SSID as default. Everything runs smoothly, no problem with
>> incoming and outgoing mails.
>>
>> On 26the Dec I changed my network SSID to a specific name. Now,
>> while i can still send outgoing mails, my incoming mails from 26 Dec
>> onwards are all stranded in the mail server and could not come into
>> my inbox. I am using Outlook Express ver. 6. I realised this when
>> someone told me to check my pop3.log file and sure enough all
>> incoming mails are stuck in the server and cannot come in. However i
>> can still receive incomg mails sent from within the network.
>>
>> Is it because the SSID has been changed and some related settings
>> need to be changed at the same time? Or is it the mail quota on the
>> server is full? Can someone help? TIA
>>
>>
> I could be wrong, but the SSID is simply the name of your wireless
> network. (service set ID) I've changed my SSID several times over
> the years and have yet to experience a mishap because of the change.
> Therefore, your changing of the SSID should not interfere with
> anything. To be on the safe side, when you changed the SSID in your
> route/AP settings, did you enter the new SSID into the card's
> configuration menu?

That's the typical symptom of changing the wap's ssid but not rebooting the
machines on your network

On Sat, 1 Jan 2005 19:39:53 -0800, Peter Pan spoketh

>
>That's the typical symptom of changing the wap's ssid but not rebooting the
>machines on your network
>

You do NOT have to reboot your (Windows) computer when changing the SSID
on your wireless network connection.

Lars M. Hansen
www.hansenonline.net
Remove "bad" from my e-mail address to contact me.
"If you try to fail, and succeed, which have you done?"

Lars M. Hansen wrote:
> On Sat, 1 Jan 2005 19:39:53 -0800, Peter Pan spoketh
>
>>
>> That's the typical symptom of changing the wap's ssid but not
>> rebooting the machines on your network
>>
>
> You do NOT have to reboot your (Windows) computer when changing the
> SSID on your wireless network connection.
>
> Lars M. Hansen
> www.hansenonline.net
> Remove "bad" from my e-mail address to contact me.
> "If you try to fail, and succeed, which have you done?"

No you don't. But if you want to access it after changing that (or the
workgroup names), it a whole lot easier to just reboot rather than connect
to a new network. I always wonder why people are so deathly afraid to power
off or re-boot... It works absolutely no matter what, and it fixes probably
90-95% of the errors..

On Sun, 2 Jan 2005 12:19:07 -0800, Peter Pan spoketh

>
>No you don't. But if you want to access it after changing that (or the
>workgroup names), it a whole lot easier to just reboot rather than connect
>to a new network. I always wonder why people are so deathly afraid to power
>off or re-boot... It works absolutely no matter what, and it fixes probably
>90-95% of the errors..
>

There's absolutely no relationship or even similarities between changing
the SSID and changing the workgroup name. Changing the SSID is simply a
minor change in what name the wireless client uses when connecting to a
network. Changing the workgroup name is a major change in what name the
operating system uses when participating in a network.

There is absolutely no need to reboot your computer after changing the
SSID. There are no benefits to doing so, and there's little point in
suggesting that it in any way, shape or form would help or even rectify
the OPs original question is way of.

Changing the SSID on a WLAN does in no way affect connectivity. Once the
change has taken place, the client should get an IP address from the
DHCP server, and connectivity to everything should be restored to the
way it was prior to the SSID being changed. The fact that the OP cannot
get his e-mail after changing the SSID is most likely coincidental.

Lars M. Hansen
http://www.hansenonline.net
(replace 'badnews' with 'news' in e-mail address)

On Sun, 02 Jan 2005 22:30:48 -0500, in alt.internet.wireless , Lars M.
Hansen <(E-Mail Removed)> wrote:

>There's absolutely no relationship or even similarities between changing
>the SSID and changing the workgroup name. Changing the SSID is simply a
>minor change in what name the wireless client uses when connecting to a
>network. Changing the workgroup name is a major change in what name the
>operating system uses when participating in a network.

This is all true

>There is absolutely no need to reboot your computer after changing the
>SSID.

Yes

>There are no benefits to doing so, and there's little point in
>suggesting that it in any way, shape or form would help or even rectify
>the OPs original question is way of.

I disagree with this tho - its very likely that some other config change
has been made and rebooting the box will probably help.


--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt>

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

On Mon, 03 Jan 2005 11:18:58 +0000, Mark McIntyre spoketh

>On Sun, 02 Jan 2005 22:30:48 -0500, in alt.internet.wireless , Lars M.
>Hansen <(E-Mail Removed)> wrote:
>
>>There's absolutely no relationship or even similarities between changing
>>the SSID and changing the workgroup name. Changing the SSID is simply a
>>minor change in what name the wireless client uses when connecting to a
>>network. Changing the workgroup name is a major change in what name the
>>operating system uses when participating in a network.
>
>This is all true
>
>>There is absolutely no need to reboot your computer after changing the
>>SSID.
>
>Yes
>
>>There are no benefits to doing so, and there's little point in
>>suggesting that it in any way, shape or form would help or even rectify
>>the OPs original question is way of.
>
>I disagree with this tho - its very likely that some other config change
>has been made and rebooting the box will probably help.

To our knowledge, nothing else has been changed. If everything is the
same except the SSID, then it should only take a matter of minutes for
the network card to recognize the change and connect to the network and
obtain an IP address. Since the OP can get internal mail, it appears
that he does have a successful network connection.

Lars M. Hansen
http://www.hansenonline.net
(replace 'badnews' with 'news' in e-mail address)

On Mon, 03 Jan 2005 07:38:41 -0500, in alt.internet.wireless , Lars M.
Hansen <(E-Mail Removed)> wrote:

>On Mon, 03 Jan 2005 11:18:58 +0000, Mark McIntyre spoketh
>
>>I disagree with this tho - its very likely that some other config change
>>has been made and rebooting the box will probably help.
>
>To our knowledge, nothing else has been changed. If everything is the
>same except the SSID, then it should only take a matter of minutes for
>the network card to recognize the change and connect to the network and
>obtain an IP address. Since the OP can get internal mail, it appears
>that he does have a successful network connection.

This does'nt invalidate the suggested fix...
--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt>

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

Mark McIntyre wrote:
> On Mon, 03 Jan 2005 07:38:41 -0500, in alt.internet.wireless , Lars M.
> Hansen <(E-Mail Removed)> wrote:
>
>> On Mon, 03 Jan 2005 11:18:58 +0000, Mark McIntyre spoketh
>>
>>> I disagree with this tho - its very likely that some other config
>>> change has been made and rebooting the box will probably help.
>>
>> To our knowledge, nothing else has been changed. If everything is the
>> same except the SSID, then it should only take a matter of minutes
>> for the network card to recognize the change and connect to the
>> network and obtain an IP address. Since the OP can get internal
>> mail, it appears that he does have a successful network connection.
>
> This does'nt invalidate the suggested fix...

Hate to tell you mr THINKS he knows it all (lars not mark), but that's
exactly the attitutude I love to see as a consultant. I get to charge
hundreds of bucks to fix the errors people like you claim can never
happen...Heres a hint, If you have a WAP/Router, and change the ssid on the
wireless part, it doesn't effect the wired parts of the network, but if your
mail server is wireless and waiting for someone to hit "connect" (SP2
doesn't autoconnect by default), it will do exactly as the OP said (you can
email to others on the network, but not get stuff from the wireless node
that talks to the outside mail service, until it is re-connected, and the
easiest way to train dumb minimum wage employees to handle a problem, is to
teach em one thing... reboot... and then if it still doesn't work, call
support)