• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 514
  • Last Modified:

limited or no connectivity

XP Pro sp2. working fine yesterday. user unable to login. limited or no connectivity. appl log shows following com+ event system detected an inconsistency in internal state. assertion "getlasterror=122L"
failed at line 201 of d:/xp_slp/com/com1x/src/events/shared/sectools.cpp
0
brossier
Asked:
brossier
  • 4
  • 3
  • 2
1 Solution
 
artoaperjanCommented:
Hello
is it stand alon or network ?
using DHCP or static IP ?

mor info pls.
0
 
briancassinCommented:
Have you tried logging in with a different user account ? You may have a corrupted user account.

Are there any other errors in the app log or in the system log ?
0
 
brossierAuthor Commented:
tried to login as different user, same results. plugged laptop into same port. no problems.
i quoted error in appl log in original question. "getlasterror=122L.... no such at MS support
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
brossierAuthor Commented:
is on network, using dhcp
0
 
briancassinCommented:
what do you mean by this "plugged laptop into same port. no problems"
so is working fine and this is only happening when you plug the laptop into different ethernet ports or something? I don't quite understand the comment
0
 
artoaperjanCommented:
could you pleas put the IPconfig/all
so we can see
0
 
brossierAuthor Commented:
re laptop in port. As a test of the wiring, I plugged my laptop into the port the system in question is attached to. Laptop boots and logs into network fine. Problem is in workstation.

IPconfig /all shows correct host name, correct domain, hybrid as node type... also show autoconfig enabled, autoconfig ip address enabled, autoconfig ip address is 169.254.43.10... no gateway

unable to ping anything
0
 
briancassinCommented:
your not getting a DHCP address your getting an APIPA... which means it isn't reaching the DHCP server which might be causing the other error..

several things
did you use the same cable to test with ? if not use the same cable see if you can still connect fine...


1. Is your windows time and date correct on the workstation ?

2. Go to the command prompt and do ipconfig /release then ipconfig/renew what happens ? do you still get 169.xxx if so continue...

3. If you go to your network connections then the properties of the connection then tcp/ip properties do you have any numbers in the ip address sections even if you have it selected for DHCP. do you have an alternate configuration listed ?

4. Try assigning a static IP address can you now ping the default gateway and other pc's on the network ? if not then you may your probably looking at an issue with the network card.
0
 
brossierAuthor Commented:
To all who responded, Thanks. I've located the problem and it is ME!!!... DHCP service in the server had stopped and as users shut down and rebooted the next day they got no IP address from the server. I should have known..... too many brushfires and too old for this crap anymore.
Thanks again.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now