Windows 2008 R2 Port Issue

Dear Tech Gurus,
Please see that we have Windows 2008 R2 Enterprise Edition on which we run our application which uses TCP Port 49158.
Yesterday our application stopped accidentally and when we tried to start application again it refuses.
I have telnet 127.0.0.1 49158 and it shows the same server get this port.
I change the port to 48157 and again try to run the server and it started successfully.
Today same issue happened. And now the 48157 is not working same behavior and I change the port to 49158 and it works fine.
What will be the possible reason please help.
Thanks
Malik Adeel Imtiaz
Malik Adeel Imtiaz

Dear Techno Trev,
Thank you so much for your reply very much appreciated.
Can you please elaborate me that how I can reserve my (49158) port in Windows 2008 R2 as you said in your reply.
Thanks
Adeel Imtiaz
Malik Adeel Imtiaz

Similar Messages

Windows 2008 Terminal Server issue after swapping modem/router

Hi, I have a problem I just can't crack.
Windows 2008 Terminal Server, all patched and up to date. The IP Address is 192.168.1.11 (on a teamed intel controller). Terminal services enabled and working ok.
TP-Link Modem 192.168.1.1, RDP Port forwarded ok.
Set the Windows gateway to 192.168.1.1 and external access to RDP is not a problem.
We had some modem speed issues, so we got a much faster connection, but it can't be used for incoming RDP, so left the TP-Link in place. So added a 3G modem at 192.168.1.5 and set that as the gateway.
External RDP access still works perfectly, and now users have much faster internet.
The TP-Link is giving some reliability issues, so I swapped it over for another modem, a Billion modem. Same 192.168.1.1 IP address, same port forwarding. External RDP access is no longer possible.
Swap back to the TP-Link and everything is fine. Test the modem on another site, everything works as expected.
If I set the gateway on the terminal server to 192.168.1.1 with the Billion attached then external RDP access is no problem. If I set it to 192.168.1.5 then it stops working again.
I tried with a new TP-Link modem of the same model with exactly the same settings and this also had the same problem. External RDP access will only work the existing TP-Link modem, which is a problem as the modem appears to be faulty.
It's almost like it hasn't worked out that it's a new network, and when Windows does that it seems to lock down RDP. That is only my assumption from experience of moving computers to new networks and RDP won't work until windows prompts you with the new
network screen to select home, office or public.
Has anyone experienced anything like this before or can shed some light on the problem?
Thanks.

Hi,
How is the issue going now? Is there any update?
Thanks.
Jeremy Wu
TechNet Community Support

Windows 2008 FRS port Customization causing Replication Delay

Hi
we have 4 windows 2008 R2 DC. we have restricted the port for FRS Replication. now we are facing replication delay.
Not finding any error in DCDIAG, REPADMIN /Showreps and in FRS event there is an error 13508 and it is not recovering since from 3 days to 13509 so please suggest the solution
whether Port customizion is recommended

Hi,
We can restrict FRS replication traffic to a specific static port. However, if there is an intermediate network device or software that is being used to filter packets between domain controllers, we need to verify that the device or the software
allows communication over the specified port. Additionally, make sure the destination TCP port that we set is open on the firewall.
Regarding restricting FRS replication traffic to a specific static port, the following article can be referred to for more information.
How to restrict FRS replication traffic to a specific static port
https://support.microsoft.com/en-us/kb/319553
Regarding troubleshooting FRS Event ID 13508, the following article can be referred to for more information.
Troubleshooting File Replication Service
https://msdn.microsoft.com/en-us/library/bb727056.aspx#EMAA
Best regards,
Frank Shen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Remote desktop connection issue with an RDP client while connecting to some of windows 2008 and 2003 operating system flavors and not receiving SDin value choice 26 from DomainMCSPDU

