Problem with yahoo Chat & www.ama-assn.org

[hochimin]

hi,

I am using wingate 5.0.5

while i am doing the physician search on the the site
"http://www.ama-assn.org" via wingate, the

page shows "session expired time out"

when doing the physician search from a directly connected machine the "DoctorFinder Usage Verification" page appears
before the search page

While connecting via Wingate the "DoctorFinder Usage Verification" page appears after the search page and shows "session expired time out".


I have also problem with yahoo chat through wingate.
To get chat i needs to configure inbond and outbond port to 8000 . where can i configure these.

pls help.

[jamesc]

page shows "session expired time out"

1. Has this always happened?
2. What connection method do you use?
3. Can you please show us your WinGate Configuration Report?
GateKeeper --> Options menu --> Advanced --> Save Report

I have also problem with yahoo chat through WinGate.
To get chat i needs to configure inbound and outbound port to 8000, where can i configure these.

When using the NAT connection method, you should not have to configure the outbound port. To set the incoming port for yahoo to listen on the WinGate computer, please do the following:



If you wanted to have the port mapped to another computer, then use the "Redirect Packet to IP Address" option as shown in the image.

[hochimin]

Thank you Mr. Jamesc for your reply.

1. It always happening.

2. I have a dlink router connected to the internet. Only restricted users are accessing the net through wingate, all others are connected to router and they have no problem for browsing and chatting.

3. Here is my wingate configuration report.


I had not installed the ENS service,

is it possible to add ENS now ?.

The ip 192.168.0.113 is connected to router (External- for Wingate)
and the 192.168.0.112 to lan for wingate users.

+++++++++++++++++++++++++++++++++++++++++++++++
1.01 WINGATE CONFIGURATION REPORT

1.02 Wednesday, November 02, 2005, 10:48

1.03

1.04 ---------------------------------------------

1.05 WinGate Engine

1.06 ---------------------------------------------

1.07 WinGate 5.0.7 (Build 826)

1.08 Operating System: Windows 2000 (NT 5.2)

1.09 Language: ENU

1.10

3.01 ---------------------------------------------

3.02 License details

3.03 ---------------------------------------------

3.04 Version: WinGate 5 Professional

3.05 Expiry: Does not expire

3.06 Num. users: 3

3.07 Max. users: Unlimited users

3.08 User database: WinGate

3.09

4.01 ---------------------------------------------

4.02 Dialer information

4.03 ---------------------------------------------

4.04 Dialer is disabled

4.05

5.01 ---------------------------------------------

5.02 Network Interfaces

5.03 ---------------------------------------------

5.04 ISDN (RAS) [External] [Unsecure]

5.05 127.0.0.1 (LOOPBACK) [Internal] [Secure]

5.06 192.168.0.112 (LAN) [Internal] [Secure]

5.07 192.168.0.113 (LAN) [External] [Unsecure]

5.08

6.01 ---------------------------------------------

6.02 Services

6.03 ---------------------------------------------

6.04

6.05 System Policies

6.06 ---------------------------------------------

6.07 Default System Access Rights:

6.08 Everyone - Restricted by ban list

6.09 Administrators - Unrestricted rights

6.10 Default Start/Stop Rights:

6.11 Administrators - Unrestricted rights

6.12 Default Edit Rights:

6.13 Administrators - Unrestricted rights

6.14

6.15 POP3 Proxy server (POP3 Proxy server)

6.16 ---------------------------------------------

6.17 Session Timeout: 120

6.18 Port: 110

6.19 Startup: Automatic start/stop

6.20 Binding 1: 127.0.0.1

6.21 Binding 2: 192.168.0.112

6.22 Access Rights: Defaults: may be used instead

6.23 Start/Stop Rights: Defaults: may be used instead

6.24 Edit Rights: Defaults: may be used instead

6.25

6.26 Telnet Proxy server (Telnet Proxy server)

6.27 ---------------------------------------------

6.28 Session Timeout: 60

6.29 Port: 23

6.30 Startup: Automatic start/stop

6.31 Binding 1: 127.0.0.1

6.32 Binding 2: 192.168.0.112

6.33 Access Rights: Defaults: may be used instead

6.34 Start/Stop Rights: Defaults: may be used instead

6.35 Edit Rights: Defaults: may be used instead

6.36

6.37 WWW Proxy server (WWW Proxy server)

6.38 ---------------------------------------------

6.39 Session Timeout: 60

6.40 Port: 80

6.41 Startup: Automatic start/stop

6.42 Binding 1: 127.0.0.1

6.43 Binding 2: 192.168.0.112

6.44 Access Rights: Defaults: may be used instead

6.45 Start/Stop Rights: Defaults: may be used instead

6.46 Edit Rights: Defaults: may be used instead

6.47

6.48 DHCP Service (DHCP Service)

