After an upgrade from NSS 4 (Comcast) to NSS 5, we lost the ability to share printers and files. The network consisted of
Hard wired HP media center with Vista Home premium
Dell laptop wireless XP PRO SP3
IBM laptop wireless XP PRO SP3
After spending several hours reconfiguring a Home / Small Office network on each computer, reconfiguring the Norton Network to a Full Trust and implementing computer monitoring, I was unable to return the NSS 4 ability to share files and printers. VERY frustrating.
The very last step I tried was to reboot the Linksys E3000 wireless router from maintenance menu. After all the time and effort spent on each machine, the last step was the answer. Apparently powering down the router and restarting IS NOT THE SAME function as rebooting from the router maintenance.
I hope that this may help others having networking / sharing problems
After an upgrade from NSS 4 (Comcast) to NSS 5, we lost the ability to share printers and files. The network consisted of
Hard wired HP media center with Vista Home premium
Dell laptop wireless XP PRO SP3
IBM laptop wireless XP PRO SP3
After spending several hours reconfiguring a Home / Small Office network on each computer, reconfiguring the Norton Network to a Full Trust and implementing computer monitoring, I was unable to return the NSS 4 ability to share files and printers. VERY frustrating.
The very last step I tried was to reboot the Linksys E3000 wireless router from maintenance menu. After all the time and effort spent on each machine, the last step was the answer. Apparently powering down the router and restarting IS NOT THE SAME function as rebooting from the router maintenance.
I hope that this may help others having networking / sharing problems
Welcome,
Sorry you had to go the long way around to solve the problem.
The difference in the router boots is like the difference in PC boots - warm - from the keyboard, cold - from the power switch. With the warm boot not everything in memory is erased. This is where the rub comes.
As a suggestion, whenever you are doing things which require multiple reboots, make at least one of them a cold boot. I like to make the last one a cold boot regardless.
Actually, the odd thing here is that the OP is reporting that the cold boot didn't solve the problem, and what finally did was rebooting the router from its software. This certainly isn't intuitive--for the reason you guys note; I'd have thought the same thing. So this is a good tip--and dpdido shoulld perhaps mark their own post as solution so other users encountering something similar can find it!