Hi Team
We have our RDP client and i came across with one issue "Expected data got 3" with this client.
This issue is getting while connecting some of below operating system flavors.
Microsoft Windows 2008 Enterprise edition
Microsoft Windows 2008 Standard edition
Microsoft Windows 2003 servers
When we are trying to get RDP to those servers with our client, getting "Expected data got 3" error. One more main thing here is the specified error is not getting for all the servers of same operating system in above list.
Able to get the RDP console for those servers using mstsc client.
When i read the [MS-RDPBCGR] specification, i found the below points
mcsSDin (variable): Variable-length PER-encoded MCS Domain PDU (DomainMCSPDU) which encapsulates an MCS Send Data Indication structure (SDin, choice 26 from DomainMCSPDU), as specified in [T125] section 11.33 (the ASN.1 structure definitions
are given in [T125] section 7, parts 7 and 10). The userData field of the MCS Send Data Indication contains a Security Header and a Valid Client License Data (section 2.2.1.12.1) structure.
In my code i am not getting SDin value as 26. Is it the problem with Remote desktop Licensing in RDP servers as specified in the specification like "The userData field of the MCS Send Data Indication contains a Security Header and a Valid
Client License Data (section 2.2.1.12.1) structure."
Could you please explain me is this issue is happening due to Licence configuration in RDP server and please provide support with server side configuration if any because our code works for other servers ?
Thanks & Regards,
Pavan G.

Hello Pavan -
Thanks for contacting Microsoft Support. I'm researching this for you and request you to please send me mail at dochelp @ Microsoft dot com so that I can share tools and techniques to collect some traces and analyze.
Thanks.
Tarun Chopra | Escalation Engineer | Open Specifications Support Team

Windows 2008 Server contacting multiple public IP on port 80 and 443

Windows 2008 Server contacting multiple public IP on port 80 and 443
Source : Microsoft Lync 2010
Port : 80
Destination : unknown.prolexic.com
Source : Internet Explorer
Port : 80
Destination :a-0001.a-msedge.net
Source : Internet Explorer
Port : 443
Destination :204.79.197.200
Is this virus? how to stop the same?

Org name of the IP shows Microsoft Corporation
Since its hits on firewall , i will have to stop the same
but not sure for what its being contacted to these Ips
OrgName: Microsoft Corporation

Windows 2008 Server Enterprise R2 x64 and Perc 4/dc SCSI driver issue

Hello all, this is the first time posting so please forgive me if this has been posted here before. I did try to search this issue but zero returns.
OK, I have a Dell PowerEdge 2900. I have just put a fresh install of MS Windows 2008 ENT. Server x64. I cannot seem to find a driver for the PERC 4/dc SCSI controller I have installed. I have been told the 2003 x64 driver would work so I attempted to install that driver but was unsuccessful. Then I was told by Dell that the driver should be native to the OS. Is the driver native to 2008 Server (or, supposed to be)? Does anyone have an answer as to where I might retrieve am driver of the controller if not? Anyway, thanks in advance

Hello,
I don't have a PowerEdge 2900, but I do have a PowerEdge 2850. I'm also just a regular bloke like yourself that just happened upon your post and after I figured this driver debacle out I registered to hopefully help.
The good thing is my PERC card is the same in the PE2850 as it is in your PE2900, as I'm utilizing a PERC 4/DC. I've also managed to run into the same issue you ran into(?) trying to load Windows 2008 Server Enterprise R2 (support for 32bit processors have been removed in R2... so no more x86 versions... my poor PE2650s never stood a chance with this OS).
I can tell you officially from my experience/research Windows Server Enterprise R2 does not have support built into it for the PERC 4/DC card.
However, I was able to download the Windows 2003 x64 driver from support.dell.com and make it work after much trial and error with newer releases of the PERC 4/DC driver that were not accepted by 2k8R2.
Here's the link: http://support.dell.com/support/downloads/download.aspx?c=us&cs=RC956904&l=en&s=hied&releaseid=R100373&SystemID=PWE_PNT_P3C_2850&servicetag=FBCLP61&os=WX64&osl=en&deviceid=6396&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=3&libid=35&fileid=129549
File name (incase Dell moves it on you guys) is "perc-w2k3-6.46.3.64-A01.exe", date released 6/9/2005, build version 6.46.3.64, and the Dell revision number is A01.
Even though it states the driver is for the LSI Logic PERC 4e/Si it's sort of a mega pack including many other drivers such as the PERC 4/DC. This was much relief because I was thinking I would need to stick with Windows 2008 until I found this driver for Windows 2008 R2. :)
What I did was:
1) Downloaded the driver and extracted it to a USB drive.
2) Booted-up via the Win2k8R2 CD and when it got to the screen where it asked to install to a partition and didn't show me a partition to install Win2k8R2 to I selected the option to load a driver.
3) From the load driver option I just browsed to the directory where I extracted the files and selected that directory. If the "hide devices that are not compatible" option is selected (normally on by default) it will show you the proper driver.
4) Select the PERC 4/DC driver and then setup your partitions the way you would like them!
From there you should be able to boot into the OS... and really have some fun.
Now you have the power... I guess the choice is yours to R2 or not to R2... that is the real question. :)
Enjoy!
Dave
Thanks and this worked for a Power edge 1800, PERC 4/DC as well. Kukan

