2k3 domain, dns entry keeps getting created for PDC - 192.168.234.235 (wrong range, s/b 192.168.0.XXX)

WINDOWS SERVER

    Next

  • 1. User Export
    Dear All, Sorry actually I had asked howto backup the User Account and password on yesterday and thank you for the solution before. However, I want to know if I can export the standalone server User Account and password from one server to another? Thx. Eric
  • 2. 4GB Memory for Server 2003 Standard
    Hi - I recently installed 4GB of RAM on my Dell Optiplex GX280 (maxing it out). Under XP, the OS only recognized 2.99GB of RAM. After poking around the Internet, I did a clean install of Server 2003 Standard. Still 2.99GB. I am contemplating going to Enterprise Edition, but I am not sure that will solve the problem. Dell support has been no help. The BIOS sees all of the RAM. Does Standard Edition should support all 4GB? Do I need the /3GB switches in boot.ini? (/3GB is specifically not recommended for the app I want to run but just asking. Also, I tried the /PAE switch. No love.) Any thoughts on why the OS is not seeing all of this? Thanks.
  • 3. Can not locate DHCP server
    I have a location using a pix 501 router and vpn setup with dhcp relay. All but one of the XP SP2 workstations can get an ip number. This workstation at one time could get to the dhcp server but it now fails. I have added a static IP number and it can ping the dhcp server and the workstation is in DNS. There are no errors in the dhcp log file for this workstation, and I check in the userenv.log and found nothing. I was wondering how I can get more debugging info on the dhcp server or workstation, or maybe someone might have another suggestion.
  • 4. VPN Remote Desktop Connection Problem
    I can remote desktop to the 2003 server however I cannot RD to any other machines on the network. (When I RD to the server it takes quite a while to connect.) Once I connect to the VPN I can ping all remote systems, when I ping them by name it takes much longer to resolve to the ip address. I cannot telnet to the machine (by ip) to on port 3389. Also when I try to RD to the 2003 server by specifying its ip address it will connect only when I use the servers name. I have tried everything that I can think of at this point.
  • 5. Administrator Desktop missing (background only) on local logon...
    A strange problem has started to occur frequently on on Windows 2003 Server (which is domain controller). Occasionally, when try to logon locally to DC, I am able to logon but all I see is the desktop background and no icons, no start menu, etc. The server is still operational... desktop just seems to be hung/missing. Sometimes I can press CTRL-ALT-DEL to logoff... but same problem occurs on logon... and sometimes I restart server this way to get the desktop back. Lately, the desktop has gone "missing" and CTRL-ALT-DEL shows nothing and I can't access anything, logoff, do a proper shutdown, etc.. In these cases I am forced to power off and re-start the domain controller cold... I don't like doing this. Funnily enough, Windows 2003 server is accessible using Remote Desktop and all icons/desktop show up, when you can NOT logon to server locally. Yes, I have tried SHUTDOWN from remote desktop but after connection is terminated from server, the server just stays up with the blank desktop. ANy ideas as to how to diagnose further and/or resolve? Server is running latest security/updates... ....grant -- Grant Leclerc Unionville Alliance Church (UAC)

2k3 domain, dns entry keeps getting created for PDC - 192.168.234.235 (wrong range, s/b 192.168.0.XXX)

Postby Tim Watts » Fri, 06 May 2005 06:12:12 GMT

I have been having dns issues with my domain, PDC is win2k3, other domain 
controllers are also 2k3.

The PDC is pointed at itself only for dns. Both of the other DC's are 
pointed first at the PDC, then at one of the other DC's. Recently I have 
been experiencing issues from some of the other servers in our network 
having difficulties finding the PDC. Started looking around in the host 
records in DNS, and found that the PDC has an entry for 192.168.234.235 
(Which is not correct, S/B 192.168.0.XXX) There is also an entry for the 
correct IP address. I deleted the incorrect address, and immediately the 
server that was having a hard time finding the PDC could find the PDC (after 
I had cleared the dns cache on the other member server)

The incorrect record keeps getting created. Can anyone shed some light on 
this, it is driving me crazy!

I'm not sure if it is the PDC, or one of the other DC's that keeps creating 
the incorrect record.

Thanks in advance.

Tim 



Similar Threads:

1.Ping 192.168.1.101 but the response is 192.168.1.107

Dear Folks,

I had bought a new Canon PIXMA MP 628 printer and it works well with my 
tablet PC running Vista Home Premium.

However, I am having difficulties to enable it to work on my another 
notebook, which is running Vista Home Premium as well.

Initially, I thought that it could be the printer drivers problem and thus, 
I reinstalled all printer drivers but alas, no effect. When I went to the 
command prompt and ping "192.168.1.101" [IP address of the printer], the 
response "Reply from 192.168.1.107 Destination Host Unreachable"

