Welcome to ISAserver.org
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Troubles with internal subnets :(
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
Troubles with internal subnets :( - 21.Sep.2006 3:13:19 PM
|
|
|
Ten
Posts: 20
Joined: 28.Jul.2004
From: Russian, Kirov
Status: offline
|
Hello. For me such problem. Has passed from version ISA2004 on ISA2006 the standard by means of Export-Import. All works perfectly, except for one: subnets have ceased "to see" a server on which it is installed ISA2006. Ping command on a host in any of a subnet up to ISAserver is fulfilled unsuccessfully. IE it is customized on a proxy. At attempt to access to any address in log ISAserver I see 2 strings - "Initiated Connection port 8080" and after a while "Closed connection"; the browser produces an error. Routing is customized correctly (IMHO) - coz before upgrade ISA of these problems was not. Subnets are certain in "Internal" list of networks. I do not know, as to do 8( Probably, there is any essential difference in operation with subnets for new version ISA. P.S. Sorry for my poor English
|
|
|
|
RE: Troubles with internal subnets :( - 22.Sep.2006 5:26:19 AM
|
|
|
Ten
Posts: 20
Joined: 28.Jul.2004
From: Russian, Kirov
Status: offline
|
All machines in all local subnetworks cannot find not only ISA Firewall, but also a host on which he is installed. The router through which packages go from these subnetworks, finds ISA Server (and this host) perfectly.
|
|
|
|
RE: Troubles with internal subnets :( - 23.Sep.2006 7:15:07 AM
|
|
|
Ten
Posts: 20
Joined: 28.Jul.2004
From: Russian, Kirov
Status: offline
|
Server rbp4.city.kirov.ru is a router in my local net. ipconfig from it: Настройка протокола IP для Windows 2000
Адаптер Ethernet Ethernet_new:
DNS суффикс этого подключения . . :
IP-адрес . . . . . . . . . . . . : 192.168.1.4
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз . . . . . . . . . . : 192.168.1.6
Адаптер Ethernet Subnet4:
DNS суффикс этого подключения . . :
IP-адрес . . . . . . . . . . . . : 192.168.4.2
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз . . . . . . . . . . :
Адаптер Ethernet VDSL_Subnet2:
DNS суффикс этого подключения . . :
IP-адрес . . . . . . . . . . . . : 192.168.2.1
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз . . . . . . . . . . :
Result route print from rbp4: ===========================================================================
Список интерфейсов
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 20 ed 53 f9 b1 ...... Intel(R) PRO Adapter
0x1000004 ...00 50 04 81 38 45 ...... 3Com EtherLink PCI
0x1000005 ...00 0a 5e 19 e2 b4 ...... 3Com Gigabit NIC (3C2000 Family)
===========================================================================
===========================================================================
Активные маршруты:
Сетевой адрес Маска сети Адрес шлюза Интерфейс Метрика
0.0.0.0 0.0.0.0 192.168.1.6 192.168.1.4 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4 1
192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4 1
192.168.2.0 255.255.255.0 192.168.2.1 192.168.2.1 1
192.168.2.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.2.255 255.255.255.255 192.168.2.1 192.168.2.1 1
192.168.4.0 255.255.255.0 192.168.4.2 192.168.4.2 1
192.168.4.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.4.255 255.255.255.255 192.168.4.2 192.168.4.2 1
217.9.144.0 255.255.240.0 192.168.1.6 192.168.1.4 1
224.0.0.0 224.0.0.0 192.168.1.4 192.168.1.4 1
224.0.0.0 224.0.0.0 192.168.2.1 192.168.2.1 1
224.0.0.0 224.0.0.0 192.168.4.2 192.168.4.2 1
255.255.255.255 255.255.255.255 192.168.2.1 192.168.2.1 1
Основной шлюз: 192.168.1.6
===========================================================================
Постоянные маршруты:
Отсутствует
192.168.1.6 is a ISA Server 2006. Host from Subnet4 ipconfig result: Настройка протокола IP для Windows 2000
Адаптер Ethernet Подключение по локальной сети:
DNS суффикс этого подключения . . :
IP-адрес . . . . . . . . . . . . : 192.168.4.1
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз . . . . . . . . . . : 192.168.4.2
Result of tracert 192.168.1.6 command from Subnet4 host: Трассировка маршрута к rbmail.city.kirov.ru [192.168.1.6] с максимальным числом прыжков 30:
1 <10 мс <10 мс <10 мс RBP4 [192.168.4.2]
2 * * * Превышен интервал ожидания для запроса.
3 * * * Превышен интервал ожидания для запроса.
4 * * * Превышен интервал ожидания для запроса.
5 * * * Превышен интервал ожидания для запроса.
<---- skip ---->
tracert 192.168.1.7 (test to another host) Трассировка маршрута к rbfs.city.kirov.ru [192.168.1.7] с максимальным числом прыжков 30:
1 1 ms <10 мс <10 мс RBP4 [192.168.4.2]
2 <10 мс <10 мс <10 мс rbfs.city.kirov.ru [192.168.1.7]
Трассировка завершена.
The situation with Subnet2 is similar Subnet4. P.S. I am sorry for Russian words. It is used Cyrillic 1251.
|
|
|
|
RE: Troubles with internal subnets :( - 25.Sep.2006 12:30:01 PM
|
|
|
Ten
Posts: 20
Joined: 28.Jul.2004
From: Russian, Kirov
Status: offline
|
Excuse me, has not absolutely understood your question.. :(
|
|
|
|
RE: Troubles with internal subnets :( - 26.Sep.2006 8:12:29 AM
|
|
|
Ten
Posts: 20
Joined: 28.Jul.2004
From: Russian, Kirov
Status: offline
|
I'm stupid... Thank you very much, Mr. Shinder! route add 192.168.2.0 mask 255.255.255.0 192.168.1.4
route add 192.168.4.0 mask 255.255.255.0 192.168.1.4 fixed my problem! For some reason I before have not guessed :( Thank you! Good luck! See you later :)
< Message edited by Ten -- 26.Sep.2006 8:15:24 AM >
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|