Routing and Remote Access issue on Windows 2008 R2

-

i have been experiencing difficulty in getting more 1 demand-dial connection work on windows 2008 r2 server configured routing , remote access. can make 1 connection rras server (resource) rras server (clienta) on nat establish pptp tunnel. when attempt bring rras connection different rras server (clientb) fails. have tried both ipv4 address assignments dhcp , static address pools on both rras configurations no change in failing connect clientb rras server. both connections setup same (vpn, pptp, require encryption, persistent connection, etc).

the errors when connection fails is:

log name:      application
source:        rasclient
date:          10/12/2012 4:45:40 pm
event id:      20227
task category: none
level:         error
keywords:      classic
user:          n/a
computer:      infr-pras-301.fim.sync
description:
coid={b8613d55-80f9-4599-ba95-4d299d23ac77}: user system dialed connection named clientb has failed. error code returned on failure 720.

log name:      system
source:        remoteaccess
date:          10/12/2012 4:45:40 pm
event id:      20111
task category: none
level:         error
keywords:      classic
user:          n/a
computer:      infr-pras-301.fim.sync
description:
demand dial connection remote interface clientb on port vpn3-3 initiated failed complete because of  following error: connection remote computer not established.  you might need change network settings connection.

any ideas on may causing , how correct it?

the goal here have 1 central rras sever hosting mutliple demand dial connections. 

thanks :)

hi,

thank post.

i suggest test dial branch office main office or use different dedicated isp nat ip address main office each vpn connection.
http://social.technet.microsoft.com/forums/en-us/winservernis/thread/213d2658-b987-4b5e-9b17-078ab5366737

if there more inquiries on issue, please feel free let know.

regards,
rick tan
technet subscriber support
if technet subscription user , have feedback on our support quality, please send feedbackhere.

rick tan

technet community support



Windows Server  >  Platform Networking



Comments

Post a Comment

Popular posts from this blog

DCOM received error "2147746132" from...

-
hi everybody, i have dc (my windows essentials 2012 server) , windows 2012 server in network.  the windows server 2012 inside domain. on server, got "non stopping" error says in event logs : ===> dcom received error "2147746132" fromd computer xxxx(my dc computer) while server trying activation : {6df8cb71-153b-4c66-8fc4-e59301b8011b} it never stops, got 11000+ new events :s i found : http://support.microsoft.com/kb/971153/fr i'm not sure should ? does got idea ? matthieu. hi, please try solution mentioned in below link: http://www.eventid.net/display-eventid-10006-source-dcom-eventno-272-phase-1.htm regards, cicely Windows Server  >  Windows Server 2012 General ...
Read more

DFSR RPC replication errors 5014 1726 with large files over VPN

-
i have similar issue ryan in reply http://social.technet.microsoft.com/forums/en-gb/winserverfiles/thread/6d49fd71-2236-4fcb-9763-bf1c03459ee8 cited below. start additional thread here because other 1 related windows server 2003 (r2) , i'm (as ryan) on windows 2008 r2 x64. here first of post ryan: i've got same problem on 2008 r2 dfsr server.  the spoke server has 2x intel 1 gigb on-board nics in active/standby teamed configuration. the hub server (running on vmware using 10gbit vmnet3 nic driver) logs dfsr event 5014 every 2-15mins (usually around 5mins). the spoke server not log event. replication running slowly. initial sync/replication. had re-configure replication folder because of lost dfsr database on spoke server.  could teamed nic on spoke causing error on host? a note: last time did initial sync on folder processed @ 30k files , hour. time it's doing few hundred and hour. another note: hub server has several replication groups , conne...
Read more

ADFS 3.0 Event ID 4625 | An Error occurred During Logon | Status: 0xC000035B

-
we're getting these random errors on our adfs security logs, how can track down generating them? an account failed log on. subject: security id: null sid account name: - account domain: - logon id: 0x0 logon type: 3 account logon failed: security id: null sid account name: account domain: failure information: failure reason: an error occured during logon. status: 0xc000035b sub status: 0x0 process information: caller process id: 0x0 caller process name: - network information: workstation name: - source network address: - source port: - detailed authentication information: logon process: kerberos authentication package: kerberos transited services: - package name (ntlm only): - key length: 0 event generated when logon request fails. generated on computer access attempted. subject fields indicate account on local system requested logon. commonly service such server service, or local process such ...
Read more