M
Me2
Hi,
Here is the situation.
@ work we host a couple of project web sites that use integrated logins. @
home I used to have DSL due to need of a static Ip. Everything worked fine.
I use a laptop (XP Pro) that has joined the domain @ work and while @ home I
log in the same way (using cached profile). Recently I switched to a cable
isp and now that same laptop cannot log on to any of the websites. Any of
my other computers (I run my own dc @ home) XP or win2k Pro get prompted and
everything works fine. I've noticed that my cable is giving me a
connection-specific DNS suffix that is different from my @ work suffix, so I
configured my home dhcp to pass me the same as I get from work and it still
won't auth me. I have another user with something similar where it does the
same at his house (same cable provider and also using XP Pro). His goes a
step beyond where when he connects in the office he can do all normal net
functions (print/file/mail) except auth on the web server until he does a
release then renew. I don't know if this is more of IIS being picky (does
this on both win2k as well as win2k3 IIS) or something else. It's only
happens on the computer that has been joined to the work domain. Nothing
has changed hardware wise at home or at work. It has to be something with
the DHCP info that I'm being handed.
I can ping by fqdn and get a response, but it just dies on the auth part.
I can go to the websites by putting in the ip addy then the site dir (ie
http://10.10.10.1/website verses http://whereiwanttogo.com/website)
After calling another user it works fine with his win 2k Pro laptop ,it just
seems to affect XP.
R
Here is the situation.
@ work we host a couple of project web sites that use integrated logins. @
home I used to have DSL due to need of a static Ip. Everything worked fine.
I use a laptop (XP Pro) that has joined the domain @ work and while @ home I
log in the same way (using cached profile). Recently I switched to a cable
isp and now that same laptop cannot log on to any of the websites. Any of
my other computers (I run my own dc @ home) XP or win2k Pro get prompted and
everything works fine. I've noticed that my cable is giving me a
connection-specific DNS suffix that is different from my @ work suffix, so I
configured my home dhcp to pass me the same as I get from work and it still
won't auth me. I have another user with something similar where it does the
same at his house (same cable provider and also using XP Pro). His goes a
step beyond where when he connects in the office he can do all normal net
functions (print/file/mail) except auth on the web server until he does a
release then renew. I don't know if this is more of IIS being picky (does
this on both win2k as well as win2k3 IIS) or something else. It's only
happens on the computer that has been joined to the work domain. Nothing
has changed hardware wise at home or at work. It has to be something with
the DHCP info that I'm being handed.
I can ping by fqdn and get a response, but it just dies on the auth part.
I can go to the websites by putting in the ip addy then the site dir (ie
http://10.10.10.1/website verses http://whereiwanttogo.com/website)
After calling another user it works fine with his win 2k Pro laptop ,it just
seems to affect XP.
R