6.49 ---------------------------------------------

6.50 Session Timeout: 60

6.51 Port: 67

6.52 Startup: Disabled

6.53 Binding 1: 192.168.0.112

6.54 Access Rights: Defaults: are ignored

6.55 Everyone - Unrestricted rights

6.56 Start/Stop Rights: Defaults: may be used instead

6.57 Edit Rights: Defaults: may be used instead

6.58

6.59 Winsock Redirector Service (Winsock Redirector Service)

6.60 ---------------------------------------------

6.61 Session Timeout: 20

6.62 Port: 2080

6.63 Startup: Automatic start/stop

6.64 Binding 1: 127.0.0.1

6.65 Binding 2: 192.168.0.112

6.66 Access Rights: Defaults: may be used instead

6.67 Start/Stop Rights: Defaults: may be used instead

6.68 Edit Rights: Defaults: may be used instead

6.69

6.70 FTP Proxy server (FTP Proxy server)

6.71 ---------------------------------------------

6.72 Session Timeout: 60

6.73 Port: 21

6.74 Startup: Automatic start/stop

6.75 Binding 1: 127.0.0.1

6.76 Binding 2: 192.168.0.112

6.77 Access Rights: Defaults: may be used instead

6.78 Start/Stop Rights: Defaults: may be used instead

6.79 Edit Rights: Defaults: may be used instead

6.80

6.81 RTSP Streaming Media Proxy (RTSP Streaming Media Proxy)

6.82 ---------------------------------------------

6.83 Session Timeout: 60

6.84 Port: 554

6.85 Startup: Automatic start/stop

6.86 Binding 1: 127.0.0.1

6.87 Binding 2: 192.168.0.112

6.88 Access Rights: Defaults: may be used instead

6.89 Start/Stop Rights: Defaults: may be used instead

6.90 Edit Rights: Defaults: may be used instead

6.91

6.92 SOCKS Proxy server (SOCKS Proxy server)

6.93 ---------------------------------------------

6.94 Session Timeout: 60

6.95 Port: 1080

6.96 Startup: Automatic start/stop

6.97 Binding 1: 127.0.0.1

6.98 Binding 2: 192.168.0.112

6.99 Access Rights: Defaults: may be used instead

6.100 Start/Stop Rights: Defaults: may be used instead

6.101 Edit Rights: Defaults: may be used instead

6.102

6.103 VDOLive Proxy server (VDOLive Proxy server)

6.104 ---------------------------------------------

6.105 Session Timeout: 60

6.106 Port: 7000

6.107 Startup: Automatic start/stop

6.108 Binding 1: 127.0.0.1

6.109 Binding 2: 192.168.0.112

6.110 Access Rights: Defaults: may be used instead

6.111 Start/Stop Rights: Defaults: may be used instead

6.112 Edit Rights: Defaults: may be used instead

6.113

6.114 POP3 Server (POP3 Server)

6.115 ---------------------------------------------

6.116 Session Timeout: 120

6.117 Port: 110

6.118 Startup: Manual start/stop

6.119 Binding 1: 127.0.0.1

6.120 Binding 2: 192.168.0.112

6.121 Access Rights: Defaults: may be used instead

6.122 Start/Stop Rights: Defaults: may be used instead

6.123 Edit Rights: Defaults: may be used instead

6.124

6.125 SMTP Server (SMTP Server)

6.126 ---------------------------------------------

6.127 Session Timeout: 300

6.128 Port: 25

6.129 Startup: Manual start/stop

6.130 Binding 1: 127.0.0.1

6.131 Binding 2: 192.168.0.112

6.132 Access Rights: Defaults: may be used instead

6.133 Start/Stop Rights: Defaults: may be used instead

6.134 Edit Rights: Defaults: may be used instead

6.135

6.136 GDP Service (GDP Service)

6.137 ---------------------------------------------

6.138 Session Timeout: 60

6.139 Port: 368

6.140 Startup: Automatic start/stop

6.141 Binding 1: 127.0.0.1

6.142 Binding 2: 192.168.0.112

6.143 Access Rights: Defaults: may be used instead

6.144 Start/Stop Rights: Defaults: may be used instead

6.145 Edit Rights: Defaults: may be used instead

6.146

6.147 XDMA Proxy service (XDMA Proxy service)

6.148 ---------------------------------------------

6.149 Session Timeout: 20

6.150 Port: 8000

6.151 Startup: Automatic start/stop

6.152 Binding 1: 127.0.0.1

6.153 Binding 2: 192.168.0.112

6.154 Access Rights: Defaults: may be used instead

6.155 Start/Stop Rights: Defaults: may be used instead

6.156 Edit Rights: Defaults: may be used instead

6.157

6.158 DNS Service (DNS Service)

6.159 ---------------------------------------------

6.160 Session Timeout: 60

