Help fight cancer with F@H! join team ECF today!!!!!!
- Thread starter Thrasher
- Start date
- th_trl_thread_readers 0
- Status
For me, this is all basic stuff. Hang in there case, we'll make a geek out of you yet!Ok, cool. Hey I'm catching up.
geek? I doubt it but this is good experience for me. I use to be more experienced with this stuff but I got lazy for about 10 yrs and now everything has changed.
For remote pc
Ok lets see for XP you would go start, connect to, show all connections. Find the current network connection - will prolly be the only one - right click and then status. in the window that opens i think there will be a details button and that will show you what the current ip address, subnet mask, and default gateway. Write them all down and close the windows taking you back to the network connections. Then you can right click the connection again and this time click properties. In the properties window will be a ipv4 (internet protocol version 4) entry. Double click it and change the setting from 'obtain bla bla automatically' to 'use the following address' and enter the numbers you wrote down. Then ok and ok so your back at the network connections window and you should now have a static ip set. Use this same number that you wrote down for the ip it asks for in both the remote desktop and adding the remote client windows on the main pc.
oh boy my finger getting tired all this typing is a workout LOL
Ok lets see for XP you would go start, connect to, show all connections. Find the current network connection - will prolly be the only one - right click and then status. in the window that opens i think there will be a details button and that will show you what the current ip address, subnet mask, and default gateway. Write them all down and close the windows taking you back to the network connections. Then you can right click the connection again and this time click properties. In the properties window will be a ipv4 (internet protocol version 4) entry. Double click it and change the setting from 'obtain bla bla automatically' to 'use the following address' and enter the numbers you wrote down. Then ok and ok so your back at the network connections window and you should now have a static ip set. Use this same number that you wrote down for the ip it asks for in both the remote desktop and adding the remote client windows on the main pc.
oh boy my finger getting tired all this typing is a workout LOL
OK, that's it for tonight. Chris has offered to walk me through setting up remote desktop via phone at his convenience. It won't be tonight but we will get it done. Thank you all for helping. I might not have understood everything but I did get something out of it, quite a lot actually. Now back to our regularly scheduled FAH talk. 
Sorry harmonic. Like you said one time "I need to type faster"
I'm calling it quits for tonight but thank you for going to all this trouble. It will be a lot easier to setup talking to somebody on the phone. 
I have a solution..... reinstall F@H, and use the Expert (Custom) Install.... Make sure you tell it to install as a service, then you'll never have to mess with folding on that machine lol. You wouldn't even need to login to a user account, as long as Windows is powered on, it'll be running F@H client as a service.
This is how I installed it on my server.
This is how I installed it on my server.
LOL I'm just trying to find a way to make things simple for you.
None of this sounds simple but having somebody walk me through it on the phone is a lot easier. But thanks.
I did that (installed as a service) on my inlaws computer but I am not sure you can monitor that remotely to see your ppd and such unless the client interface is running
and a static ip from their isp would be handy as well.I did that (installed as a service) on my inlaws computer but I am not sure you can monitor that remotely to see your ppd and such unless the client interface is running
Even without a static ip the one they have hasent changed since I set it up. BUT no matter what I do I cant connect to their client regardless of opening firewall ports everywhere and ect - even though I can connect to mine from their end. They have at&t internet there must be some kind of firewall or something just upstream from their connection. After working on it for several days I finally gave up on trying to monitor it and just let it run on its own.
Oh, you meant monitor it externally.... I haven't tried that in any way yet.
Also check the ports set in the client versus the ports opened in the firewall... I noticed mine were different from default on one of mine.
also make sure that port forwarding is done for the correct IP as well while you're at it.
also make sure that port forwarding is done for the correct IP as well while you're at it.
Yea I have all my internal network computers monitored in one client on the main pc and I can monitor my main pc from their end across the net (even though it only shows this pc and not the rest that its monitoring) but just cant connect to them from here even though all the right ports are opened and forwarded where nessary. Cant ping or anything else either. I guess it could still be something setup in the firewall/router in their dsl modem device but based on the settings I used it should be working. Even added a specific allowance in the modem firewall to accept packets from my ip address... They dont run 24/7 anyhow though so I finally decided to just let it be and fold whatever it folds lol
It's nice to see all the Windows chatter. Terry sure is giving the geeks a workout in here. Sorry, I've not been around much but Real Life has been a bit on the busy side off late.
199th.. WooHoo!!
Loft/Chris, Congratulations on your respective totals as well. You guys sure are racking up the points.
/me goes looking for another few computers to throw into the fray!
- Status
Similar threads
