• February 28, 2025, 01:38:46 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Configuration Information  (Read 5005 times)

myfriend12

  • Level 1 Member
  • *
  • Posts: 4
Configuration Information
« on: June 09, 2010, 12:47:07 AM »

Hi,

I am having a huge problem that is frustrating me.  I have a DNS 323 configured with a static IP.  Every computer works except for one which gives me the error "Configuration information could not be read for the domain controller, either because the machine is unavailable, or access has been denied".  I know the machine is there because I can still access it from other computers and I can access it over FTP.  I have looked through all of the computer settings and they all look the same.  Also, if I change the DNS to have a dynamic IP address, it works on all computers.  However due to the FTP I do not want it dynamic.

Thoughts?

Please help
Logged

fordem

  • Level 10 Member
  • *****
  • Posts: 2168
Re: Configuration Information
« Reply #1 on: June 09, 2010, 05:24:56 AM »

Based on the error message provided - it would appear that the computer in question is configured to participate in a Windows AD domain - and is being used away from that domain - perhaps this is a company issue laptop, being used at home.

If this is the case then you may need to login to the system with a stand alone user rather than a domain user to get around this error - if company policies permit.

With regard the static & dynamic addressing - you could consider using a DHCP reservation rather than a static ip address - as long as the NAS is connected to the same DHCP server, it will be given the reserved address so that the end result is effectively the same as a static address.
Logged
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.

myfriend12

  • Level 1 Member
  • *
  • Posts: 4
Re: Configuration Information
« Reply #2 on: June 09, 2010, 07:53:57 AM »

Based on the error message provided - it would appear that the computer in question is configured to participate in a Windows AD domain - and is being used away from that domain - perhaps this is a company issue laptop, being used at home.

If this is the case then you may need to login to the system with a stand alone user rather than a domain user to get around this error - if company policies permit.

With regard the static & dynamic addressing - you could consider using a DHCP reservation rather than a static ip address - as long as the NAS is connected to the same DHCP server, it will be given the reserved address so that the end result is effectively the same as a static address.

Hi,

The computer is a desktop that I setup that is in one of our offices.  I built our entire network from scratch so this is why I am so confused. 

Also, this happens on all accounts on the computer, not just one.

The NAS is the only storage unit on the network and the computers run seperately.  There is no server for the computers to log into.  I will look into the DHCP reservation.

Any other suggestions?

Thanks
Logged

Buhric

  • Level 3 Member
  • ***
  • Posts: 191
Re: Configuration Information
« Reply #3 on: June 10, 2010, 04:49:34 AM »

Like fordem said... looks like that computer is setup for a domain... and not a workgroup....
since its a computer setting... it will give out the same error, no matter what user is logged in....
Logged

myfriend12

  • Level 1 Member
  • *
  • Posts: 4
Re: Configuration Information
« Reply #4 on: June 10, 2010, 07:13:17 PM »

Like fordem said... looks like that computer is setup for a domain... and not a workgroup....
since its a computer setting... it will give out the same error, no matter what user is logged in....


I looked that up and it said that it was part of our network WORKGROUP
Logged

myfriend12

  • Level 1 Member
  • *
  • Posts: 4
Re: Configuration Information
« Reply #5 on: June 10, 2010, 07:34:25 PM »

Never mind, I figured it out.  I went into the network and changed the name of the computer, restarted and it worked.

Thanks for the help.
Logged