|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (7 bit)
Join Date: May 2003
Posts: 99
|
VPN Server
I setup my 2000 Server as a VPN Server, I currently use a static mapping scheme with 4 clients, after I configured the VPN server I tested the connection on a client machine (within my LAN) using the 192.168.1.x address assinged to that machine, and it connected without a hitch and obviously assinged that machine a different static IP, I have setup the VPN server to assign static IP's when someone connects....My question is will this cause any problems when I connect to the VPN server within my LAN (For test purposes)...I mean the client already has a 192.168.1.x address and then recieves another when it connects to the VPN server. I hope this makes sense to you all!!!
|
|
|
|
|
|
#2 |
|
Member (7 bit)
Join Date: May 2003
Posts: 99
|
I should mention that the VPN Server is also the DC/DNS server, I got the following errors on the Event Viwer under the DNS tab.
Event Type: Error Event Source: DNS Event Category: None Event ID: 6702 Date: 1/8/2004 Time: 1:02:08 PM User: N/A Computer: Description: DNS Server has updated its own host (A) records. In order to insure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code. If this DNS server does not have any DS-integrated peers, then this error should be ignored. If this DNS server's ActiveDirectory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it. To insure proper replication: 1) Find this server's ActiveDirectory replication partners that run the DNS server. 2) Open DnsManager and connect in turn to each of the replication partners. 3) On each server, check the host (A record) registration for THIS server. 4) Delete any A records that do NOT correspond to IP addresses of this server. 5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the ActiveDirectory DNS server you are updating.) 6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data. Data: 0000: 2d 23 00 00 -#.. Event Type: Error Event Source: DNS Event Category: None Event ID: 7063 Date: 1/8/2004 Time: 1:01:48 PM User: N/A Computer: Description: The DNS server is configured to forward to a non-recursive DNS server at 65.xxx.x.x DNS servers in forwarders list MUST be configured to process recursive queries. Either 1) fix the forwarder (65.xxx.x.x) to allow recursion - connect to it with DNS Manager - bring up server properties - open "Advanced" tab - uncheck "Disable Recursion" - click OK OR 2) remove this forwarder from this servers forwarders list - DNS Manager - bring up server properties - open "Forwarders" tab - remove (65.xxx.x.x) from list of forwarders - click OK |
|
|
|
|
|
#3 |
|
Member (11 bit)
|
Yeow, you are a few gazillion LAN parties ahead of me, dude!
|
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|