[quote name='PFDurand35' date='Oct 8 2005, 09:48 AM']
Thank you Mitch1509! Although I'm apparently not out of the woods yet. My DHCP Client and RPC serviced were not set to automatic and now are. Such a simple fix (well almost - see below). I have to say I'm not overly impressed that Verzion did not know to check for this."
As far as I know, this rpc server unavailable error that comes up after you notice your lan is stuck in Acquiring netwrk address, then when you go to ipconfig, the ip says 0.0, and when renewing you get rpc server unavailable, is from some branch of the Mytob worm. This is all that most of the verizon bulletins posted back in March. I've also noticed that when I see this on a person's pc, that they cannot do anything w/their lan, which my understanding, is bound to their nic. I gather from the behavior of these symptoms is that something affects the NIC's ability to communicate w/the servers to get an IP address. So Mytob being what's been said as the culprit has made sense to me, since virus' do things like that to the internet protocol sometimes. I've also noticed that when this happens not only can you do nothing w/the LAN to get online, but the only way to get ppl online is to create a connectoid. If you have the verizon cd the tech would end up either creating WinPoet dialer or if you use windows XP, an XP dialer w/wan miniport pppoe connection. Why those types of connections wrk when the router doesnt, has not been explained to me. If any of you are more tech saavy than I am and have training w/netwrking and this protocol, I'd love your input, as I have been looking for solutions and explanations for awhile.
I have little time to investigate mytob or the rpc server unavailable error, but have seen it enough I googled it today to see what all it could mean, or to see if possibly the rpc server unavailable when the above symptoms occur is something not related to the Mytob worm. I'm happy to see a solution posted above that makes a little more sense than the simple phrase "it's an effect left from the Mytob worm."
I am not a computer technician, but I'm very pc saavy, I have a lot of yrs of hands on experience, love to learn new things and anything w/the pc, and am in the dsl tech support field. What I've just posted is part of the reason the verizon tech couldnt tell you that. We do not specialize in pc errors. Just your internet connection basics. Your basic tcp/ip settings, int options settings, some of the lan settings, assistance w/checking ip, releasing and renewing ip, verizon's pop3/smtp settings, setting up the basic aspects of the routers Westell 2200, 327w,6100, ActionTec, Linksys, minimal wireless support, and the installation or removal of verizon cd sftware. Maybe a little more. Beyond that you save time and headache by getting a certified person to see what you're running into personally instead of trying to explain it over the phone which has more of a disadvantage, unfortunately.