6.161 Port: 53

6.162 Startup: Disabled

6.163 Binding 1: 192.168.0.112

6.164 Access Rights: Defaults: may be used instead

6.165 Start/Stop Rights: Defaults: may be used instead

6.166 Edit Rights: Defaults: may be used instead

6.167

6.168 WWW Server for viewing log files (Logfile Server)

6.169 ---------------------------------------------

6.170 Session Timeout: 60

6.171 Port: 8010

6.172 Startup: Automatic start/stop

6.173 Binding 1: 127.0.0.1

6.174 Binding 2: 192.168.0.112

6.175 Access Rights: Defaults: may be used instead

6.176 Start/Stop Rights: Defaults: may be used instead

6.177 Edit Rights: Defaults: may be used instead

6.178

6.179 Remote Control Service (Remote Control Service)

6.180 ---------------------------------------------

6.181 Session Timeout: 60

6.182 Port: 808

6.183 Startup: Automatic start/stop

6.184 Binding 1: 127.0.0.1

6.185 Binding 2: 192.168.0.112

6.186 Access Rights: Defaults: may be used instead

6.187 Start/Stop Rights: Defaults: may be used instead

6.188 Edit Rights: Defaults: may be used instead

6.189

7.01 ---------------------------------------------

7.02 System Route Table

7.03 ---------------------------------------------

7.04 Current Route Table:

7.05 ---------------------------------------------

7.06 Network Mask Gateway Interface Metric

7.07 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.113 20

7.08 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

7.09 192.168.0.0 255.255.255.0 192.168.0.112 192.168.0.112 20

7.10 192.168.0.0 255.255.255.0 192.168.0.113 192.168.0.113 20

7.11 192.168.0.112 255.255.255.255 127.0.0.1 127.0.0.1 20

7.12 192.168.0.113 255.255.255.255 127.0.0.1 127.0.0.1 20

7.13 192.168.0.255 255.255.255.255 192.168.0.112 192.168.0.112 20

7.14 192.168.0.255 255.255.255.255 192.168.0.113 192.168.0.113 20

7.15 224.0.0.0 240.0.0.0 192.168.0.112 192.168.0.112 20

7.16 224.0.0.0 240.0.0.0 192.168.0.113 192.168.0.113 20

7.17 255.255.255.255 255.255.255.255 192.168.0.112 192.168.0.112 1

7.18 255.255.255.255 255.255.255.255 192.168.0.113 192.168.0.113 1

7.19

9.01 ---------------------------------------------

9.02 END OF CONFIGURATION REPORT
+++++++++++++++++++++++++++++++++++++++++++++++

[jamesc]

Hi Hochimin,

If I can get this last detail off you, I can advise a solution regarding Yahoo.

When I asked "2. What connection method do you use? "

I meant, how do your clients connect to the WinGate server? Proxy / WinGate Intrernet Client (WGIC).

[hochimin]

hi,


Our clients connecting through Proxy to wingate server



Thank you

[jamesc]

Regarding http://www.ama-assn.org

1. Does this problem still occur when caching is turned off?

2. Version 5.0.5 was released in May 2003. Can you upgrade to our latest version and see if you are still having the issue? Your license will still work with it. If you do upgrade, please check your network adpatrers are correctly marked an Internal/External

http://downloads.qbik.com/qbiknz2/downl ... 68-USE.EXE



Regarding Yahoo Messenger

If you are still having problems with Yahoo Messenger after the upgrade, then you may want to configure that application to use NAT. Based off your network description, there are two ways this can be done.


1. Put the WinGate Internet Client on the restricted users machines, and set the Yahoo Messenger Program as "Local" in the application list; this will allow yahoo to use the NAT connection method to your router; assuming the restricted clients can have a default gateway and DNS set in their TCP/IP.

2. You can add the ENS in afterward. Before you do, you should consider changing the subnets of the Internal / External network cards. You currently have them configured as:
EXTERNAL 192.168.0.113
INTERNAL 192.168.0.112

Can you change the subnet for the external adapter to 192.168.1.113
You would have to change your dlink router address too, to be on the 192.168.1.x subnet.
Your users who are currently connected directly to the router will need to utilise WinGates NAT; they should not notice any difference, unless they have ports mapped to their machine from the router.


To install ENS:

a) Backup your current WinGate registry,
(Windows) Start menu --> Programs --> WinGate --> Advanced Options --> Registry --> Export settings.

b) Reinstall WinGate with the ENS option.

c) After the reinstall, check your settings / policies to make sure they are the same as before.

More information on the NAT connection method is available from here: http://support.qbik.com/index.php?_a=kn ... ils&_i=123

[hochimin]

hi,

the new version solved my problem with http://www.ama-assn.org

but the yahoo chat problem still remains same.

is there is any way to get it without using the wingate client.?

thank you.