Issues installing 11g client on windows 2008 R2

Hi I am a windows admin and have been asked to install oracle SQL developer and oracle 11g client on a windows 2008 R2 server.
However it will not work.
After having issues and having to manually set environment variables and creating the folder path network\admin for the ora files, we still get the following issue
"IO Error: The network adapter could not establish the connection"
We have tried both 64 and 32bit versions.
Any help here would be very much appreciated.
Paul.

Thanks for everyones response to this.
First issue was the server we were installing this on is not on the domain and doesnt point to our internal DNS. Hence it couldnt resolve the Host name in the tns file.
I added this to the hosts file, then we had to modify some of the registry entries and path manually.
We were then able to succesfully make a connection.
Paul.

Issue with OBIEE 11.1.1.5.0 Installation on Windows 2008 64-bit machine

Hi
I'm following the below steps to install OBIEE 11.1.1.5.0 Installation on Windows 2008 64-bit machine. However the installation is unsuccessful as it fails at the "Domain Creation" step. It would be very helpful and greatly appreciated if any workaround is provided. Thanks!
1.JRockit Windows 64 bit Version jrockit-jdk1.6.0_24-R28.1.3-4.0.1-windows-x64
2. Oracle 11G Database
3. RCU Installation
4. WebLogic 10.3.5.0 Generic Version
5. Weblogic patch
6. OBIEE 11G 64 bit version (11.1.1.5). Software only
7. Execute Configure.bat in :\Middleware\Oracle_BI1\bin
Thanks

Hi,
Kindly refer my blog link:
http://obieeelegant.blogspot.com/2011/10/windows-7-home-premium-edition-is-not.html
from exp..with obiee11g installation with win 7 64bit i have face so many issues..
http://obieeelegant.blogspot.com/2011/09/obiee-11g-111150-software-only.html
obiee11.1.1.5.0(Software Only Install) windows 7 64bit Installation Error
OBIEE11g software only install configuration get hangover on win 2008 64
==========
Note: some time it works with simple install option then rebooting mechine/restarting mechine it's not working.then i had OWC and discussed with MY Oracle Support team...they confirmed it's not support. please refer the certification matrix excel file in my blog link
Hope it's clear...
Thanks
Deva
Edited by: Devarasu on Nov 25, 2011 11:18 AM

Issue with Installing Oracle 10g R2 on a Windows 2008 Domain Controller

I'm assigned a evaluation task for my company. The task invoke to install oracle in my Domain Controller Server.
I got "ORA-12560: TNS:protocol adapter error" when I installed ORACLE 10g R2 for Win2K8 on my Windows 2008 (a Domain Controller Server). It happened in the create predefined database period.
I tried to google and noted that there are some RUMOS say "We cannot deploy ORACLE on a Domain Controller, It's impossible"
Is this true? Please, Please advise!
Thansk,

This is a link to a same issue
Creating instance oracle 10.2.0.4 on Windows 2008 32bit

Issue with installing password sync on Windows 2008

