 AZinOH join:2007-04-25 Swanton, OH Reviews:
·Windstream
| Why Won't It Connect? I have a wireless desktop which dual-boots Vista & Ubuntu 10.04. When using Ubuntu, I can connect to my network almost immediately. However, when I end the Ubuntu session and go into Vista there is sometimes a problem. Although I can see my own network and have excellent signal strength (4 or 5 bars) Vista doesn't always want to connect immediately. The Sagem 1704 modem/router acts as though it doesn't want to release an IP address. Today I waited 17 minutes before Vista would connect. After connecting, it works just fine. Does this sound like a good guess? If no, what else should I be looking at? If yes, is there a setting I should tweak that might solve this? Thanks for any assistance. |
|
 billaustinthey call me Mr. BillPremium,MVM join:2001-10-13 North Las Vegas, NV kudos:2 | I would say it is a Windows problem. The router doesn't care what OS you run, and should be assigning the same IP for either one since it is the same network card.
Check for updated drivers for the wireless card. Have you updated Vista to SP2 and loaded all the other updates? |
|
 AZinOH join:2007-04-25 Swanton, OH | Yes I am on SP2 and have loaded all updates. It says the driver for the Broadcom wireless card does not need to be updated. |
|
 billaustinthey call me Mr. BillPremium,MVM join:2001-10-13 North Las Vegas, NV kudos:2 1 edit | Check the vendor's site for the wireless card and see if they have an updated driver. The one provided through Windows update will not always be the latest one.
A quick google search shows your router has a less than stellar reputation. I would look at putting it in bridge mode and getting a separate wireless router. |
|
|
|
 AZinOH join:2007-04-25 Swanton, OH Reviews:
·Windstream
| said by billaustin:Check the vendor's site for the wireless card and see if they have an updated driver. The one provided through Windows update will not always be the latest one.
A quick google search shows your router has a less than stellar reputation. I would look at putting it in bridge mode and getting a separate wireless router. Stellar or not, this router is what my ISP has chosen for all new installs until/unless they decide to provide something different. I'll continue checking for a driver update. |
|
 mozerdLight Will Pierce The DarknessPremium,MVM join:2004-04-23 Nepean, ON | reply to AZinOH said by AZinOH:The Sagem 1704 modem/router acts as though it doesn't want to release an IP address. Today I waited 17 minutes before Vista would connect. After connecting, it works just fine. Does this sound like a good guess? If no, what else should I be looking at? If yes, is there a setting I should tweak that might solve this? Thanks for any assistance. What happens if on system boot-up you go into Vista first? does Vista connect immediately or does it take a long time? -- David Mozer IT-Expert on Call Information Technology for Home and Business |
|
 AZinOH join:2007-04-25 Swanton, OH | If I boot Vista first it usually connects within a minute or so. |
|
 mozerdLight Will Pierce The DarknessPremium,MVM join:2004-04-23 Nepean, ON | OK, that is what I expected.
Next question --- in the Dual Boot scenario if Vista is the 1st system you boot into then end that session and go into Ubuntu what is the network behaviour? |
|
 AZinOH join:2007-04-25 Swanton, OH | When booting Ubuntu after a Vista session, Ubuntu connected to the network in less than 15 seconds. |
|
 mozerdLight Will Pierce The DarknessPremium,MVM join:2004-04-23 Nepean, ON 3 edits | OK, that is what I expected. Before switching from Ubantu you need to go into terminal mode and release the IP THEN switch to Vista and you should connect quickly. In Ubantu, open terminal and type the command:
# ifconfig [cenection] down
[EDIT] make sure that ur in root. and if the above does not work for U you could also try
# dhcpcd -k
Alternatively if you want to avoid this behaviour you will need to: 1.. Put the Sagem 1704 modem/router in 'bridge' mode 2.. use another wireless router to act as your DHCP server Sagem 1704 in bridge mode then connected to another wireless router that does all the routing and wireless connectivity.
Then your connectivity will work the way that you want in a dual boot scenario like you have. |
|
 billaustinthey call me Mr. BillPremium,MVM join:2001-10-13 North Las Vegas, NV kudos:2 | reply to AZinOH said by AZinOH:Stellar or not, this router is what my ISP has chosen for all new installs until/unless they decide to provide something different. I'll continue checking for a driver update. Just because they provide a poor modem/router combo does not mean you have to live with poor behavior. Put the modem in bridge mode so that the router functions are disabled and it acts as just a modem. Then connect a separate wireless router to the ethernet port. This should resolve your issues. |
|
 wayjacPremium,MVM join:2001-12-22 Indy kudos:1 | reply to AZinOH said by AZinOH:is there a setting I should tweak that might solve this? Thanks for any assistance I would manually set the tcp/ip info for both operating systems |
|
 AZinOH join:2007-04-25 Swanton, OH Reviews:
·Windstream
| reply to mozerd
said by mozerd:OK, that is what I expected. Before switching from Ubantu you need to go into terminal mode and release the IP THEN switch to Vista and you should connect quickly. In Ubantu, open terminal and type the command:
# ifconfig [cenection] down
[EDIT] make sure that ur in root. and if the above does not work for U you could also try
# dhcpcd -k
Would I be able to run those commands using sudo? I don't think I've ever used /root...and not sure I want to. Thanks for your reply. |
|
 mozerdLight Will Pierce The DarknessPremium,MVM join:2004-04-23 Nepean, ON 1 edit | said by AZinOH:Would I be able to run those commands using sudo? I don't think I've ever used /root...and not sure I want to. Yes, you can use sudo as follows;
sudo ifconfig eth0 down
sudo /etc/init.d/networking stop
The first command only takes down eth0 (if that is the device [network interface] you are working with). The second command takes down all networking [other ethernet devices, wireless, etc.]. |
|