XxthugstylezxX

Members
  • Content count

    696
  • Joined

  • Last visited

Community Reputation

1 Neutral

About XxthugstylezxX

  • Rank
    a55 k1553r
  • Birthday 01/01/1986

Contact Methods

  • AIM
    thugstylez91396
  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Interests
    computers, Security, females, cars specificly imports,
  • Location
    734/313
  1. If I have a domain such as www.xyz.com even though the website is being hosted else where, can I still use www.xyz.com as my domain controller for my network? Or do I even really need a domain to make a DC? As long as im not creating a server of any other sort? Thinking about it logically you would need a static IP address in order to have a DC, and you could not use a actual domain without a static ip address. I dont know I just need it put in English to me, the books and white papers have not done me justice. Basically I have two projects that involve me running a DC. So any further explanation or a direction in a white paper, or tutorial that can explain it good please it would be appreciated.
  2. What port is RDP set to on the machine you're trying to connect? That is the port you should use when on your local network... don't worry about what your WAN is set to, since it doesn't matter (you should just be using the local hostname or IP address from inside your network). 3390 works from outside, but that has no bearing on the server itself; that's just the port forwarding. You could have 3390 on the outside forward to 3389 on the target box and it would work the same way. You can have any port on your WAN forward to any server/port on your LAN, and neither one has any bearing on the other... you just have to remember that they might be different when you're outside. I have RDP on my local machine listening on port 3390. Due to my router not really port forwarding I had open up the port on the firewall of the router. So I really couldnt just have port 3390 forward to RDP's default 3389 without buying a different router. Since it's not my house I really cant up and buy a new router and say hey Mom/Dad im replacing this POS with this not so POS. That's why i took the route I did. Testing further I could still remote locally to my machine however i still had to specify the port. The default port did not take. Thanks again guys for all the help.
  3. This is great feedback. Thanks guys! Now that i have all your IP's logged time to start my real dirty work hehe. So I guess what i've gathered and based on what's been said. The default port of 3389 will work locally? As it has before, before i started tinkering with the security. However when I have terminal service listening on a different port it will not work locally, due to packets going out and coming back in. Which makes perfect sense. That is unless my machine was sitting on a DMZ. However and this is something im going to be able to test myself... I should be able to use RDP locally through my local work group? Still using the newly defined port terminal service is listening on. I guess I still have a bit of work to do. Again thanks guys. You saved me the trouble of having to call a bunch of friends that know nothing about computers and explaining step by step how to do this. hehe
  4. Was that with the default port? Or with the port I have RDP listening on via 3390?
  5. That may be what it was then. Before i set the new port, it was working locally on my lan. Obviously through another computer. However since doing everything else i have yet to be able to use that same computer to remote. My overall goal is to beable to work on my computer obviously anywhere. However i also want to connect locally, which thinking about it I can do via work groups. Thanks for the help, just a bit more testing and hopefully i can move onto my next tasks. =)
  6. All of those were/are great suggestions. - Nmap-online did not show any good results. Granted it's been a while since i've used nmap. - sheilds up also did not turn up any results for me - canyouseeme.org showed my newly listening port of 3390 open and forwarding correctly, and i also checked 3389 and the previous one i set of 3387 that both did not get through. Seeing that conyouseeme.org shows 3390 does port forward that mean that its on my computers end of why i cannot connect? If anyone wants to try, and by all means its my computer and i am giving explicit permission to do so. Try to connect to xplicit.servebbs.com:3390
  7. Ok i've registered at dyndns got my domain etc etc. I configured everything to allow myself to RDP to my desktop from where ever. Everything on a default stand worked perfectly. However i tried to secure it and now it does not work at all. What i've done security wise: - Changed the default port that terminal service listenes on via registry edit. In this case i've changed the default port from 3389 to 3387. - Changed local security polocies to allow only 1 user, in this case my added administrators acount. I deleted the administrators group, and remote login group. - I configured my router which is where i believe the problem is to port forward on port 3387. I unfortunatly use at&t's modem/router/wireless 2wire. Model 3800HGV-B. For those of you that use this god aweful device. You know that the "firewall" is complete crap. You really cant port forward. You can only define a firewall exception. When i added the default RDP, and Remote Assistance it worked. Now it does not work. Sorry if that did not make much sense im currently on about 3 hours of sleep for the past 48 hours. However any help would be appriciated.
  8. I figured it out. It would login with "Use last settings and configurations that worked" it would just run like shit, and if i tried doing anything it would freeze. So i got norton system works 2k7 to run win doctor. Sure enough between that, and ridding myself of a god aweful amount of viruses and spyware it works fine now.
  9. So there is nothing more you can do when recovery console, or xp repair wont show up, and windows wont boot fully? Besides the format and reinstall.
  10. Wow, you are more of a man than I. I would have told her to wait until i got there.
  11. I just dont understand why the repair console, or repair feature works sometimes with some computers, but not all. Also why there is not a bootable cd dedicated to the repair of xp like this that's made by third party. Guess its time to invest in a bigger external. =/
  12. Is it normal for XP repair console or the repair feature to not show up when running a xp cd? Are there only certain versions that have this? What am i missing? Basically damn virus ate system files rendering my desktop useless right now. I've rid myself of both spyware and viruses or at least as much as i could, but the computer will not fully boot xp even in safe mode. It will get to the login screen normally and freeze on a blank blue background. Or with safe mode it'll get to mud.sys file loading before it stops. As much as a format would be in my best interest there is way to much i did not back up, and way to much to rebuild. Any thoughts?
  13. So i need as many vista drivers video, and network wireless/lan that i can get to incorperate into a vista oem cd. Can anyone help. I've googled with no resultes for vista. I know there are packs for xp but not vista.
  14. Messaged you but guess your afk. Thats my ID. Begins with an i.

  15. This is almost the exact idea me and my buddy were working on. However we never lifted ours off the ground, and our's was more a all IT related e-learning/video. I think you should expand it to all fields of IT. Good job on the site btw. :voteyes: