For those new to message boards please try to follow a few simple rules when posting your question.
Choose the correct forum for your message. Posting a VB.NET question in the C++ forum will end in tears.
Be specific! Don't ask "can someone send me the code to create an application that does 'X'. Pinpoint exactly what it is you need help with.
Keep the subject line brief, but descriptive. eg "File Serialization problem"
Keep the question as brief as possible. If you have to include code, include the smallest snippet of code you can.
Be careful when including code that you haven't made a typo. Typing mistakes can become the focal point instead of the actual question you asked.
Do not remove or empty a message if others have replied. Keep the thread intact and available for others to search and read. If your problem was answered then edit your message and add "[Solved]" to the subject line of the original post, and cast an approval vote to the one or several answers that really helped you.
If you are posting source code with your question, place it inside <pre></pre> tags. We advise you also check the "Encode "<" (and other HTML) characters when pasting" checkbox before pasting anything inside the PRE block, and make sure "Use HTML in this post" check box is checked.
Be courteous and DON'T SHOUT. Everyone here helps because they enjoy helping others, not because it's their job.
Please do not post links to your question into an unrelated forum such as the lounge. It will be deleted. Likewise, do not post the same question in more than one forum.
Do not be abusive, offensive, inappropriate or harass anyone on the boards. Doing so will get you kicked off and banned. Play nice.
If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums.
No advertising or soliciting.
We reserve the right to move your posts to a more appropriate forum or to delete anything deemed inappropriate or illegal.
Having an odd issue when RDP connecting to a server that I can't for the life of me find any solution for. Sorry if this isn't the correct place to post but any assistance is immensely appreciated.
Essentially, when initially connecting to the terminal server with RDP, the printer is correctly set as the default. However, when the client disconnects (not sign out, just closing the RDP session) the default printer changes and must be manually set as default again. So the catch is, that we'd need a solution that isn't based on user login, but instead upon re-connection to the server.
Since their not logging in every time a login script would also sadly be out. Forcing the printer in question to stay as default for ONLY that user would be the aim (lots of other users on the server that do not have this issue and use other printers).
Another thing too note is that the printer is adding as default upon initial log in but is not being added to the server's control panel printer list. I am hoping that being able to find a solution to this control panel issue will solve the default printer setting issue.
Our company is using GlobalProtect to provide remote domain access for people working from home.
I have valid credentials for connecting to the VPN portal, and valid credentials for the two company domains.
When the VPN connection is active, I can ping almost any resource by name or IP, but when I attempt, say, to map a drive to a ping-able server, I am unable to do so.
I asked the IT guy for help, and when he disabled some Hyper-V network adapters on spec, I was suddenly able to map a drive. Joy in mudville.
BUT the next day, I believe that after I launched the Hyper-V manager, I suddenly lost the ability to map once more. I tried disabling those Hyper-V network adapters again, but no joy in mudville this time.
Granted, I may have done something else to put my setup in that state, but I obviously can't tell you what.
Any ideas would be appreciated.
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
"I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
The first thing I would do is revalidate the IPv6 configuration on the web server, starting from the network interface, down to the web service configuration. I would also try the ipv6only=on statement in the nginx config file, and see whether that makes a difference.
"Five fruits and vegetables a day? What a joke!
Personally, after the third watermelon, I'm full."
I migrated a web application from a local (virtual) server running Windows Server 2003 to another local (virtual) server running Windows Server 2012 R2.
In our warehouse we do order picking with (non domain joined) pda's using this web application. The (motorola) pda's run Windows CE, and are connected to the network over wifi / wlan.
I can connect to the web application on the old server from the pda's, but I cannot connect to the web application on the new server. I cannot even connect to the default website on the new server.
I can connect to the web application on both the old and new servers, with normal domain joined PC's running Windows 7 and 10, and also with my iphone (safari browser).
So the question is, how do I get my pda's to connect to the web application on the new server?
Google has not been forthcoming, or I simply haven't been able to figure out the right search term.
Any help very much appreciated. Please let me know if I have left out pertinent information or if there might be a better forum for this question.
My advice is free, and you may get what you paid for.
First off, are we sure it's not a network issue like firewall or routing? Can the PDA see the new web server. You may not have something like ping on the PDA, but you should be able to ping or traceroute from the server to the PDA.
Assuming its not one of the above, could it be a SSL/TLS issue? Does the WS2012 server listen only for https, while the PDA is trying http only? If the PDA is trying https, does it speak a compatible version with the server (e.g PDA is using SSLv2 while server only accepts TLSv1.2 and later)? If that all seems correct, are there any logs on the WS2012 system that show the PDA connect attempts and why they were rejected?
Hello all. I wanted to repost this with some more info that will hopefully help understand my question a little better. Please see screenshots links a the bottom of post.
Our email program needs to connect and send mail using MS O365 accounts and the TLS protocol for security reasons with port 587. For testing, I used TELNET to the O365 STMP server using port 587, the EHLO command and starting TLS using the STARTTLS command but that is far as I can get. After that, anything I do just sits there and no more responses from the server. I am trying to figure login commands at this point, which I researched from Google but didn't seem to work, much less anything else. A set of connection rules I found about TLS here on Code Project is the list below. If I need to, I can send a screenshot of what the TELNET session looks like to help out. Any help would be very appreciated. Thanks!
1. The client connects to the server using TCP.
2. The server sends a welcome message using the un-encrypted connection to the client.
3. The client sends a EHLO command using the un-encrypted connection to the server.
4. The server responds to the EHLO command using the un-encrypted connection.
5. The client sends a STARTTLS command using the un-encrypted connection to the server.
6. The server responds to the STARTTLS command using the un-encrypted connection.
7. The client negotiates an encrypted connection with the server.
8. The client sends a EHLO command using the encrypted connection to the server.
9. The server responds to the EHLO command using the encrypted connection.
A) This first image is how I TELNET to email server for testing purposes. In the program, we use SMTP sockets to do the same thing: Image 3
B) This next one is a normal SMTP screen using port 25 (NO TLS) and connects successfully: Image 1
C) Last screenshot is my TELNET attempt to TLS protocol in which I am stuck on what to do next after successfully starting the TLS sever: Image 4
Click + (New) -> From: Partner organization To: Office 365 -> Next -> Name: Bruce (what ever) -> Next -> Use the sender's IP address -> Next -> + (Add IP) 188.8.131.52 -> OK -> Next -> Select Security restrictions and click your way through.
You should be able to side step TLS and still be somewhat secured through the connector.
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
We have using Essl K20 BioMetric System.
And device is connected Using TCP LAN and maintain data in Access DB, The Data transfer more difficult from device.
Each Time we download from etimetrack Desktop App.
And now we need to transfer data automatically to PC with out manual download.
Any possible way for this?