View previous topic :: View next topic |
Author |
Message |
wienerwald
Joined: 26 Aug 2010 Posts: 6 Location: Germany
|
Posted: Thu Aug 26, 2010 12:48 pm Post subject: Instand keyword issue |
|
|
Too keep it short and simple:
We have a distributed network topology with external dhcp-servers at each site...To get instant keywords working, we provided the clients with the correct dns-suffix via dhcp (same as set in instant keywords @ FS-management). DNS is provided by FirstSpot.
With this Setup, logging out by typing "logout.ourdomain.local" in a browser works fine. Unfortunately a simple "logout" does not. |
|
Back to top |
|
|
wienerwald
Joined: 26 Aug 2010 Posts: 6 Location: Germany
|
Posted: Thu Aug 26, 2010 12:49 pm Post subject: |
|
|
Oh, forgot something:
What am I missing? How to get this to work? |
|
Back to top |
|
|
wienerwald
Joined: 26 Aug 2010 Posts: 6 Location: Germany
|
Posted: Thu Aug 26, 2010 12:52 pm Post subject: |
|
|
Mh...missing the edit button. And I meant InstanT keyword, of course. |
|
Back to top |
|
|
alan Forum facilitator
Joined: 26 Sep 2003 Posts: 4435
|
Posted: Thu Aug 26, 2010 4:34 pm Post subject: |
|
|
It should be still related to default DNS suffix. Your client should get DNS suffix of "ourdomain.local" from your DHCP server.
To test, just issue the below command in the client side:
nslookup logout
and you should get the Visitor Network Interface IP. _________________ ~ Patronsoft Limited ~ |
|
Back to top |
|
|
wienerwald
Joined: 26 Aug 2010 Posts: 6 Location: Germany
|
Posted: Fri Aug 27, 2010 7:23 am Post subject: |
|
|
That´s the Problem: Firstspot does not resolve a simple "logout", therefore "logout" doesn´t work.
The DNS-suffix sent by the DHCP-Server and the one in "Instant Keywords" are set identical! "ipconfig -all" proves that. |
|
Back to top |
|
|
alan Forum facilitator
Joined: 26 Sep 2003 Posts: 4435
|
Posted: Fri Aug 27, 2010 7:36 am Post subject: |
|
|
Please issue the following command in the client PC:
ipconfig/all
nslookup
set d2
logout
and post the output here. _________________ ~ Patronsoft Limited ~ |
|
Back to top |
|
|
wienerwald
Joined: 26 Aug 2010 Posts: 6 Location: Germany
|
Posted: Fri Aug 27, 2010 10:32 am Post subject: |
|
|
Thanks, that pointed me into the right direction.
I was testing the visitor network with a domain-joined machine. The diagnostic nslookup-ouput showed that the connection specific dns-suffix was not in the clients dns queries at all. I tried to additionally push dhcp-option 115 (domain search order) to the client with no success.
Since we push dns search order lists via group policy to our internal clients, dhcp-option 115 doesn´t seem to override these settings (which is fine! ;]).
So, after leaving the domain with the client, everything worked like a charm.
So we finally seem to end up with a simple "logout" working for all machines except for domain-machines which have a dns suffix list/search order applied by group policy - the users of these clients have to use "logout.somedomain.local". I can live with that! |
|
Back to top |
|
|
wienerwald
Joined: 26 Aug 2010 Posts: 6 Location: Germany
|
Posted: Fri Aug 27, 2010 10:36 am Post subject: |
|
|
Oh, I meant DHCP-option 119....not 115. |
|
Back to top |
|
|
|