I have installed pwd sync 64 bit on Windows 2008. Configured it in direct mode (no jms). But when I change the password of a user it is not syncing with the IdM. We have the 32 bit pwd sync working fine on Win 2003. Is there any special steps for installing, configuring 64 bit pwd sync on Win 2008. Thanks. Jack

Hi again Tim-
Given the error "failed to crack URL" I believe you're hitting an issue we have documented as bug # 21999. Here's the jist of it and a possible way around it.
==========
When installing password sync on a Windows 2008 system, if you are not
logged in as 'Administrator', the installer and the configure applications
may be subject to Windows File And Registry Virtualization (FARV). This may
cause the registry entries for password sync to be written to the user portion
of the registry, rather than the system portion. Subsequently, password sync
will fail with the message "failed to crack URL".
To work around FARV, either run the MSI installer from a privileged cmd.exe
prompt, or run the configure.exe application using the "Run As Administrator"
functionality (right-click on the configure.exe application, select "Run As
Administrator").
==========
Hope this helps.
Regards,
Alex

Issue while installing idm 8.1.1 gateway on 64 bit windows 2008 R2

Hi
We have issue in installing idm 8.1.1 gateway on 64 bit windows 2008 R2
C:\Program Files (x86)\IDM\gateway>gateway -i
An error occured while trying to install the service: Input/output error
Sun notes: if you're running 64-bit Windows 2008, you need the JDKTM Version 6 Update 12 and later.
But this java version should be there in Gateway server(windows 2008) or idm installed server?
We don't have java installed on gateway server. is this causing issue?
please let us know
Thanks

I may have found a workaround. Can you try to change the "compatibility mode" in 2008 R2 to "Windows XP SP3" and see if it will install?
Admittedly I have not done this myself so I'm not entirely sure where or how it's done, but I have confirmation it resolves the issue from others who have faced it.
Edited by: user12611524 on May 2, 2011 5:11 PM

Windows 2008 R2 Failover Clustering Issue - The operation returned because the timeout period expired.

I am trying to get a new Windows 2008 R2 cluster to work on two VMware servers (VMware ESXi 5.0.3) and am experiencing some form of timeout issue during the creation of the cluster according to the logs.
All validation checks pass successfully, whether trying to create a single node or dual node cluster, but the same error message is seen when creating the cluster. I have tried various suggestions found but none of them have made a difference. In an effort
to further diagnose the issue I enabled the following diagnostic logs:
- FailoverClustering
- FailoverClustering-Manager
- FailoverClustering-Client
The only useful error I can find is in the FailoverClustering-Client log which reports an error 'Couldn't resolve tcp binding to cluster' for each physical node to be part of the cluster.
In order to further diagnose the cause of the issue, I am looking for any options for increasing logging when attempting to create the cluster. Is there a way to increase the logging to see what the actual timeout is occurring with?
Alex.

Sorry, I should have been more clear ...The servers I am attempting to create a cluster with are Virtual Servers running on a VMware ESXi (5.0.3). They have access to two shared disks (connected to each VM using a separate SCSI Controller from that for the
disk used to install the OS) with Virtual SCSI Bus Sharing set within VMware.
Each Virtual Server has two NICs configured (with static IPs) - one for internal (domain connectivity) and the other for heartbeat connectivity. The servers can ping each other via both interfaces, as expected, but only domain connectivity works via the
internal NIC.
I have tried creating a single node or dual node cluster and get the same error each time. When the cluster is attempting to be created I can see the new computer object is created in Active Directory (which is then deleted when the cluster creation fails)
and I have also tried pre-creating the computer object and specifically setting permissions on it.
When creating the cluster I have tried via the GUI and via PowerShell (both with and without the option to attach the shared storage) but always get the same type of timeout error message. I am hoping there are further debugging options that can be used
to provide a better output as to what the timeout is occurring with.

Windows 2008 R2 Fax Server (Ongoing issue)

I have a Windows 2008 R2 active directory, fax services work inbound through USB modem - have 50 Windows 7 clients connecting to the fax server and outbound faxing works. Here's the issue: After a few days, the clients start getting server disconnected
on the fax clients. When I go to the Server, I restart the fax services, even though no event viewer shows any error's. I do see inbound fax errors of some not received, but these are not consistent when this happens.
I restart the fax services (by restarting print spooler service), and clients still show disconnected. If I remove the account from the Windows 7 Fax client and try to add it back - I get the "You do not have security permissions to complete this
operation. Contact your fax administrator for more information".
Now, I reboot the windows 2008 R2 server and fax services work again inbound and outbound, and I can reconnect the Windows 7 Fax client that I previously removed. UAC is turned off, Domain Admins full control to Fax server permission, and domain users
have fax permissions.
This issue has happened over the last 3 weeks, I've uninstalled Fax roles, and reinstalled many times prior and followed the fax setup step by step on techarticles - like I stated, the fax services work then stop, and rebooting the server allows the faxing
to work again. This server does house Exchange 2010 SP3, but the only thing effected or having issues on this box is Fax services. Any suggestions to look?

Hi ITQ_Jhays,
Please go to Control Panel -> Printers and share the fax printer.
A similar discussion is for your reference:
I can't connect to fax server from client computers.
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows 2008 r2 WSUS port 8530

WINDOWS 2008 R2
new install of WSUS server 3.2.7600.251 want to change the port to 8530 from 80
But when I open command prompt and run wsusutil usecustomport true.....I get error :
C:\Program Files\Update Services\Tools>wsusutil usecustomwebsite true
Fatal Error: Exception has been thrown by the target of an invocation.

Hi,
Did you stop the WSUS service before you change the port?
If no, please try to stop the WSUS service with the command below first:
net stop wsusservice
After change the port, run the command net start wsusservice to start he WSUS service.
Besides, do not forget to change the WSUS GPO settings.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows 2008 R2 NFS setup issues...

Hi all,
Server is a domain controller and is the only server in it's domain.
Windows 2008 Enterprise R2 fully updated and is a new install.
I can only install NFS client not NFS server (only from CLI using Ocsetup, from Server Manager / Roles NFS does not install at all).
Errors logged are:
The Windows component "ServicesForNFS-ServerAndClient;ServerForNFS-Infrastructure;NFS-Administration;ClientForNFS-Infrastructure" could not be configured.
The component installer returned an error: 3017 "The requested operation failed. A system reboot is required to roll back changes made." (Command line: "Ocsetup
ServicesForNFS-ServerAndClient;ServerForNFS-Infrastructure;NFS-Administration;ClientForNFS-Infrastructure")
AND:
Update CoreFileServer of package FileServer-All failed to be turned on. Status: 0x80070bc9.
Update ClientForNFS-Infrastructure of package NFS-Full failed to be turned on. Status: 0x80070bc9.
Update NFS-Administration of package NFS-Full failed to be turned on. Status: 0x80070bc9.
Update ServerForNFS-Infrastructure of package NFS-Full failed to be turned on. Status: 0x80070bc9.
The component setup program encountered an error: 0x643. Fatal error during installation
... anyone had the same experience... really need NFS server installed to use User Name Mapping service!
Thanks.

Hi Lex,
I will try to follow your setup steps and see if I can hit the same issue. Here is what I am going to try
1) New Install of Windows 2008 Enterprise Edition R2
2) Turn on automatic updating and install all updates
3) Install AD Services and promote server to DC (new domain in new forest, functional level Windows 2003)
4) Do you have DNS or any other selection besides this ?
After this I will run
Ocsetup
ServicesForNFS-ServerAndClient;ServerForNFS-Infrastructure;NFS-Administration;ClientForNFS-Infrastructure
I see that you mentioned "really need NFS server installed to use User Name Mapping service!" Are you planning to run User Name Mapping Service on this machine ? User
name mapping service is no longer shipped from Windows 2008 Server onwards.
Thanks,
Frank

Windows 2008 R2 Port Issue

Similar Messages

Maybe you are looking for