|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
We are having an issue with SBS 2003 Premium edition where we can not RDP in to the SBS Box anymore either externally or internally. When it was initally setup this was not an issue and the only things that have changed are any new Microsoft updates that have been installed.
It seems like the SBS Box isn't listening for port 3389 anymore, does anyone have any ideas as to what the issue might be or anything to try and troubleshoot the problem?
We have no issues connecting to any of the other 4 Servers through the RWW.
Thanks in advance
|
|
I forgot to mention the error report the ISA Server is giving when we try to establish a connection:
A connection was abortively closed after one of the peers sent a RST segement.
Not sure if this helps, please let me know if you require anymore information?
"Brent C" wrote:
[Quoted Text] > We are having an issue with SBS 2003 Premium edition where we can not RDP in > to the SBS Box anymore either externally or internally. When it was initally > setup this was not an issue and the only things that have changed are any new > Microsoft updates that have been installed. > > It seems like the SBS Box isn't listening for port 3389 anymore, does anyone > have any ideas as to what the issue might be or anything to try and > troubleshoot the problem? > > We have no issues connecting to any of the other 4 Servers through the RWW. > > Thanks in advance
|
|
Brent,
Try logging on to the console (from the server itself) and re-applying Windows Server 2003 SP2. To check to see if it is listening you can use netstat -aon | find ":3389"
--
Hope that helps, David Copeland Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Newsgroups: SBS v4.x : microsoft.public.backoffice.smallbiz SBS 2000: microsoft.public.backoffice.smallbiz2000 SBS 2003: microsoft.public.windows.server.sbs "Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message news:0ABA0099-C728-4DAC-9C89-EF218135A359[ at ]microsoft.com...
[Quoted Text] >I forgot to mention the error report the ISA Server is giving when we try >to > establish a connection: > > A connection was abortively closed after one of the peers sent a RST > segement. > > Not sure if this helps, please let me know if you require anymore > information? > > > > "Brent C" wrote: > >> We are having an issue with SBS 2003 Premium edition where we can not RDP >> in >> to the SBS Box anymore either externally or internally. When it was >> initally >> setup this was not an issue and the only things that have changed are any >> new >> Microsoft updates that have been installed. >> >> It seems like the SBS Box isn't listening for port 3389 anymore, does >> anyone >> have any ideas as to what the issue might be or anything to try and >> troubleshoot the problem? >> >> We have no issues connecting to any of the other 4 Servers through the >> RWW. >> >> Thanks in advance
|
|
David,
I have previously tried the netstat command and it is not listening for 3389. I will try re-applying SP2.
Thanks
"David Copeland [MSFT]" wrote:
[Quoted Text] > Brent, > > Try logging on to the console (from the server itself) and re-applying > Windows Server 2003 SP2. To check to see if it is listening you can use > netstat -aon | find ":3389" > > -- > > Hope that helps, > David Copeland > Microsoft Small Business Server Support > > This posting is provided "AS IS" with no warranties, and confers no rights. > > Newsgroups: > SBS v4.x : microsoft.public.backoffice.smallbiz > SBS 2000: microsoft.public.backoffice.smallbiz2000 > SBS 2003: microsoft.public.windows.server.sbs > "Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message > news:0ABA0099-C728-4DAC-9C89-EF218135A359[ at ]microsoft.com... > >I forgot to mention the error report the ISA Server is giving when we try > >to > > establish a connection: > > > > A connection was abortively closed after one of the peers sent a RST > > segement. > > > > Not sure if this helps, please let me know if you require anymore > > information? > > > > > > > > "Brent C" wrote: > > > >> We are having an issue with SBS 2003 Premium edition where we can not RDP > >> in > >> to the SBS Box anymore either externally or internally. When it was > >> initally > >> setup this was not an issue and the only things that have changed are any > >> new > >> Microsoft updates that have been installed. > >> > >> It seems like the SBS Box isn't listening for port 3389 anymore, does > >> anyone > >> have any ideas as to what the issue might be or anything to try and > >> troubleshoot the problem? > >> > >> We have no issues connecting to any of the other 4 Servers through the > >> RWW. > >> > >> Thanks in advance > >
|
|
Susan recently hit a similar thing where the TS service was not listening on 3389.
ends up the RDP 'device' was the culprit, not sure of the solution. Maybe David can assist.
devmgr. show non present and show hidden, RDPNP was disabled or broken, _I think_.
"Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message news:70321B35-10B7-4707-9BA0-BA919B5C565E[ at ]microsoft.com...
[Quoted Text] > David, > > I have previously tried the netstat command and it is not listening for > 3389. I will try re-applying SP2. > > Thanks > > "David Copeland [MSFT]" wrote: > >> Brent, >> >> Try logging on to the console (from the server itself) and re-applying >> Windows Server 2003 SP2. To check to see if it is listening you can use >> netstat -aon | find ":3389" >> >> -- >> >> Hope that helps, >> David Copeland >> Microsoft Small Business Server Support >> >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> Newsgroups: >> SBS v4.x : microsoft.public.backoffice.smallbiz >> SBS 2000: microsoft.public.backoffice.smallbiz2000 >> SBS 2003: microsoft.public.windows.server.sbs >> "Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message >> news:0ABA0099-C728-4DAC-9C89-EF218135A359[ at ]microsoft.com... >> >I forgot to mention the error report the ISA Server is giving when we >> >try >> >to >> > establish a connection: >> > >> > A connection was abortively closed after one of the peers sent a RST >> > segement. >> > >> > Not sure if this helps, please let me know if you require anymore >> > information? >> > >> > >> > >> > "Brent C" wrote: >> > >> >> We are having an issue with SBS 2003 Premium edition where we can not >> >> RDP >> >> in >> >> to the SBS Box anymore either externally or internally. When it was >> >> initally >> >> setup this was not an issue and the only things that have changed are >> >> any >> >> new >> >> Microsoft updates that have been installed. >> >> >> >> It seems like the SBS Box isn't listening for port 3389 anymore, does >> >> anyone >> >> have any ideas as to what the issue might be or anything to try and >> >> troubleshoot the problem? >> >> >> >> We have no issues connecting to any of the other 4 Servers through the >> >> RWW. >> >> >> >> Thanks in advance >> >>
|
|
Susan recently hit a similar thing where the TS service was not listening on 3389.
ends up the RDP 'device' was the culprit, not sure of the solution. Maybe David can assist.
devmgr. show non present and show hidden, RDPNP was disabled or broken, _I think_.
"Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message news:70321B35-10B7-4707-9BA0-BA919B5C565E[ at ]microsoft.com...
[Quoted Text] > David, > > I have previously tried the netstat command and it is not listening for > 3389. I will try re-applying SP2. > > Thanks > > "David Copeland [MSFT]" wrote: > >> Brent, >> >> Try logging on to the console (from the server itself) and re-applying >> Windows Server 2003 SP2. To check to see if it is listening you can use >> netstat -aon | find ":3389" >> >> -- >> >> Hope that helps, >> David Copeland >> Microsoft Small Business Server Support >> >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> Newsgroups: >> SBS v4.x : microsoft.public.backoffice.smallbiz >> SBS 2000: microsoft.public.backoffice.smallbiz2000 >> SBS 2003: microsoft.public.windows.server.sbs >> "Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message >> news:0ABA0099-C728-4DAC-9C89-EF218135A359[ at ]microsoft.com... >> >I forgot to mention the error report the ISA Server is giving when we >> >try >> >to >> > establish a connection: >> > >> > A connection was abortively closed after one of the peers sent a RST >> > segement. >> > >> > Not sure if this helps, please let me know if you require anymore >> > information? >> > >> > >> > >> > "Brent C" wrote: >> > >> >> We are having an issue with SBS 2003 Premium edition where we can not >> >> RDP >> >> in >> >> to the SBS Box anymore either externally or internally. When it was >> >> initally >> >> setup this was not an issue and the only things that have changed are >> >> any >> >> new >> >> Microsoft updates that have been installed. >> >> >> >> It seems like the SBS Box isn't listening for port 3389 anymore, does >> >> anyone >> >> have any ideas as to what the issue might be or anything to try and >> >> troubleshoot the problem? >> >> >> >> We have no issues connecting to any of the other 4 Servers through the >> >> RWW. >> >> >> >> Thanks in advance >> >>
|
|
http://msmvps.com/blogs/bradley/archive/2007/05/07/back-to-rdping-to-my-server.aspx
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/16b3ce0417f39445/5dd8111968e07a02?lnk=st&q=terminal+server+device+redirector&rnum=4#5dd8111968e07a02
Read that thread. Prior to all that, I had disabled the RSS and offloading, I had up'd the NIC drivers and I STILL lost RDP to the server. In the driver section that one driver had a "!" and had to be reinstalled from the cab folder.
If it's not that, CALL Product support services as issues like this with SP2 are a free call.
-- http://www.sbslinks.com/really.htm
"SuperGumby [SBS MVP]" wrote:
[Quoted Text] > Susan recently hit a similar thing where the TS service was not listening on > 3389. > > ends up the RDP 'device' was the culprit, not sure of the solution. Maybe > David can assist. > > devmgr. show non present and show hidden, RDPNP was disabled or broken, _I > think_. > > "Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message > news:70321B35-10B7-4707-9BA0-BA919B5C565E[ at ]microsoft.com... > > David, > > > > I have previously tried the netstat command and it is not listening for > > 3389. I will try re-applying SP2. > > > > Thanks > > > > "David Copeland [MSFT]" wrote: > > > >> Brent, > >> > >> Try logging on to the console (from the server itself) and re-applying > >> Windows Server 2003 SP2. To check to see if it is listening you can use > >> netstat -aon | find ":3389" > >> > >> -- > >> > >> Hope that helps, > >> David Copeland > >> Microsoft Small Business Server Support > >> > >> This posting is provided "AS IS" with no warranties, and confers no > >> rights. > >> > >> Newsgroups: > >> SBS v4.x : microsoft.public.backoffice.smallbiz > >> SBS 2000: microsoft.public.backoffice.smallbiz2000 > >> SBS 2003: microsoft.public.windows.server.sbs > >> "Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message > >> news:0ABA0099-C728-4DAC-9C89-EF218135A359[ at ]microsoft.com... > >> >I forgot to mention the error report the ISA Server is giving when we > >> >try > >> >to > >> > establish a connection: > >> > > >> > A connection was abortively closed after one of the peers sent a RST > >> > segement. > >> > > >> > Not sure if this helps, please let me know if you require anymore > >> > information? > >> > > >> > > >> > > >> > "Brent C" wrote: > >> > > >> >> We are having an issue with SBS 2003 Premium edition where we can not > >> >> RDP > >> >> in > >> >> to the SBS Box anymore either externally or internally. When it was > >> >> initally > >> >> setup this was not an issue and the only things that have changed are > >> >> any > >> >> new > >> >> Microsoft updates that have been installed. > >> >> > >> >> It seems like the SBS Box isn't listening for port 3389 anymore, does > >> >> anyone > >> >> have any ideas as to what the issue might be or anything to try and > >> >> troubleshoot the problem? > >> >> > >> >> We have no issues connecting to any of the other 4 Servers through the > >> >> RWW. > >> >> > >> >> Thanks in advance > >> > >> > > >
|
|
I have tried all the suggestions listed and none of them have fixed the problem. I tried reinstalling SP2, removing SP2 and then reinstalling SP2 again without any luck. Between each instance of uninstall/reinstall I tested RDP and no luck still.
I have checked the drivers under device manager and all are ok. Tried updating the NIC Drivers etc.
I don't know if this is specifically a problem with SP2, does anyone else have anyother suggestions? I am starting to get pretty frustrated here so anything I can try is appreciated. It is a pain as well because each time I have to try something I have to drive 1.5 hours each way to test and then drive back without a resolution.
"SuperGumby [SBS MVP]" wrote:
[Quoted Text] > Susan recently hit a similar thing where the TS service was not listening on > 3389. > > ends up the RDP 'device' was the culprit, not sure of the solution. Maybe > David can assist. > > devmgr. show non present and show hidden, RDPNP was disabled or broken, _I > think_. > > "Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message > news:70321B35-10B7-4707-9BA0-BA919B5C565E[ at ]microsoft.com... > > David, > > > > I have previously tried the netstat command and it is not listening for > > 3389. I will try re-applying SP2. > > > > Thanks > > > > "David Copeland [MSFT]" wrote: > > > >> Brent, > >> > >> Try logging on to the console (from the server itself) and re-applying > >> Windows Server 2003 SP2. To check to see if it is listening you can use > >> netstat -aon | find ":3389" > >> > >> -- > >> > >> Hope that helps, > >> David Copeland > >> Microsoft Small Business Server Support > >> > >> This posting is provided "AS IS" with no warranties, and confers no > >> rights. > >> > >> Newsgroups: > >> SBS v4.x : microsoft.public.backoffice.smallbiz > >> SBS 2000: microsoft.public.backoffice.smallbiz2000 > >> SBS 2003: microsoft.public.windows.server.sbs > >> "Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message > >> news:0ABA0099-C728-4DAC-9C89-EF218135A359[ at ]microsoft.com... > >> >I forgot to mention the error report the ISA Server is giving when we > >> >try > >> >to > >> > establish a connection: > >> > > >> > A connection was abortively closed after one of the peers sent a RST > >> > segement. > >> > > >> > Not sure if this helps, please let me know if you require anymore > >> > information? > >> > > >> > > >> > > >> > "Brent C" wrote: > >> > > >> >> We are having an issue with SBS 2003 Premium edition where we can not > >> >> RDP > >> >> in > >> >> to the SBS Box anymore either externally or internally. When it was > >> >> initally > >> >> setup this was not an issue and the only things that have changed are > >> >> any > >> >> new > >> >> Microsoft updates that have been installed. > >> >> > >> >> It seems like the SBS Box isn't listening for port 3389 anymore, does > >> >> anyone > >> >> have any ideas as to what the issue might be or anything to try and > >> >> troubleshoot the problem? > >> >> > >> >> We have no issues connecting to any of the other 4 Servers through the > >> >> RWW. > >> >> > >> >> Thanks in advance > >> > >> > > > >
|
|
You missed my earlier email.
And you forgot to call PSS support.
-------------------
http://msmvps.com/blogs/bradley/archive/2007/05/07/back-to-rdping-to-my-server.aspx
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/16b3ce0417f39445/5dd8111968e07a02?lnk=st&q=terminal+server+device+redirector&rnum=4#5dd8111968e07a02
Read that thread. Prior to all that, I had disabled the RSS and offloading, I had up'd the NIC drivers and I STILL lost RDP to the server. In the driver section that one driver had a "!" and had to be reinstalled from the cab folder.
If it's not that, CALL Product support services as issues like this with SP2 are a free call.
Brent C wrote:
[Quoted Text] > I have tried all the suggestions listed and none of them have fixed the > problem. I tried reinstalling SP2, removing SP2 and then reinstalling SP2 > again without any luck. Between each instance of uninstall/reinstall I tested > RDP and no luck still. > > I have checked the drivers under device manager and all are ok. Tried > updating the NIC Drivers etc. > > I don't know if this is specifically a problem with SP2, does anyone else > have anyother suggestions? I am starting to get pretty frustrated here so > anything I can try is appreciated. It is a pain as well because each time I > have to try something I have to drive 1.5 hours each way to test and then > drive back without a resolution. > > "SuperGumby [SBS MVP]" wrote: > >> Susan recently hit a similar thing where the TS service was not listening on >> 3389. >> >> ends up the RDP 'device' was the culprit, not sure of the solution. Maybe >> David can assist. >> >> devmgr. show non present and show hidden, RDPNP was disabled or broken, _I >> think_. >> >> "Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message >> news:70321B35-10B7-4707-9BA0-BA919B5C565E[ at ]microsoft.com... >>> David, >>> >>> I have previously tried the netstat command and it is not listening for >>> 3389. I will try re-applying SP2. >>> >>> Thanks >>> >>> "David Copeland [MSFT]" wrote: >>> >>>> Brent, >>>> >>>> Try logging on to the console (from the server itself) and re-applying >>>> Windows Server 2003 SP2. To check to see if it is listening you can use >>>> netstat -aon | find ":3389" >>>> >>>> -- >>>> >>>> Hope that helps, >>>> David Copeland >>>> Microsoft Small Business Server Support >>>> >>>> This posting is provided "AS IS" with no warranties, and confers no >>>> rights. >>>> >>>> Newsgroups: >>>> SBS v4.x : microsoft.public.backoffice.smallbiz >>>> SBS 2000: microsoft.public.backoffice.smallbiz2000 >>>> SBS 2003: microsoft.public.windows.server.sbs >>>> "Brent C" <BrentC[ at ]discussions.microsoft.com> wrote in message >>>> news:0ABA0099-C728-4DAC-9C89-EF218135A359[ at ]microsoft.com... >>>>> I forgot to mention the error report the ISA Server is giving when we >>>>> try >>>>> to >>>>> establish a connection: >>>>> >>>>> A connection was abortively closed after one of the peers sent a RST >>>>> segement. >>>>> >>>>> Not sure if this helps, please let me know if you require anymore >>>>> information? >>>>> >>>>> >>>>> >>>>> "Brent C" wrote: >>>>> >>>>>> We are having an issue with SBS 2003 Premium edition where we can not >>>>>> RDP >>>>>> in >>>>>> to the SBS Box anymore either externally or internally. When it was >>>>>> initally >>>>>> setup this was not an issue and the only things that have changed are >>>>>> any >>>>>> new >>>>>> Microsoft updates that have been installed. >>>>>> >>>>>> It seems like the SBS Box isn't listening for port 3389 anymore, does >>>>>> anyone >>>>>> have any ideas as to what the issue might be or anything to try and >>>>>> troubleshoot the problem? >>>>>> >>>>>> We have no issues connecting to any of the other 4 Servers through the >>>>>> RWW. >>>>>> >>>>>> Thanks in advance >>>> >> >> >>
|
|
Has anyone managed to fix this problem? I am having exact same thing on SBS 2003 R2. Difference with mine is that SP2 was already on the box and RDP was working fine for a week. Then overnight RDP is not working, nestat find :3389 just returns to the command prompt so RDP is not listening, I have checked terminal service is running, remote desktop is enabled, rdp connection in TS manager is active and says its listening, port number in the registry is correct.
Only thing I can think of that changed is that we installed Mcafee Groupshield but I have since uninstalled that and problem still occurs.
I have followed suggestions on here, checked for the driver in Device Manager (with show hidden items) and reapplied SP2 but still not working.
Any other pointers would be greatly appreciated as this is driving me mad!
Regards
Paddy
"Brent C" wrote:
[Quoted Text] > We are having an issue with SBS 2003 Premium edition where we can not RDP in > to the SBS Box anymore either externally or internally. When it was initally > setup this was not an issue and the only things that have changed are any new > Microsoft updates that have been installed. > > It seems like the SBS Box isn't listening for port 3389 anymore, does anyone > have any ideas as to what the issue might be or anything to try and > troubleshoot the problem? > > We have no issues connecting to any of the other 4 Servers through the RWW. > > Thanks in advance
|
|
|