1359 Internal Error

from GoogleSign inHidden fieldsSearch for groups or messages

Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > System Error 1359; An internal Error has occurred Want to Advertise Here? Solved System Error 1359; An internal Error has occurred Posted on 2005-11-15 Networking 1 Verified Solution 7 Comments 12,521 Views Last https://groups.google.com/d/topic/voiceattack/lZOBzfbJrQA Modified: 2010-01-19 Hello, Whenever I try to access computer A from computer B on my network, I receive the message that "...is not accessible... An internal error occurred." Also, whenever I try to connect through command prompt (net use \\computer\share password), I am told that "System error 1359 has occurred. An internal error occurred." Do you have any idea what this means? I've only https://www.experts-exchange.com/questions/21632232/System-Error-1359-An-internal-Error-has-occurred.html seen the problem mentioned in error code lists; it seems like this rarely occurs in the world. 0 Question by:davidmigl Facebook Twitter LinkedIn Google Best Solution byCetusMOD PAQ'd, 500 points refunded. CetusMOD Community Support Moderator Go to Solution 6 Comments LVL 18 Overall: Level 18 Networking 1 Message Expert Comment by:Rartemass2005-11-15 From what i've found this is related to system restore issues. Turn off System restore and try again. Go here for instructions on how to turn it off/on http://support.microsoft.com/kb/310405 0 Message Author Comment by:davidmigl2005-11-17 Tried turning off system restore and rebooting. Still no luck. I'm thinking I might just reinstall windows because of another problem that is present; I cannot get the XP luna styles to work, and when I go to the "appearance" tab of display properties, I can't select windows XP style. I probably need to create a new question for that, though. 0 Message Author Comment by:davidmigl2005-11-17 Alright - I solved all those problems, not by directly addressing them, but by upgrading from XP SP1 to SP2. Apparently SP2 refreshes many of the system files, making it almost equivalent to a reinstall. Needless to s

Popular Forums Computer Help Computer Newbies Laptops Phones TVs & Home Theaters Networking & Wireless Windows 7 Windows 10 Cameras All Forums News https://www.cnet.com/forums/discussions/cannot-enable-administrator-account-540249/ Top Categories Apple Computers Crave Deals Google Internet Microsoft Mobile Photography Security Sci-Tech Tech Culture Tech Industry Photo Galleries Video Forums Video Top Categories Apple Byte Carfection http://forums.isaserver.org/Error_1359_w%2F_request_forwarding/m_2002040741/tm.htm CNET Top 5 CNET Update Googlicious How To Netpicks Next Big Thing News On Cars Phones Prizefight Tablets Tomorrow Daily CNET Podcasts How To Top Categories Appliances Computers 1359 internal Gaming Home Entertainment Internet Mobile Apps Phones Photography Security Smart Home Tablets Wearable Tech Forums Speed Test Smart Home Top Categories Tour CNET Smart Home Smart Home News Smart Home How To Best Smart Home Devices Cars Top Categories Car Reviews Best Cars New Cars Used Cars Deals Top Categories Cheapskate Best Tech Under $50 All 1359 internal error Deals Tech Deals Non-Tech Deals Audio Deals Cell Phone Deals Desktop Deals Laptop Deals Hard Drive & Storage Deals Printer Deals Tablet Deals Camera Deals Monitor Deals Software Deals TV Deals Web Hosting VPN Services WordPress Hosting Domain Names Download Sign In / Join Sign In to CNET Join CNET Member Benefits My Profile Forums Sign Out US Other editions United Kingdom Australia China France Germany Japan Korea CNET en Español CNET Forums Windows Vista Cannot enable administrator account Windows Vista forum About This ForumCNET's Forum on Windows Vista is the best source for finding help or troubleshooting advice from a community of experts. Discussions cover Windows installation, driver problems, crashes, upgrading, service packs, and other Windows Vista-related questions.Real-Time ActivityMy Tracked DiscussionsFAQsPoliciesModerators Question Cannot enable administrator account by Steven Haninger / September 2, 2011 9:01 PM PDT I am trying to resolve an issue with another persons Compaq Presario V6000 laptop running Vista Home Premium. The original issue was that he forgot his user p

| Address Book | Member List | Search | FAQ | Ticket List | Log Out Error 1359 w/ request forwarding Users viewing this topic: none Logged in as: Guest Tree Style Printable Version All Forums >> [ISA 2006 Publishing] >> Web Publishing >> Error 1359 w/ request forwarding Page: [1] Login Message << Older Topic Newer Topic >> Error 1359 w/ request forwarding - 16.Mar.2007 11:36:49 AM jtower Posts: 1 Joined: 16.Mar.2007 Status: offline I have ISA 2006 publishing a site on a web farm. For simplicity, the web farm only has one server in it right now (to grow later). The application is supposed to display more features to users originating from my company's public internet IP than it displays to otherinternet users. To support this feature, I need the REMOTE_ADDR which it appears I can only get by turning on request forwarding (Requests appear to come from the: Original client who sent the request). FYI, I also need to support HTTPS and HTTP awareness at the application level so the application can redirect to/from secure on a page-by-page basis. Finally, it would be nice if I could also use the "forward the original host header..." setting so I could build redirection links off the HTTP_HOST server variable. Everything works fine until I turn on the request forwarding feature. When it's on, I get: Error Code: 500 Internal Server Error. An internal error occurred. (1359) Here's my setup: - ISA 2006 Ent - Listener set up on 80/443 with wildcard cert *.externalsite.com - Individual rules matching each app:client.externalsite.com and binding to successive internal ports: - client1.externalsite.com -> webserver:80/443 - client2.externalsite.com -> webserver:81/444 - etc... - Rules all use internal.domainname.com as internal site name (to later support farm) - Webserver publishes sites on above specified IP/Port combination with corrent client.externalsite.com host heade