 | Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years. Thanks, CNET Support |
I still can not get the remote assistance to work.
I have installed windows xp pro.Other people can log into me , but I can't log into them I get an error msg. win32 failed and will shut down. an the other msg. is remote host ncould not be resolved please try agin.
Im useing a westel router 237w I have turned the firewall off and turn off the virus software also.
I then checked of UPnP box and I don't know if I set up the NAT This is driveing me nuts I hear that most of all the problems are with westel routers and that they are very hard to set-up I call westel Tech. what a joke.I hope there is somebody out there that can help me with this problem. It cost me more to change from Home to PRO.
Thanks ****
P.S.
I get no help from Verizon or Westel
Discussion is locked
answer to the reply The other computer that I did the remote with got into my laptop with no problem at all and when I tryed to get back to his desk top that is when veery thing went wrong. the first Msg. was "remote host could not resolve please try again"
then I received an other Msg."win32 nor responding and will shut down" I own a company and I need to use the remote between all of the computers at first I had a mix between Home an Pro. and have changed them to the pro. ver. and have had the same problem all the time.I feel that the problem might be in the router set up or software this is no made up story as I do not play around and trying to run my bussiness. I hope that some might help and by the way when I received the Msg. that the computer was shuting down the lap top locked up Why?. In order to get the exact msg. I will have to one of the other ask me for a remote that is when this all happens
That points to a name resolution issue. It is not a router or Microsoft issue. Your IT staff needs to define how a name to IP address name gets resolved.
There is not enough information in your post for me to hazard a guess why the name didn't get resolved.
For testing, try a command window (hint: start, run, cmd) and try PINGing the computer by name. You can also help your IT staff with the NSLOOKUP command since it will help determine what DNS needs the entries for the target machine.
Best of luck in resolving your first issue.
-> Next that shutdown issue. That reeks of some virus/spyware/trojan or just damaged OS issue. Sorry, but there is not enough detail for me to guess otherwise.
Sik the IT people on that one.
In closing, TightVNC could be easier to setup and use. Try that. And it doesn't require the Pro version.
Bob
Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic