Member Avatar for Krispy84

I have a win 2000 client running in a 2003 environment and it just up and randomly has decided that it is going to loose connection to EVERYTHING, however, It is at a different location and i can remote into it so it's obviously physically connected, my dhcp server provides it an address, and all the DNS's are pingable.

It gets all it's network drive paths on login and can connect to anywhere inside the network...
I can ping anything internal or external...
but...
IE will not open any website internal or external...
and my propritary program has gotten a socket error...

As a user logged into the network it has this issue.
Logged in as a locally it has this issue.
But...
If i actually disjoin(instead of just logging in locally) i can connect to w/e i'd like.

anyone have an idea of what to start looking at to resolve this?
I've run AdAware and AVG and neither have found anything to resolve this.

  • 2 Contributors
  • 5 Replies
  • 127 Views
  • 10 Hours Discussion Span
  • Latest Post Latest Post by Member #46692

Dani AI

Generated

Useful troubleshooting notes based on the symptom pattern in this thread (ICMP and file shares OK, but socket-based clients like a browser and a custom app fail while the machine is domain-joined). s observations and s proxy/browser suggestions are good starting points; the next steps focus on isolating whether the problem is a Winsock/LSP/COM registration issue or a domain-applied change (GPO/startup software) that alters the machine-wide network stack.

Quick diagnostic checklist (collect these before making changes):

ipconfig /all
nslookup <server-name>
telnet <host> 80   # test raw TCP connect to HTTP port
netstat -an
eventvwr       # check System/Application logs for network/socket errors

Also run the same browser/app under Process Explorer to inspect loaded modules (look for non-Microsoft network filter DLLs) and note any services or startup items pushed by domain policies.

Targeted repair steps to try (in order, with backups):

  • Check for proxy/WPAD settings in IE and any domain Startup/Logon scripts or computer policies that install networking software. Disable those temporarily to test.
  • Re-register core IE/network COM DLLs as admin (for example regsvr32 urlmon.dll), run sfc /scannow to repair system files, and reinstall/repair any managed runtimes if managed apps are affected.
  • Inspect for third-party LSPs or filter drivers (AV/IDS/VPN) and uninstall or disable them to test. If Winsock appears corrupted, restore the stack using vendor/OS-recommended tools or by reinstalling the TCP/IP protocol through Network Connections.
  • Capture a network trace (Microsoft Network Monitor) while reproducing the failure to see whether TCP SYNs are sent and responses received.

Cautions: back up the registry before edits, document services you disable, and test changes out-of-hours. If the machine’s behavior changes when you remove it from the domain, prioritize reviewing applied computer-level GPOs and domain-deployed security/network software.

Recommended Answers

All 5 Replies

Member Avatar for Member #46692

hmm, how are you connecting to the net, via a proxy server if so make sure the address is set correctly.

I.e go to tools> internet options >connections tab and then the LAN button (in internet explorer)

Also what happens if you install another browser, such as firefox?

Member Avatar for Krispy84

don't have a proxy, wish it were that easy. and the setting for that is disabled in any case.

haven't tried another browser. The concerning thing is that my proprietary app is running into a socket error too that doesn't get an issue when it's disjoined. i will try firefox next.

Can anyone think of a difference between logging in locally and actually disjoining from the domain?

I can't see how these 2 are different at all but they make all the difference.

Member Avatar for Member #46692

What do you mean by disjoining from the domain?
What is the socket error.

Member Avatar for Krispy84

i appreciate your help but i finally got it resolved...

by disjoining i meen making it part of workgroup instead of the domain.

it was resolved by reinstalling the .net framework stuff for window's.

i honestly don't know why this was the resolution but it worked and sometimes it's better not to ask questions :D

thankyou very much for your help

Member Avatar for Member #46692

i honestly don't know why this was the resolution but it worked and sometimes it's better not to ask questions

I know what you mean.

How the dot net framework would affect Internet explorer I wouldn't know. Oh well.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.