• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Renegade box on workgroup (ICS Problem)

Rumble

Member
I have a workstation that connects to the others in the group (sees hard drives ,files etc) but refuses to connect to internet with either auto detect ip settings or setting ip, subnets and gateways manually. All are win 2k on wifi 80211b . Connected to dsl thru a router with wifi access point plugged into the router. The other boxes connect no problem (I also tried this machine with a 10/100 hard connection with the same results. Is this a registry setting or perhaps a result of leftover setting from a previously installed and removed internet sharing software ? (All Aboard I Believe was the software)
Thanks, John in Miami
 
As this software effects quite a lot of the tcp/ip stack settings, I'd roll through the system registry looking for the software name and removing the keys that you find. I know this is scary, but for something like this software package, even after you remove it, the reg settings may have adverse effects on the network connection.

HTH,
-Cerial
 
Thanks- I'll give a try "We ain't afraid of no stinkin' registry" I may try a win2k repair as well ...or an xp upgrade ...or somthing
 
erm....why not just uninstall and reinstall TCP/IP - yes it can be done in the connection settings and it solves more problems than people think in networking.
 
Dyehouse1-Thanks - You sometimes overlook the obvious.....I will give it a try...but I had tried switching connection from wifi to 10/100 and the wired connection still could not see the internet..assuming that this is a totally new tcp/ip setting
 
Solution Found- You always feel like a dummy when it proves to be somthing simple -It was in the advavnced tcpip settings- somehow a restriction got clicked - deselected -everything OK
 
Back
Top