loging to long

0 pts.
Tags:
Availability
Cabling
Hardware
Hubs
Network management software
Networking
Routers
Switches
we have a winserver 2003 we use a 16ports vpn linksys router switch, but the autentication period is to long over a minute, how we can fix that? we had other routers and is the same problem with out autentication to the server the workstations log on in less than 10 seconds, and also after 8 hours of been conected to the server we loss conection is there a place to change the conection time? we usually are 12 hours conected to the server.
ASKED: January 24, 2006  9:07 AM
UPDATED: January 30, 2006  1:32 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Your details are a little sketchy. Are the workstations and server on the same logical network? Can they ping with no problems? Is there anything in the error logs of the router or the systems? Are these systems part of a microsoft domain with the server as domain controller? How are you using VPNs? To me this sounds like something is timing out.

You might want to test connectivity by putting a workstation and the server on a small switch together and see if there are still problems.

Discuss This Question: 7  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Luissal
    Thanks astronomer for your answeer, we have the server and the work station in the same logical domain, the server is the domain controller, we tried diferent swicth boxes and 3 diferent routers.... same problem We have no errors in the server nor the router. we can ping with out any problem. And we don use VPN's yet we have the capability on the new router but haven't used yet.
    0 pointsBadges:
    report
  • Stbr05
    This is just a guess, but I would take some time and check what protocols are configured on your MS machine. Does the router suport anything but IP?
    0 pointsBadges:
    report
  • Dwiebesick
    How do your workstations obtain their IP address? Do a ipconfig /all on one workstation and see what the DNS number is. I suspect that your network enviroment may not be properly set up and you workstaions are using an external DNS server to try and locate SRV records like the DC to logon. Do you have a DNS server? Are you running Active Directory in your enviroment? If you have a DNS server, that is the IP your workstations should pull. THAT DNS server then should be configured with forwarders to forward resolution request that is not authoritative for, ie the rest of the world. dmw
    2,235 pointsBadges:
    report
  • Davbrown
    I don't know if you have tried this, but the DNS cache may need to be flushed. I find that this resolves a lot of problems with authentication. I would try going to the command prompt and typing the following: ipconfig /flushdns this should only take a few seconds and then type the following: ipconfig /registerdns and this should re-register your system with the domain controller and hopefully take care of your issues.
    0 pointsBadges:
    report
  • Astronomer
    The reason I asked about the logical network, (not logical domain), is because of an issue we discovered on our net. Our architecture uses central domain controllers with integrated active directory DNS but we discovered that systems couldn't browse shares on the other subnets. We found to my chagrin that we have to continue running WINS to allow browsing to all of the internal network shares. Are you testing ping by IP or name? Pinging by IP verifies basic IP connectivity. Pinging by fully qualified name checks DNS resolution as well. If you have problems here do some debugging with nslookup. Pinging by unqualified name also checks your domain search order. I strongly recommend you set up a DNS structure like ours if you haven't done so already. I'm in agreement with dmw. Incorporate active directory DNS and WINS on your domain controller. Depending on your ISP you may want it to forward DNS requests to the ISP DNS server or go directly to the root servers. Point all of your clients to the DC for both DNS and WINS. Make sure they are getting registered in active directory DNS. rt
    15 pointsBadges:
    report
  • Espettit
    I agree w/ dwiebesick. Everytime I have seen this kind of problem the WS's were trying to use external DNS. Set your WS's to use your DC as the primary DNS and the issue should go away.
    0 pointsBadges:
    report
  • Luissal
    THanks for all your input but I havent had a chance to try anything yet, because our company runs incometaxes and is risky to just play right now with the server, but as soon I have a chance I will let now everyone if I fix it or I destroyed the server....
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following