Search found 5 matches

Search found 5 matches Page 1 of 1
by sepp.huber
Tue Feb 16, 2021 6:32 pm
Forum: Viscosity Support (Windows Version)
Topic: DNS Issues after v1.9 Update
Replies: 14
Views: 4612

Hey Eric, cannot find anything in the VPN logs. Here the output of route print : C:\Users\sepp.huber>ROUTE PRINT =========================================================================== Schnittstellenliste 12...a8 5e 45 54 0a 43 ......Intel(R) I211 Gigabit Network Connection #2 9...00 ff a4 79 32...
by sepp.huber
Mon Feb 15, 2021 8:00 pm
Forum: Viscosity Support (Windows Version)
Topic: DNS Issues after v1.9 Update
Replies: 14
Views: 4612

Hey Eric, Yes, when the timeout problem occurs, the nslookup bing.com fd00::9a9b:cbff:fe97:b3d6 (= DNS-IPv6 address of Fritz!Box) command leads to a timeout. But if I disconnect the VPN, then everything works fine again. Today, I removed Viscocity and re-installed it again. Since then, there were no...
by sepp.huber
Fri Feb 12, 2021 6:31 pm
Forum: Viscosity Support (Windows Version)
Topic: DNS Issues after v1.9 Update
Replies: 14
Views: 4612

Hey Eric, this request works perfect. I got an instant response: nslookup bing.com fd00::9a9b:cbff:fe97:b3d6 Server: fritz.box Address: fd00::9a9b:cbff:fe97:b3d6 Nicht autorisierende Antwort: Name: bing.com Addresses: 2620:1ec:c11::200 13.107.21.200 204.79.197.200 But today, everything seems to be a...
by sepp.huber
Tue Feb 09, 2021 9:11 pm
Forum: Viscosity Support (Windows Version)
Topic: DNS Issues after v1.9 Update
Replies: 14
Views: 4612

Hey Eric, Thanks for your answer! One of the servers seem to work fine, the second not. The third and fourth DNS servers are my FritzBox: C:\Users\sepp-huber>nslookup bing.com 172.16.30.10 Server: ****** Address: 172.16.30.10 Nicht autorisierende Antwort: Name: bing.com Addresses: 2620:1ec:c11::200 ...
by sepp.huber
Mon Feb 08, 2021 8:03 pm
Forum: Viscosity Support (Windows Version)
Topic: DNS Issues after v1.9 Update
Replies: 14
Views: 4612

Hey Eric, since the release of 1.9.1 (1701) I have the same problem again. With the beta version before, everything seemed to be fine. But after updating to 1.9.1 nslookup tells me, that resolving a domain leads to a timeout: C:\Users\sepp.huber>nslookup bing.com Server: Viscosity Address: fd53:7061...
Search found 5 matches Page 1 of 1