PC Connection troubleshooting

Configure XP Firewall:
Service Pack 1:

• Open Network Connections
• Select relevant Dial-up, LAN or High-Speed Internet connection
• Under Network Tasks, click Change settings
• On Advanced, under Internet Connection Firewall
• uncheck "Protect my computer and network"
  • There are advanced options to enable specific ports but that is at the user's discretion to configure

Service Pack 2:

• Click Start
• Click Control Panel
• Click Security Center
• Click Windows Firewall

If it is ON, you have two choices:

• 1) Turn it OFF (not recommended)
• OR
• 2) Add iVisit to the Exceptions list
  • Click Exceptions (Be sure "Don't allow exceptions is NOT checked!)
  • Click Add Program
  • Select iVisit from the "Add a program" list
  • Click OK
  • Click OK again
  • Close Security Center and Control Panel
  • Start iVisit

CONFIGURE AOL FIREWALL TO ALLOW iVisit THROUGH A SPECIFIC PORT:

1. On the Windows® desktop, double-click the AOL Safety and Security Center icon. If the icon is not present, click the Start button, point to Programs or All Programs, point to AOL Safety and Security Center, then click Firewall.
2. From the list of items on the left side of the program window, double-click the Firewall item, then click the Port Permissions tab.
3. Click the Add button.
4. In the Permission name: box, type the name for the port permission.
5. Enter the numbers associated with the incoming and outgoing TCP /IP ports and/or UDP/IP ports in the appropriate boxes.
6. Click the Allow or Block button to apply that permission level to the specified ports.

SET YOUR FIREWALL SECURITY SETTING TO LOW:

1. On the end of the Windows® task bar next to the clock, right-click the AOL Safety and Security Center icon, point to Firewall, then click Open Firewall. The AOL Safety and Security Center window will be opened to the AOL Firewall page.
2. Click the Settings tab.
3. Click the Low option to mark it.

PC TRACE

• 1: In windows click START RUN
• 2: Type COMMAND and click OK
• 3: An MS-DOS Prompt window will appear before you with a blinking cursor.
• 4: Type the follow:
  • tracert ivisit.net
  • If you are running a trace to a friend, type tracert their-ip-address (i.e. tracert 192.168.0.1).
• 5: Wait a few minutes as the trace proceeds and your command prompt cursor will then re-appear.
• 6: Look at the MS (millisecond) latency time for each hop (each line). If any of these are well into the hundreds or timing out before reaching the iVisit server Firewall (border2.ge4-1-bbnet2.ext1.lax.pnap.net) this is the trouble. If the latency or time out appears in the first hop then it's possible you're behind a Network Firewall or buggy router. If it occurs in the middle to last hops then you'll need to talk to your ISP to resolve as it's a routing problem through the Internet. If you have a Firewall temporarily disable it OR temporarily allow ICMP type 8 outgoing to pass through.
• REPEAT the above steps to trace from your computer to a friends computer!
• Type EXIT and press ENTER to close the MS-DOS Prompt

FOR PC USERS NEEDING HELP WITH MULTIPLE IP ADDRESS ADAPTERS:
When running iVisit for FIRST time after install you will be presented with a window:"Select IP Address"
At which point you select the IP address of the Adapter you wish to use:
EXAMPLE:
IP 200.14.25.0 "Cable Modem Ethernet Adapter"
IP 25.10.232.5 "Dial-Up 56k Adapter"
Then click OK
To change IP after already running iVisit do the following:

• click SETTINGS > PREFERENCES > CONNECTION MANAGEMENT
• Under Multi-homed Systems Settings
• click IP SELECTOR > click the IP address you wish to use > click OK
• click OK on window telling you "Your changes will not take effect until iVisit is restarted"
• click OK
• close iVisit
• restart iVisit

To confirm that you are behind a NAT, open the Network Stats window in iVisit. If it shows 2 IP addresses for your local IP, with the second in parentheses, you are behind a NAT.

Zone Alarm:
Set "Internet Security Level" to Medium to unblock video (UDP port 9940)

Some versions of Windows2000 and ME can also have their security level set so high that it prevents software like iVisit working. Try lowering the security level.

Internet Connect Sharing Config:
If you have Internet Connect Sharing running on a PC a special configuration file is available which will enable iVisit to work in these situations.
http://www.practicallynetworked.com/sharing/ics/icsconfiguration.htm
http://www.practicallynetworked.com/sharing/ics/icsconfig_maps.htm
http://www.practicallynetworked.com/downloads/ICS_Config_maps/ivisit.ics

Mac Connection troubleshooting
If you are running NetBarrier on a Mac and are using a 'Customized' set - go to "Add Set" and select the iVisit option then click Save.

Using internal Mac-Firewall on OSX:

1. Open System Preferences > Sharing Control Panel
2. Click Firewall Tab
3. Click New
   • Port Name Other
   • Port Range 9940-9950
   • Description iVisit
4. Click [OK] then Close the Control, Panel
5. Now the Firewall is open for incoming and outgoing traffic of iVisit.

MAC TRACE:
(to the server, or a person you can't connect with; 'user unreachable')

OS 9
• 1: Download WhatRoute, IPNetMonitor, AGNetTools or similar utility from VersionTracker or TuCows (any basic trace utility)
• 2: Trace from your machine to ivisit.net or the person you can't connect to
A trace to ivisit.net is successful if it reaches our Firewall at:
border2.ge1-1-bbnet1.ext1.lax.pnap.net
A trace to another person is successful if it reaches the IP# you entered.
• 3: Look at the MS (millisecond) latency time for each hop (each line). If any of these are well into the hundreds or timing out before reaching the iVisit server this is the trouble.
If the latency or time out appears in the first hop then it's possible you're behind a Network Firewall or buggy router. If it occurs in the middle to last hops then you'll need to talk to your ISP to resolve as it's a routing problem through the Internet.

OS X
• 1: Run Applications/Utilities/Network Utility
• 2: Click the [Trace] Tab and enter ivisit.net or the IP# of the person you can't connect to
A trace to ivisit.net is successful if it reaches our Firewall at:
border2.ge1-1-bbnet1.ext1.lax.pnap.net
A trace to another person is successful if it reaches the IP# you entered.
• 3: Look at the MS (millisecond) latency time for each hop (each line). If any of these are well into the hundreds or timing out before reaching the iVisit server this is the trouble.
If the latency or time out appears in the first hop then it's possible you're behind a Network Firewall or buggy router. If it occurs in the middle to last hops then you'll need to talk to your ISP to resolve as it's a routing problem through the Internet.