IRC Mapping

[Mortifer]

Wonder if anyone can help me. Users on my network are unable to connect to an IRC server through wingate 5. I'm running an Windows Xp network. Ip range 192.168.0.0. Subnet 255.255.255.0. Under services->Irc Mapping I put on the following options:
1. Service will start automatically
2. Service port = 6667
3. Enable default mapping to snow.shadowfire.org on port 6667
4. Specify interfaces connections will be accepted on:
127.0.0.1
192.168.0.1
5. Rotate connections out on all the following interfaces:
discovery (my dialup connection)
127.0.0.1
192.168.0.1
6. under Mappings:
Link to snow.shadowfire.org:6667 no dependencies

The rest I just left as the defaults are. Have I missed something?

[tim]

Wonder if anyone can help me. Users on my network are unable to connect to an IRC server through wingate 5. I'm running an Windows Xp network. Ip range 192.168.0.0. Subnet 255.255.255.0. Under services->Irc Mapping I put on the following options:
1. Service will start automatically
2. Service port = 6667
3. Enable default mapping to snow.shadowfire.org on port 6667
4. Specify interfaces connections will be accepted on:
127.0.0.1
192.168.0.1
5. Rotate connections out on all the following interfaces:
discovery (my dialup connection)
127.0.0.1
192.168.0.1
6. under Mappings:
Link to snow.shadowfire.org:6667 no dependencies
The rest I just left as the defaults are. Have I missed something?

Hi, remove the rotate option. It will not be able to use the 127 or 192 IPs to connect to an external site.

What results do you then get?

Tim

[Mortifer]

Chose the top option, let operating system decide, and it still doesn't work. Can you think of anything else?

[tim]

Chose the top option, let operating system decide, and it still doesn't work. Can you think of anything else?

Are the clients configured to use Wingate as the IRC server? This is required if you use the Mapped link method.

Have you tried letting them connect directly through the NAT, this is likely to be the best method.

Tim

[Mortifer]

I didn't think of that. I will change the server in the irc client to look at my server. Do the clients also have to go through port 6667 to my server?

I'm a bit new to this, so I'm unsure what this NAT is your talking about. What is that? And how do I use that methog?

Thanx for your Help so far Tim, much appreciated.

[adrien]

NAT stands for Network Address Translation.

The way to get it working is to configure the TCP/IP properties of your client machines so that their default gateway is the IP address of the WinGate machine. Then they use WinGate as their router to the internet, and the ENS (network driver of WinGate) translates the packet addresses as it forwards them onto the internet and back.

Then all the machines on your network think they are directly connected to the internet. There are some drawbacks for some client applications, but in the main about 99% of things work well like this, and the performance is better than working through a proxy although you then lose some control over what your users do.

Adrien

[Mortifer]

Thanx Guys, It worked. I configured the IRC Client to connect to my server and all worked fine. The user tells me that the connection to IRC keeps on dropping every now and then. I'll try the NAT method and see if that is more stable.

[adrien]

That will be because of session timeouts. If you go to the Sessions tab in the proxy you created for IRC, you will probably see that the default setting of 60s is in there - try increasing this to about 300 or so.

Adrien

[Mortifer]

Thank you guys, it worked like a charm. It was the session timeout.