Could somebody help me on this? 

2.My PCs 192.168.4.0 subnet querying the logon server in 192.168.5.0

3.Please read "168.192.0.1" as "192.168.0.1"

Oops, memorised it wrongly when writing that message.


4.Routing Linux 192.168.10.x network to Dlink router on 192.168.1.x network

8/5/2006, 1:23AM

Hi,

Thanks for taking the time to shine some light!

I have a Linux Redhat 7.2 box on a 192.168.10.x  network and I have
clients that need to connect also connected to the same Dlink router
which is at 192.168.1.1

All my boxes are physically plugged into the D-link router so they are
all on the same physical network.

I heard that if all machines are on the same router, then all one has
to do is add the odd man out network to the routing page, which I did:


Enable : Yes
Destination IP 192.168.10.100
Netmask : 255.255.255.0
Gateway : 192.168.1.1
Interface :LAN
Metric :  1

My router is on 192.168.1.1
Linux box is on 192.168.10.100
clients on 192.168.1.100

I don't want to be sloppy and change the subnet mask to 255.255.0.0

Shouldn't this work? But my Linux box at 192.168.10.100 can't ping my
D-link router at 192.168.1.1

I could probably do a "route add" command on the Linux box to be able
to ping the D-link, but shouldn't the router, since it's on the same
physical network, see the ping from anything on it's network? Yes...it
should drop it from a different subnet...I know....but since I added
the route in the D-link routing table, shouldn't it not only see it but
route it and/or respond to it?

I can ping the D-link 192.168.1.1 from my boxes on the 192.168.1.x
network.

I don't want to have to add "route print" statements on all my boxes. I
thought this is what routers were for...connecting different subnets?

Thanks for your input!

Thanks,

The "Route Guy"

5.Routing Linux 192.168.10.x network to Dlink router on 192.168.1.x network

Hi Robert,

Thanks for the reply!

The reason I don't let DHCP do it's dirty deeds is that most of my
boxes are servers or other test clients whose addresses I need to stay
static.

So, opening up my subnet mask is one solution, but in situations where
widening the subnetmask is not desired, shouldn't my router be able to
"route" from one subnet to the other?

I want my 192.168.10.100 to be able to send packets through 192.168.1.1
(The D-link router) to get to 192.168.1.104 and other 192.168.1.x
clients.

Can't I get the D-link to route this way without just opening my subnet
mask?

And does this mean I have to open the subnet mask on all clients and
servers? The reason I ask is that, again, I've read that the router
should be able to handle all of this without changing the clients as
long as they are all plugged into the same router, because the router
gets all the packets, but makes decisions about which to route based on
it's own configured routing table.

I thought I modified the routing table sufficiently with my
> > Enable : Yes
> > Destination IP 192.168.10.100
> > Netmask : 255.255.255.0
> > Gateway : 192.168.1.1
> > Interface :LAN
> > Metric :  1

entry...but apparently not.

Any direction on how to get the router to route without widening the
subnet mask is appreciated!

Sincerely,

RG


Robert Harris wrote:
> q4n wrote:
> > 8/5/2006, 1:23AM
> >
> > Hi,
> >
> > Thanks for taking the time to shine some light!
> >
> > I have a Linux Redhat 7.2 box on a 192.168.10.x  network and I have
> > clients that need to connect also connected to the same Dlink router
> > which is at 192.168.1.1
> >
> > All my boxes are physically plugged into the D-link router so they are
> > all on the same physical network.
> >
> > I heard that if all machines are on the same router, then all one has
> > to do is add the odd man out network to the routing page, which I did:
> >
> >
> > Enable : Yes
> > Destination IP 192.168.10.100
> > Netmask : 255.255.255.0
> > Gateway : 192.168.1.1
> > Interface :LAN
> > Metric :  1
> That would mean that packets for 192.168.10.100 are to be sent to
> 192.168.1.1 which probably isn't what you want.
>
> If your 192.168.1.x and 192.168.10.x are on the same subnet, and there
> aren't any othe 192.168.y.x on different subnets, then setting the
> subnet mask to 255.255.0.0 is what you need to to.
>
> But why doesn't your Linux box have a 192.168.1.x address anyway? Why
> don't you just let your router assign its IP address like everybody else's?
>
> Robert
>
> >
> > My router is on 192.168.1.1
> > Linux box is on 192.168.10.100
> > clients on 192.168.1.100
> >
> > I don't want to be sloppy and change the subnet mask to 255.255.0.0
> > 
> > [snip]

6. 192.168.xxx.xxx "unreachable"?????

7. can't find server name for 192.168.100.xxx/unknown server

8. Is there an Internet Connection Sharing system that doesn't use the 192.168.0.x range



Return to WINDOWS SERVER

 

Who is online

Users browsing this forum: No registered users and 90 guest