Workstation on a Domain can ping gatway, external DNS and resolve External names to IP address but can't browse Internet

We have a Windows 2003 R2 domain with a DC, and 20 workstations. All workstations and servers can browse the internet but 1. The workstation in question can ping internal ip's and netbios names with sucess. It can also resolve external domain names to their appropriate ip addresses and can ping them either by ip or name (ie. www.google.com = 216.239.51.104). When the workstation logs on to the domain the user cannot get a browser to finish connecting, IE or Firefox report "connecting to www.google.com...." but never do.

I have tried changeing firefox's config to "network.dns.disableipv6" from false to true with no joy.

I have checked windows firewall (off) and proxy settings in both browsers (not set).

If I log in to the local machine (not thru the domain) both browsers work. So I am left with something in the profile maybe?????

I created a new user on the machine and logged on to the domain with new user to get a fresh new profile and still no joy!!

Any body?????

Anybody seen th
entre-tcvAsked:
Who is Participating?
 
Computer101Connect With a Mentor Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0
 
SysExpertCommented:
IS this user the newst in the Domain ?

Have you checked his effective rights  for Browser and Internet access ?

I hope this helps !
0
 
entre-tcvAuthor Commented:
Forgot to mention that all workstations are XP Pro SP2.

Problem exists whether workstation receives dynamic IP or static ip.

Have also changed TCP/IP properties on NIC from just the ip of the internal Domain controller only to the DC's IP plus the ISP's DNS servers as 2ndary and terciary (sp?) This also has no change.

SYSExpert: This user was migrated last from local to new domain using Windows XP "Files and Settings Transfer Wizard".

I have not checked effective right for browser as felt all in domain would have the same effective rights and all others can browse.

Other users were also migrated using FSTW....
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

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.

 
entre-tcvAuthor Commented:
Why would being the newest in the domain make a difference?  
0
 
SysExpertCommented:
Well, If he is the newst in the Domain, perhaps some default Profile settings were changed ad that is why only he is affected.

just something to think about.



0
 
johnb6767Commented:
Any chance there could be a corrupt LSP in his Winsock?

netsh winsock reset

restores the winsock to default..

and even for giggles...

netsh firewall reset

well, you get the idea of that one.....

But a totally blown winsock wouldnt even allow name resolution period though I would think....May be wrong....
0
 
entre-tcvAuthor Commented:
I tried the winsockfix earlier and couldn't see any difference.

I think it may be that something went awry during the FSTW process, after all it took several hours for the collection phase and wound up running over night. The we migrated the "profile" to the new domain user. The workstation connects fine when you log on to the local machine.

Would you expect to see that if there's a problem within the TCP/ip stack or Winsock?
0
 
SysExpertCommented:
No, so that is why I think it is a profile issue.

0
 
entre-tcvAuthor Commented:
I tend to agree as the transfer took sooooooo long. I believe it may have some gremlims in it. I am in the process of running a full defrag on the "local machine" now and after that will remove everything that isnot essential. I will then try anoth FSTW run after lunch.

I will let you know how it goes.
0
 
entre-tcvAuthor Commented:
Ok. I went back and started to clean up the workstation in question by doing a defrag, running scandisk with fix option, deleting all docs and data from other (previous) users of the workstation, etc. Only problem was that by the time I finished re-running Files and Setttings Transfer Wizard again was that the workstation would not connect to web sites thru any browser even logged into the local machine!!

I decided my best bet was to move the primary drive to the second bay in the PC, install a new drive in the workstation and do a fresh OS install of XP Pro on the new drive. That way I would know that the problem wasn't in the OS or the hardware.

After that was done, I checked www connectivity(OK now), made the DC the only DNS entry (experience), re-authenticated the workstation to the domain, added the domain user, re-installed M$Office 2K3 as that user and imported the previously saved PST files and backup cd of the users old Data.

I still don't know what caused the browsers to stop working or how to fix it short of re-installing the OS.
0
 
entre-tcvAuthor Commented:
Never got a solution fron anyone and solved it myself.
No points awarded in this case. But thanks for the effort.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.