LAT/Route conflict, Win2kServer

  • Thread starter Thread starter David Bolt
  • Start date Start date
D

David Bolt

Getting a bit desperate here, and somewhat confused.
The server is connected to a hub by one nic, and to a Router by a second nic.
Because this is Small Business Server, we are using ISA Server for the firewalling etc.
Now, as long as no one attempts to access pages via IIS, all seems OK, but access to IIS pages results in messages indicating a conflict between the Windows Routing table and the LAT.
Here is the result of the Route PRINT (all metrics are 1):
===================================
Interface List
0x1 ...............MS TCP Loopback interface
0x2 ...xx xx xx xx xx xx .NDIS 5.0 driver (Microsoft's packet scheduler)
0x2 ...yy yy yy yy yy yy .NDIS 5.0 driver (Microsoft's packet scheduler)
===================================
Active Routes:
Network destination, Netmask, Gateway, Interface
0.0.0.0, 0.0.0.0, 192.168.0.9, 192.168.0.1
127.0.0.0, 255.0.0.0, 127.0.0.1, 127.0.0.1
192.168.0.0, 255.255.255.0, 192.168.0.1, 192.168.0.1
192.168.0.1, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.0.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
192.168.16.0, 255.255.255.0, 192.168.16.2, 192.168.16.2
192.168.16.2, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.16.255, 255.255.255.255, 192.168.16.2, 192.168.16.2
224.0.0.0, 224.0.0.0, 192.168.0.1, 192.168.0.1
224.0.0.0, 224.0.0.0, 192.168.16.2, 192.168.16.2
255.255.255.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
Default Gateway: 192.168.0.9
Persistent Routes: none
Now, both NICs have static IP addresses, 192.168.16.2 for the primary connecting the server to the hub and 192.168.0.1 for the secondary connecting the server to the router. The gateway 192.168.0.9 is on the router.

The default LAT is this:
The LAT table is currently:
10.0.0.0 - 10.255.255.255
169.254.0.0 - 169.254.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.0.255
192.168.16.0 - 192.168.16.255
but this causes conflicts.
The addresses 192.168.0.1 and 192.168.0.9 seem to be causing problems, but I do not understand why.
192.168.0.9 is a gateway on the router, which my mail software requires access to.
Any explanations, including internal and external interfaces, would be most helpful.
Thanks
Dave
 
Hi Dave,

Have you run the ICW-wizard from the SBS-console?
In the LAT, delete the 169-address, and the 192.168.0.xxx-range. The external IP-range should not be in the LAT.

Marina

"David Bolt" <[email protected]> schreef in bericht Getting a bit desperate here, and somewhat confused.
The server is connected to a hub by one nic, and to a Router by a second nic.
Because this is Small Business Server, we are using ISA Server for the firewalling etc.
Now, as long as no one attempts to access pages via IIS, all seems OK, but access to IIS pages results in messages indicating a conflict between the Windows Routing table and the LAT.
Here is the result of the Route PRINT (all metrics are 1):
===================================
Interface List
0x1 ...............MS TCP Loopback interface
0x2 ...xx xx xx xx xx xx .NDIS 5.0 driver (Microsoft's packet scheduler)
0x2 ...yy yy yy yy yy yy .NDIS 5.0 driver (Microsoft's packet scheduler)
===================================
Active Routes:
Network destination, Netmask, Gateway, Interface
0.0.0.0, 0.0.0.0, 192.168.0.9, 192.168.0.1
127.0.0.0, 255.0.0.0, 127.0.0.1, 127.0.0.1
192.168.0.0, 255.255.255.0, 192.168.0.1, 192.168.0.1
192.168.0.1, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.0.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
192.168.16.0, 255.255.255.0, 192.168.16.2, 192.168.16.2
192.168.16.2, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.16.255, 255.255.255.255, 192.168.16.2, 192.168.16.2
224.0.0.0, 224.0.0.0, 192.168.0.1, 192.168.0.1
224.0.0.0, 224.0.0.0, 192.168.16.2, 192.168.16.2
255.255.255.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
Default Gateway: 192.168.0.9
Persistent Routes: none
Now, both NICs have static IP addresses, 192.168.16.2 for the primary connecting the server to the hub and 192.168.0.1 for the secondary connecting the server to the router. The gateway 192.168.0.9 is on the router.

The default LAT is this:
The LAT table is currently:
10.0.0.0 - 10.255.255.255
169.254.0.0 - 169.254.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.0.255
192.168.16.0 - 192.168.16.255
but this causes conflicts.
The addresses 192.168.0.1 and 192.168.0.9 seem to be causing problems, but I do not understand why.
192.168.0.9 is a gateway on the router, which my mail software requires access to.
Any explanations, including internal and external interfaces, would be most helpful.
Thanks
Dave
 
Ran ICW, and picked up a couple of problems.
Now, 192.168.0.100 - 192.168.0.100 is in the LAT, which makes sense since it is the HP JetDirect.
192.168.0.0 - 192.168.255.255 is in the LAT, and I am uncertain about that.
When I go into the DHCP console it is apparently on 192.168.0.1, with the scope set to 192.168.16.0, which puzzles me a bit.
The user who connects to AOL is suddenly no longer able to connect.
The mail server is looking for a DNS server at 192.168.0.1 first, failing then looking at 192.168.16.2 and succeeding.
Route and LAT listings follow.
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...XX XX XX XX XX XX ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
0x3 ...YY YY YY YY YY ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.9 192.168.0.1 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 1
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.100 255.255.255.255 192.168.16.2 192.168.16.2 1
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 1
192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2 1
192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2 1
224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1
224.0.0.0 224.0.0.0 192.168.16.2 192.168.16.2 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
Default Gateway: 192.168.0.9
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.0.100 255.255.255.255 192.168.16.2 1

LAT:
From To Description
10.0.0.0 10.255.255.255
169.254.0.0 169.254.255.255
172.16.0.0 172.31.255.255
192.168.0.0 192.168.255.255
192.168.0.100 192.168.0.100
192.168.16.0 192.168.16.255

Any more pointers?
Thanks lots
Dave
Hi Dave,

Have you run the ICW-wizard from the SBS-console?
In the LAT, delete the 169-address, and the 192.168.0.xxx-range. The external IP-range should not be in the LAT.

Marina

"David Bolt" <[email protected]> schreef in bericht Getting a bit desperate here, and somewhat confused.
The server is connected to a hub by one nic, and to a Router by a second nic.
Because this is Small Business Server, we are using ISA Server for the firewalling etc.
Now, as long as no one attempts to access pages via IIS, all seems OK, but access to IIS pages results in messages indicating a conflict between the Windows Routing table and the LAT.
Here is the result of the Route PRINT (all metrics are 1):
===================================
Interface List
0x1 ...............MS TCP Loopback interface
0x2 ...xx xx xx xx xx xx .NDIS 5.0 driver (Microsoft's packet scheduler)
0x2 ...yy yy yy yy yy yy .NDIS 5.0 driver (Microsoft's packet scheduler)
===================================
Active Routes:
Network destination, Netmask, Gateway, Interface
0.0.0.0, 0.0.0.0, 192.168.0.9, 192.168.0.1
127.0.0.0, 255.0.0.0, 127.0.0.1, 127.0.0.1
192.168.0.0, 255.255.255.0, 192.168.0.1, 192.168.0.1
192.168.0.1, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.0.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
192.168.16.0, 255.255.255.0, 192.168.16.2, 192.168.16.2
192.168.16.2, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.16.255, 255.255.255.255, 192.168.16.2, 192.168.16.2
224.0.0.0, 224.0.0.0, 192.168.0.1, 192.168.0.1
224.0.0.0, 224.0.0.0, 192.168.16.2, 192.168.16.2
255.255.255.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
Default Gateway: 192.168.0.9
Persistent Routes: none
Now, both NICs have static IP addresses, 192.168.16.2 for the primary connecting the server to the hub and 192.168.0.1 for the secondary connecting the server to the router. The gateway 192.168.0.9 is on the router.

The default LAT is this:
The LAT table is currently:
10.0.0.0 - 10.255.255.255
169.254.0.0 - 169.254.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.0.255
192.168.16.0 - 192.168.16.255
but this causes conflicts.
The addresses 192.168.0.1 and 192.168.0.9 seem to be causing problems, but I do not understand why.
192.168.0.9 is a gateway on the router, which my mail software requires access to.
Any explanations, including internal and external interfaces, would be most helpful.
Thanks
Dave
 
Hi Dave,

Can you give the ipconfig/all from the server please?

Marina
"Dave" <[email protected]> schreef in bericht Ran ICW, and picked up a couple of problems.
Now, 192.168.0.100 - 192.168.0.100 is in the LAT, which makes sense since it is the HP JetDirect.
192.168.0.0 - 192.168.255.255 is in the LAT, and I am uncertain about that.
When I go into the DHCP console it is apparently on 192.168.0.1, with the scope set to 192.168.16.0, which puzzles me a bit.
The user who connects to AOL is suddenly no longer able to connect.
The mail server is looking for a DNS server at 192.168.0.1 first, failing then looking at 192.168.16.2 and succeeding.
Route and LAT listings follow.
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...XX XX XX XX XX XX ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
0x3 ...YY YY YY YY YY ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.9 192.168.0.1 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 1
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.100 255.255.255.255 192.168.16.2 192.168.16.2 1
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 1
192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2 1
192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2 1
224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1
224.0.0.0 224.0.0.0 192.168.16.2 192.168.16.2 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
Default Gateway: 192.168.0.9
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.0.100 255.255.255.255 192.168.16.2 1

LAT:
From To Description
10.0.0.0 10.255.255.255
169.254.0.0 169.254.255.255
172.16.0.0 172.31.255.255
192.168.0.0 192.168.255.255
192.168.0.100 192.168.0.100
192.168.16.0 192.168.16.255

Any more pointers?
Thanks lots
Dave
Hi Dave,

Have you run the ICW-wizard from the SBS-console?
In the LAT, delete the 169-address, and the 192.168.0.xxx-range. The external IP-range should not be in the LAT.

Marina

"David Bolt" <[email protected]> schreef in bericht Getting a bit desperate here, and somewhat confused.
The server is connected to a hub by one nic, and to a Router by a second nic.
Because this is Small Business Server, we are using ISA Server for the firewalling etc.
Now, as long as no one attempts to access pages via IIS, all seems OK, but access to IIS pages results in messages indicating a conflict between the Windows Routing table and the LAT.
Here is the result of the Route PRINT (all metrics are 1):
===================================
Interface List
0x1 ...............MS TCP Loopback interface
0x2 ...xx xx xx xx xx xx .NDIS 5.0 driver (Microsoft's packet scheduler)
0x2 ...yy yy yy yy yy yy .NDIS 5.0 driver (Microsoft's packet scheduler)
===================================
Active Routes:
Network destination, Netmask, Gateway, Interface
0.0.0.0, 0.0.0.0, 192.168.0.9, 192.168.0.1
127.0.0.0, 255.0.0.0, 127.0.0.1, 127.0.0.1
192.168.0.0, 255.255.255.0, 192.168.0.1, 192.168.0.1
192.168.0.1, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.0.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
192.168.16.0, 255.255.255.0, 192.168.16.2, 192.168.16.2
192.168.16.2, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.16.255, 255.255.255.255, 192.168.16.2, 192.168.16.2
224.0.0.0, 224.0.0.0, 192.168.0.1, 192.168.0.1
224.0.0.0, 224.0.0.0, 192.168.16.2, 192.168.16.2
255.255.255.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
Default Gateway: 192.168.0.9
Persistent Routes: none
Now, both NICs have static IP addresses, 192.168.16.2 for the primary connecting the server to the hub and 192.168.0.1 for the secondary connecting the server to the router. The gateway 192.168.0.9 is on the router.

The default LAT is this:
The LAT table is currently:
10.0.0.0 - 10.255.255.255
169.254.0.0 - 169.254.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.0.255
192.168.16.0 - 192.168.16.255
but this causes conflicts.
The addresses 192.168.0.1 and 192.168.0.9 seem to be causing problems, but I do not understand why.
192.168.0.9 is a gateway on the router, which my mail software requires access to.
Any explanations, including internal and external interfaces, would be most helpful.
Thanks
Dave
 
Marina,
Here it is.
Dave

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server
Primary DNS Suffix . . . . . . . : A.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : A.local

Ethernet adapter Router:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card 10/100 (SMC1211TX) #2
Physical Address. . . . . . . . . : YY-YY-YY-YY-YY

DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.9
DNS Servers . . . . . . . . . . . : 192.168.0.1
192.168.16.2
Primary WINS Server . . . . . . . : 192.168.0.9

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card 10/100 (SMC1211TX)
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.16.2
Primary WINS Server . . . . . . . : 192.168.16.2


Hi Dave,

Can you give the ipconfig/all from the server please?

Marina
"Dave" <[email protected]> schreef in bericht Ran ICW, and picked up a couple of problems.
Now, 192.168.0.100 - 192.168.0.100 is in the LAT, which makes sense since it is the HP JetDirect.
192.168.0.0 - 192.168.255.255 is in the LAT, and I am uncertain about that.
When I go into the DHCP console it is apparently on 192.168.0.1, with the scope set to 192.168.16.0, which puzzles me a bit.
The user who connects to AOL is suddenly no longer able to connect.
The mail server is looking for a DNS server at 192.168.0.1 first, failing then looking at 192.168.16.2 and succeeding.
Route and LAT listings follow.
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...XX XX XX XX XX XX ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
0x3 ...YY YY YY YY YY ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.9 192.168.0.1 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 1
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.100 255.255.255.255 192.168.16.2 192.168.16.2 1
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 1
192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2 1
192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2 1
224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1
224.0.0.0 224.0.0.0 192.168.16.2 192.168.16.2 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
Default Gateway: 192.168.0.9
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.0.100 255.255.255.255 192.168.16.2 1

LAT:
From To Description
10.0.0.0 10.255.255.255
169.254.0.0 169.254.255.255
172.16.0.0 172.31.255.255
192.168.0.0 192.168.255.255
192.168.0.100 192.168.0.100
192.168.16.0 192.168.16.255

Any more pointers?
Thanks lots
Dave
Hi Dave,

Have you run the ICW-wizard from the SBS-console?
In the LAT, delete the 169-address, and the 192.168.0.xxx-range. The external IP-range should not be in the LAT.

Marina

"David Bolt" <[email protected]> schreef in bericht Getting a bit desperate here, and somewhat confused.
The server is connected to a hub by one nic, and to a Router by a second nic.
Because this is Small Business Server, we are using ISA Server for the firewalling etc.
Now, as long as no one attempts to access pages via IIS, all seems OK, but access to IIS pages results in messages indicating a conflict between the Windows Routing table and the LAT.
Here is the result of the Route PRINT (all metrics are 1):
===================================
Interface List
0x1 ...............MS TCP Loopback interface
0x2 ...xx xx xx xx xx xx .NDIS 5.0 driver (Microsoft's packet scheduler)
0x2 ...yy yy yy yy yy yy .NDIS 5.0 driver (Microsoft's packet scheduler)
===================================
Active Routes:
Network destination, Netmask, Gateway, Interface
0.0.0.0, 0.0.0.0, 192.168.0.9, 192.168.0.1
127.0.0.0, 255.0.0.0, 127.0.0.1, 127.0.0.1
192.168.0.0, 255.255.255.0, 192.168.0.1, 192.168.0.1
192.168.0.1, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.0.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
192.168.16.0, 255.255.255.0, 192.168.16.2, 192.168.16.2
192.168.16.2, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.16.255, 255.255.255.255, 192.168.16.2, 192.168.16.2
224.0.0.0, 224.0.0.0, 192.168.0.1, 192.168.0.1
224.0.0.0, 224.0.0.0, 192.168.16.2, 192.168.16.2
255.255.255.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
Default Gateway: 192.168.0.9
Persistent Routes: none
Now, both NICs have static IP addresses, 192.168.16.2 for the primary connecting the server to the hub and 192.168.0.1 for the secondary connecting the server to the router. The gateway 192.168.0.9 is on the router.

The default LAT is this:
The LAT table is currently:
10.0.0.0 - 10.255.255.255
169.254.0.0 - 169.254.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.0.255
192.168.16.0 - 192.168.16.255
but this causes conflicts.
The addresses 192.168.0.1 and 192.168.0.9 seem to be causing problems, but I do not understand why.
192.168.0.9 is a gateway on the router, which my mail software requires access to.
Any explanations, including internal and external interfaces, would be most helpful.
Thanks
Dave
 
Hi Dave,

Internal nic is okay.
External nic should be:
IP 192.168.0.1
Sub 255.255.255.0
GW 192.168.0.9
DNS 192.168.16.2

On the external nic only TCP/IP should be bound, no WINS. On DNS-tab there should be no check at 'register in DNS' and 'suffix'.

Check the bindingorder in Network Connections, advanced, advanced and make sure the internal nic is on top.

In your LAT only the 192.168.16.x range should be there. You can leave the 10 and 172-range, but delete the others.

Marina

"Dave" <[email protected]> schreef in bericht Marina,
Here it is.
Dave

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server
Primary DNS Suffix . . . . . . . : A.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : A.local

Ethernet adapter Router:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card 10/100 (SMC1211TX) #2
Physical Address. . . . . . . . . : YY-YY-YY-YY-YY

DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.9
DNS Servers . . . . . . . . . . . : 192.168.0.1
192.168.16.2
Primary WINS Server . . . . . . . : 192.168.0.9

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card 10/100 (SMC1211TX)
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.16.2
Primary WINS Server . . . . . . . : 192.168.16.2


Hi Dave,

Can you give the ipconfig/all from the server please?

Marina
"Dave" <[email protected]> schreef in bericht Ran ICW, and picked up a couple of problems.
Now, 192.168.0.100 - 192.168.0.100 is in the LAT, which makes sense since it is the HP JetDirect.
192.168.0.0 - 192.168.255.255 is in the LAT, and I am uncertain about that.
When I go into the DHCP console it is apparently on 192.168.0.1, with the scope set to 192.168.16.0, which puzzles me a bit.
The user who connects to AOL is suddenly no longer able to connect.
The mail server is looking for a DNS server at 192.168.0.1 first, failing then looking at 192.168.16.2 and succeeding.
Route and LAT listings follow.
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...XX XX XX XX XX XX ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
0x3 ...YY YY YY YY YY ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.9 192.168.0.1 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 1
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.100 255.255.255.255 192.168.16.2 192.168.16.2 1
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 1
192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2 1
192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2 1
224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1
224.0.0.0 224.0.0.0 192.168.16.2 192.168.16.2 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
Default Gateway: 192.168.0.9
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.0.100 255.255.255.255 192.168.16.2 1

LAT:
From To Description
10.0.0.0 10.255.255.255
169.254.0.0 169.254.255.255
172.16.0.0 172.31.255.255
192.168.0.0 192.168.255.255
192.168.0.100 192.168.0.100
192.168.16.0 192.168.16.255

Any more pointers?
Thanks lots
Dave
Hi Dave,

Have you run the ICW-wizard from the SBS-console?
In the LAT, delete the 169-address, and the 192.168.0.xxx-range. The external IP-range should not be in the LAT.

Marina

"David Bolt" <[email protected]> schreef in bericht Getting a bit desperate here, and somewhat confused.
The server is connected to a hub by one nic, and to a Router by a second nic.
Because this is Small Business Server, we are using ISA Server for the firewalling etc.
Now, as long as no one attempts to access pages via IIS, all seems OK, but access to IIS pages results in messages indicating a conflict between the Windows Routing table and the LAT.
Here is the result of the Route PRINT (all metrics are 1):
===================================
Interface List
0x1 ...............MS TCP Loopback interface
0x2 ...xx xx xx xx xx xx .NDIS 5.0 driver (Microsoft's packet scheduler)
0x2 ...yy yy yy yy yy yy .NDIS 5.0 driver (Microsoft's packet scheduler)
===================================
Active Routes:
Network destination, Netmask, Gateway, Interface
0.0.0.0, 0.0.0.0, 192.168.0.9, 192.168.0.1
127.0.0.0, 255.0.0.0, 127.0.0.1, 127.0.0.1
192.168.0.0, 255.255.255.0, 192.168.0.1, 192.168.0.1
192.168.0.1, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.0.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
192.168.16.0, 255.255.255.0, 192.168.16.2, 192.168.16.2
192.168.16.2, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.16.255, 255.255.255.255, 192.168.16.2, 192.168.16.2
224.0.0.0, 224.0.0.0, 192.168.0.1, 192.168.0.1
224.0.0.0, 224.0.0.0, 192.168.16.2, 192.168.16.2
255.255.255.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
Default Gateway: 192.168.0.9
Persistent Routes: none
Now, both NICs have static IP addresses, 192.168.16.2 for the primary connecting the server to the hub and 192.168.0.1 for the secondary connecting the server to the router. The gateway 192.168.0.9 is on the router.

The default LAT is this:
The LAT table is currently:
10.0.0.0 - 10.255.255.255
169.254.0.0 - 169.254.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.0.255
192.168.16.0 - 192.168.16.255
but this causes conflicts.
The addresses 192.168.0.1 and 192.168.0.9 seem to be causing problems, but I do not understand why.
192.168.0.9 is a gateway on the router, which my mail software requires access to.
Any explanations, including internal and external interfaces, would be most helpful.
Thanks
Dave
 
Marina,
OK, did that. Works somewhat better. <VBG>
Thanks!
I even managed to get auto-enrolment for certificates to work.

Now, the following problems are revealed.
IIS Web Service wont start, I have found info that indicates I need to see what is using what ports, so not stuck on that one yet.
I can not browse to the HP JetDirect management console on 192.168.0.100 from the server, not yet tried from another machine, but suspect I will be able to. Leaves me puzzled if that's how it works out.
I can not get into these newsgroups from the server using Outlook Express. I can from other PCs on the network with no problems. Also leaves me puzzled.
DHCP is running, but when I attempt to connect via VPN I get an error message in the logs saying that DHCP Server can not be found. I also see messages at intervals saying that DHCP is not found and a default address will be used for connecting clients.
Any thoughts about what I should be looking for?
Regards,
Dave
Hi Dave,

Internal nic is okay.
External nic should be:
IP 192.168.0.1
Sub 255.255.255.0
GW 192.168.0.9
DNS 192.168.16.2

On the external nic only TCP/IP should be bound, no WINS. On DNS-tab there should be no check at 'register in DNS' and 'suffix'.

Check the bindingorder in Network Connections, advanced, advanced and make sure the internal nic is on top.

In your LAT only the 192.168.16.x range should be there. You can leave the 10 and 172-range, but delete the others.

Marina

"Dave" <[email protected]> schreef in bericht Marina,
Here it is.
Dave

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server
Primary DNS Suffix . . . . . . . : A.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : A.local

Ethernet adapter Router:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card 10/100 (SMC1211TX) #2
Physical Address. . . . . . . . . : YY-YY-YY-YY-YY

DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.9
DNS Servers . . . . . . . . . . . : 192.168.0.1
192.168.16.2
Primary WINS Server . . . . . . . : 192.168.0.9

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card 10/100 (SMC1211TX)
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.16.2
Primary WINS Server . . . . . . . : 192.168.16.2


Hi Dave,

Can you give the ipconfig/all from the server please?

Marina
"Dave" <[email protected]> schreef in bericht Ran ICW, and picked up a couple of problems.
Now, 192.168.0.100 - 192.168.0.100 is in the LAT, which makes sense since it is the HP JetDirect.
192.168.0.0 - 192.168.255.255 is in the LAT, and I am uncertain about that.
When I go into the DHCP console it is apparently on 192.168.0.1, with the scope set to 192.168.16.0, which puzzles me a bit.
The user who connects to AOL is suddenly no longer able to connect.
The mail server is looking for a DNS server at 192.168.0.1 first, failing then looking at 192.168.16.2 and succeeding.
Route and LAT listings follow.
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...XX XX XX XX XX XX ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
0x3 ...YY YY YY YY YY ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.9 192.168.0.1 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 1
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.100 255.255.255.255 192.168.16.2 192.168.16.2 1
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 1
192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2 1
192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2 1
224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1
224.0.0.0 224.0.0.0 192.168.16.2 192.168.16.2 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
Default Gateway: 192.168.0.9
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.0.100 255.255.255.255 192.168.16.2 1

LAT:
From To Description
10.0.0.0 10.255.255.255
169.254.0.0 169.254.255.255
172.16.0.0 172.31.255.255
192.168.0.0 192.168.255.255
192.168.0.100 192.168.0.100
192.168.16.0 192.168.16.255

Any more pointers?
Thanks lots
Dave
Hi Dave,

Have you run the ICW-wizard from the SBS-console?
In the LAT, delete the 169-address, and the 192.168.0.xxx-range. The external IP-range should not be in the LAT.

Marina

"David Bolt" <[email protected]> schreef in bericht Getting a bit desperate here, and somewhat confused.
The server is connected to a hub by one nic, and to a Router by a second nic.
Because this is Small Business Server, we are using ISA Server for the firewalling etc.
Now, as long as no one attempts to access pages via IIS, all seems OK, but access to IIS pages results in messages indicating a conflict between the Windows Routing table and the LAT.
Here is the result of the Route PRINT (all metrics are 1):
===================================
Interface List
0x1 ...............MS TCP Loopback interface
0x2 ...xx xx xx xx xx xx .NDIS 5.0 driver (Microsoft's packet scheduler)
0x2 ...yy yy yy yy yy yy .NDIS 5.0 driver (Microsoft's packet scheduler)
===================================
Active Routes:
Network destination, Netmask, Gateway, Interface
0.0.0.0, 0.0.0.0, 192.168.0.9, 192.168.0.1
127.0.0.0, 255.0.0.0, 127.0.0.1, 127.0.0.1
192.168.0.0, 255.255.255.0, 192.168.0.1, 192.168.0.1
192.168.0.1, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.0.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
192.168.16.0, 255.255.255.0, 192.168.16.2, 192.168.16.2
192.168.16.2, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.16.255, 255.255.255.255, 192.168.16.2, 192.168.16.2
224.0.0.0, 224.0.0.0, 192.168.0.1, 192.168.0.1
224.0.0.0, 224.0.0.0, 192.168.16.2, 192.168.16.2
255.255.255.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
Default Gateway: 192.168.0.9
Persistent Routes: none
Now, both NICs have static IP addresses, 192.168.16.2 for the primary connecting the server to the hub and 192.168.0.1 for the secondary connecting the server to the router. The gateway 192.168.0.9 is on the router.

The default LAT is this:
The LAT table is currently:
10.0.0.0 - 10.255.255.255
169.254.0.0 - 169.254.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.0.255
192.168.16.0 - 192.168.16.255
but this causes conflicts.
The addresses 192.168.0.1 and 192.168.0.9 seem to be causing problems, but I do not understand why.
192.168.0.9 is a gateway on the router, which my mail software requires access to.
Any explanations, including internal and external interfaces, would be most helpful.
Thanks
Dave
 
Hi David,

Have you run the IIS-wizard from the SBS-console.
I wouldn't worry about the Jetdirect, I've never really liked that stuff.

If your would like to run Outlook Express from the server (mind you, it is not recommended to use your server as a workstation!), you will have to make some modifications in ISA. I would have to look it up for you.

In the RRAS configuration, did you setup that RAS-clients will get an IP from the DHCP server, and that it should only look to your internal lan? You also could setup a static pool for this (but that's not necessary).

Marina

"David Bolt" <[email protected]> schreef in bericht Marina,
OK, did that. Works somewhat better. <VBG>
Thanks!
I even managed to get auto-enrolment for certificates to work.

Now, the following problems are revealed.
IIS Web Service wont start, I have found info that indicates I need to see what is using what ports, so not stuck on that one yet.
I can not browse to the HP JetDirect management console on 192.168.0.100 from the server, not yet tried from another machine, but suspect I will be able to. Leaves me puzzled if that's how it works out.
I can not get into these newsgroups from the server using Outlook Express. I can from other PCs on the network with no problems. Also leaves me puzzled.
DHCP is running, but when I attempt to connect via VPN I get an error message in the logs saying that DHCP Server can not be found. I also see messages at intervals saying that DHCP is not found and a default address will be used for connecting clients.
Any thoughts about what I should be looking for?
Regards,
Dave
Hi Dave,

Internal nic is okay.
External nic should be:
IP 192.168.0.1
Sub 255.255.255.0
GW 192.168.0.9
DNS 192.168.16.2

On the external nic only TCP/IP should be bound, no WINS. On DNS-tab there should be no check at 'register in DNS' and 'suffix'.

Check the bindingorder in Network Connections, advanced, advanced and make sure the internal nic is on top.

In your LAT only the 192.168.16.x range should be there. You can leave the 10 and 172-range, but delete the others.

Marina

"Dave" <[email protected]> schreef in bericht Marina,
Here it is.
Dave

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server
Primary DNS Suffix . . . . . . . : A.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : A.local

Ethernet adapter Router:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card 10/100 (SMC1211TX) #2
Physical Address. . . . . . . . . : YY-YY-YY-YY-YY

DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.9
DNS Servers . . . . . . . . . . . : 192.168.0.1
192.168.16.2
Primary WINS Server . . . . . . . : 192.168.0.9

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card 10/100 (SMC1211TX)
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.16.2
Primary WINS Server . . . . . . . : 192.168.16.2


Hi Dave,

Can you give the ipconfig/all from the server please?

Marina
"Dave" <[email protected]> schreef in bericht Ran ICW, and picked up a couple of problems.
Now, 192.168.0.100 - 192.168.0.100 is in the LAT, which makes sense since it is the HP JetDirect.
192.168.0.0 - 192.168.255.255 is in the LAT, and I am uncertain about that.
When I go into the DHCP console it is apparently on 192.168.0.1, with the scope set to 192.168.16.0, which puzzles me a bit.
The user who connects to AOL is suddenly no longer able to connect.
The mail server is looking for a DNS server at 192.168.0.1 first, failing then looking at 192.168.16.2 and succeeding.
Route and LAT listings follow.
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...XX XX XX XX XX XX ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
0x3 ...YY YY YY YY YY ...... NDIS 5.0 driver (Microsoft's Packet Scheduler)
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.9 192.168.0.1 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 1
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.100 255.255.255.255 192.168.16.2 192.168.16.2 1
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 1
192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2 1
192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2 1
224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1
224.0.0.0 224.0.0.0 192.168.16.2 192.168.16.2 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
Default Gateway: 192.168.0.9
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.0.100 255.255.255.255 192.168.16.2 1

LAT:
From To Description
10.0.0.0 10.255.255.255
169.254.0.0 169.254.255.255
172.16.0.0 172.31.255.255
192.168.0.0 192.168.255.255
192.168.0.100 192.168.0.100
192.168.16.0 192.168.16.255

Any more pointers?
Thanks lots
Dave
Hi Dave,

Have you run the ICW-wizard from the SBS-console?
In the LAT, delete the 169-address, and the 192.168.0.xxx-range. The external IP-range should not be in the LAT.

Marina

"David Bolt" <[email protected]> schreef in bericht Getting a bit desperate here, and somewhat confused.
The server is connected to a hub by one nic, and to a Router by a second nic.
Because this is Small Business Server, we are using ISA Server for the firewalling etc.
Now, as long as no one attempts to access pages via IIS, all seems OK, but access to IIS pages results in messages indicating a conflict between the Windows Routing table and the LAT.
Here is the result of the Route PRINT (all metrics are 1):
===================================
Interface List
0x1 ...............MS TCP Loopback interface
0x2 ...xx xx xx xx xx xx .NDIS 5.0 driver (Microsoft's packet scheduler)
0x2 ...yy yy yy yy yy yy .NDIS 5.0 driver (Microsoft's packet scheduler)
===================================
Active Routes:
Network destination, Netmask, Gateway, Interface
0.0.0.0, 0.0.0.0, 192.168.0.9, 192.168.0.1
127.0.0.0, 255.0.0.0, 127.0.0.1, 127.0.0.1
192.168.0.0, 255.255.255.0, 192.168.0.1, 192.168.0.1
192.168.0.1, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.0.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
192.168.16.0, 255.255.255.0, 192.168.16.2, 192.168.16.2
192.168.16.2, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.168.16.255, 255.255.255.255, 192.168.16.2, 192.168.16.2
224.0.0.0, 224.0.0.0, 192.168.0.1, 192.168.0.1
224.0.0.0, 224.0.0.0, 192.168.16.2, 192.168.16.2
255.255.255.255, 255.255.255.255, 192.168.0.1, 192.168.0.1
Default Gateway: 192.168.0.9
Persistent Routes: none
Now, both NICs have static IP addresses, 192.168.16.2 for the primary connecting the server to the hub and 192.168.0.1 for the secondary connecting the server to the router. The gateway 192.168.0.9 is on the router.

The default LAT is this:
The LAT table is currently:
10.0.0.0 - 10.255.255.255
169.254.0.0 - 169.254.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.0.255
192.168.16.0 - 192.168.16.255
but this causes conflicts.
The addresses 192.168.0.1 and 192.168.0.9 seem to be causing problems, but I do not understand why.
192.168.0.9 is a gateway on the router, which my mail software requires access to.
Any explanations, including internal and external interfaces, would be most helpful.
Thanks
Dave
 
Marina, Hello again!
Yes, I did run the IIS wizard. All it does is restrict to a particular ip address, I used 192.168.16.2
I agree about not using the server as a workstation, but with all the fun I am having it is very useful to be able to go to the newsgroups etc from the server, since it is the only computer in that room. If you have any idea where to find that information I would be interested.
I have now made sure that RAS clients will get IP from DHCP, and internal LAN. I also found some settings to do with enabling VPN that I thought I had already set.
I found a nice document that told me I have to set IIS to publish the web pages using port 81, which should have been a bit more easily found out. Sometimes I despair at MS's documentation. All the information is in there somewhere, but finding it can be 'difficult'
Anyway, I think your help has got me past my worst problems for now. Thanks.
Dave
Hi David,

Have you run the IIS-wizard from the SBS-console.
I wouldn't worry about the Jetdirect, I've never really liked that stuff.

If your would like to run Outlook Express from the server (mind you, it is not recommended to use your server as a workstation!), you will have to make some modifications in ISA. I would have to look it up for you.

In the RRAS configuration, did you setup that RAS-clients will get an IP from the DHCP server, and that it should only look to your internal lan? You also could setup a static pool for this (but that's not necessary).

Marina
 
Hi David,

We gotta stop meeting like this ;-)

Did you already know about www.smallbizserver.net and the microsoft.public.backoffice.smallbiz2000 newsgroup? Have a look there anyway.

About OE on the server: I know you'll have to add some serverrules in ISA, but I would have to look it up for you. (You are running antivirus, right?)
I'll do that later tonight or tomorrow.

Marina

"David Bolt" <[email protected]> schreef in bericht Marina, Hello again!
Yes, I did run the IIS wizard. All it does is restrict to a particular ip address, I used 192.168.16.2
I agree about not using the server as a workstation, but with all the fun I am having it is very useful to be able to go to the newsgroups etc from the server, since it is the only computer in that room. If you have any idea where to find that information I would be interested.
I have now made sure that RAS clients will get IP from DHCP, and internal LAN. I also found some settings to do with enabling VPN that I thought I had already set.
I found a nice document that told me I have to set IIS to publish the web pages using port 81, which should have been a bit more easily found out. Sometimes I despair at MS's documentation. All the information is in there somewhere, but finding it can be 'difficult'
Anyway, I think your help has got me past my worst problems for now. Thanks.
Dave
Hi David,

Have you run the IIS-wizard from the SBS-console.
I wouldn't worry about the Jetdirect, I've never really liked that stuff.

If your would like to run Outlook Express from the server (mind you, it is not recommended to use your server as a workstation!), you will have to make some modifications in ISA. I would have to look it up for you.

In the RRAS configuration, did you setup that RAS-clients will get an IP from the DHCP server, and that it should only look to your internal lan? You also could setup a static pool for this (but that's not necessary).

Marina
 
Marina,
Hello again.
I'll check up those locations.
Yes, I am running antivirus, managed to get something on the network while installing it but it's working fine now.
The thing that surprises me is that I have no problem using OE on one of the workstations as a newsreader, and when the network configuration that we have already worked through was incorrect I could access newsgroups from the server as well.
Anyway, no further access 'till Monday so no panic.
Thanks again
Dave

Hi David,

We gotta stop meeting like this ;-)

Did you already know about www.smallbizserver.net and the microsoft.public.backoffice.smallbiz2000 newsgroup? Have a look there anyway.

About OE on the server: I know you'll have to add some serverrules in ISA, but I would have to look it up for you. (You are running antivirus, right?)
I'll do that later tonight or tomorrow.

Marina

"David Bolt" <[email protected]> schreef in bericht Marina, Hello again!
Yes, I did run the IIS wizard. All it does is restrict to a particular ip address, I used 192.168.16.2
I agree about not using the server as a workstation, but with all the fun I am having it is very useful to be able to go to the newsgroups etc from the server, since it is the only computer in that room. If you have any idea where to find that information I would be interested.
I have now made sure that RAS clients will get IP from DHCP, and internal LAN. I also found some settings to do with enabling VPN that I thought I had already set.
I found a nice document that told me I have to set IIS to publish the web pages using port 81, which should have been a bit more easily found out. Sometimes I despair at MS's documentation. All the information is in there somewhere, but finding it can be 'difficult'
Anyway, I think your help has got me past my worst problems for now. Thanks.
Dave
Hi David,

Have you run the IIS-wizard from the SBS-console.
I wouldn't worry about the Jetdirect, I've never really liked that stuff.

If your would like to run Outlook Express from the server (mind you, it is not recommended to use your server as a workstation!), you will have to make some modifications in ISA. I would have to look it up for you.

In the RRAS configuration, did you setup that RAS-clients will get an IP from the DHCP server, and that it should only look to your internal lan? You also could setup a static pool for this (but that's not necessary).

Marina
 
Hi David,

ISA is preventing you from accessing the newsgroups on the server. That's why you had to install the Firewall Client on the workstations, so you're able to. Just like I said, now that ISA is doing it's job, you just have to make some modifications to be able to access the newsgroups from the server. I'll get them for you, it's not that hard.

Marina

"David Bolt" <[email protected]> schreef in bericht Marina,
Hello again.
I'll check up those locations.
Yes, I am running antivirus, managed to get something on the network while installing it but it's working fine now.
The thing that surprises me is that I have no problem using OE on one of the workstations as a newsreader, and when the network configuration that we have already worked through was incorrect I could access newsgroups from the server as well.
Anyway, no further access 'till Monday so no panic.
Thanks again
Dave

Hi David,

We gotta stop meeting like this ;-)

Did you already know about www.smallbizserver.net and the microsoft.public.backoffice.smallbiz2000 newsgroup? Have a look there anyway.

About OE on the server: I know you'll have to add some serverrules in ISA, but I would have to look it up for you. (You are running antivirus, right?)
I'll do that later tonight or tomorrow.

Marina

"David Bolt" <[email protected]> schreef in bericht Marina, Hello again!
Yes, I did run the IIS wizard. All it does is restrict to a particular ip address, I used 192.168.16.2
I agree about not using the server as a workstation, but with all the fun I am having it is very useful to be able to go to the newsgroups etc from the server, since it is the only computer in that room. If you have any idea where to find that information I would be interested.
I have now made sure that RAS clients will get IP from DHCP, and internal LAN. I also found some settings to do with enabling VPN that I thought I had already set.
I found a nice document that told me I have to set IIS to publish the web pages using port 81, which should have been a bit more easily found out. Sometimes I despair at MS's documentation. All the information is in there somewhere, but finding it can be 'difficult'
Anyway, I think your help has got me past my worst problems for now. Thanks.
Dave
Hi David,

Have you run the IIS-wizard from the SBS-console.
I wouldn't worry about the Jetdirect, I've never really liked that stuff.

If your would like to run Outlook Express from the server (mind you, it is not recommended to use your server as a workstation!), you will have to make some modifications in ISA. I would have to look it up for you.

In the RRAS configuration, did you setup that RAS-clients will get an IP from the DHCP server, and that it should only look to your internal lan? You also could setup a static pool for this (but that's not necessary).

Marina
 
Hi David,

In ISA, drill down to servers and arrays, servername, access policy, ip packet filters.
Create a new packet filter, custom, TCP outbound, internal port dynamic, external port fixed 119.

Will this work for you?

Marina
"David Bolt" <[email protected]> schreef in bericht Marina,
Hello again.
I'll check up those locations.
Yes, I am running antivirus, managed to get something on the network while installing it but it's working fine now.
The thing that surprises me is that I have no problem using OE on one of the workstations as a newsreader, and when the network configuration that we have already worked through was incorrect I could access newsgroups from the server as well.
Anyway, no further access 'till Monday so no panic.
Thanks again
Dave

Hi David,

We gotta stop meeting like this ;-)

Did you already know about www.smallbizserver.net and the microsoft.public.backoffice.smallbiz2000 newsgroup? Have a look there anyway.

About OE on the server: I know you'll have to add some serverrules in ISA, but I would have to look it up for you. (You are running antivirus, right?)
I'll do that later tonight or tomorrow.

Marina

"David Bolt" <[email protected]> schreef in bericht Marina, Hello again!
Yes, I did run the IIS wizard. All it does is restrict to a particular ip address, I used 192.168.16.2
I agree about not using the server as a workstation, but with all the fun I am having it is very useful to be able to go to the newsgroups etc from the server, since it is the only computer in that room. If you have any idea where to find that information I would be interested.
I have now made sure that RAS clients will get IP from DHCP, and internal LAN. I also found some settings to do with enabling VPN that I thought I had already set.
I found a nice document that told me I have to set IIS to publish the web pages using port 81, which should have been a bit more easily found out. Sometimes I despair at MS's documentation. All the information is in there somewhere, but finding it can be 'difficult'
Anyway, I think your help has got me past my worst problems for now. Thanks.
Dave
Hi David,

Have you run the IIS-wizard from the SBS-console.
I wouldn't worry about the Jetdirect, I've never really liked that stuff.

If your would like to run Outlook Express from the server (mind you, it is not recommended to use your server as a workstation!), you will have to make some modifications in ISA. I would have to look it up for you.

In the RRAS configuration, did you setup that RAS-clients will get an IP from the DHCP server, and that it should only look to your internal lan? You also could setup a static pool for this (but that's not necessary).

Marina
 
Hello Marina,
Once again with the good eh?
I'll try that first thing in the morning.
Thanks a lot
Dave
Hi David,

In ISA, drill down to servers and arrays, servername, access policy, ip packet filters.
Create a new packet filter, custom, TCP outbound, internal port dynamic, external port fixed 119.

Will this work for you?

Marina
"David Bolt" <[email protected]> schreef in bericht Marina,
Hello again.
I'll check up those locations.
Yes, I am running antivirus, managed to get something on the network while installing it but it's working fine now.
The thing that surprises me is that I have no problem using OE on one of the workstations as a newsreader, and when the network configuration that we have already worked through was incorrect I could access newsgroups from the server as well.
Anyway, no further access 'till Monday so no panic.
Thanks again
Dave

Hi David,

We gotta stop meeting like this ;-)

Did you already know about www.smallbizserver.net and the microsoft.public.backoffice.smallbiz2000 newsgroup? Have a look there anyway.

About OE on the server: I know you'll have to add some serverrules in ISA, but I would have to look it up for you. (You are running antivirus, right?)
I'll do that later tonight or tomorrow.

Marina

"David Bolt" <[email protected]> schreef in bericht Marina, Hello again!
Yes, I did run the IIS wizard. All it does is restrict to a particular ip address, I used 192.168.16.2
I agree about not using the server as a workstation, but with all the fun I am having it is very useful to be able to go to the newsgroups etc from the server, since it is the only computer in that room. If you have any idea where to find that information I would be interested.
I have now made sure that RAS clients will get IP from DHCP, and internal LAN. I also found some settings to do with enabling VPN that I thought I had already set.
I found a nice document that told me I have to set IIS to publish the web pages using port 81, which should have been a bit more easily found out. Sometimes I despair at MS's documentation. All the information is in there somewhere, but finding it can be 'difficult'
Anyway, I think your help has got me past my worst problems for now. Thanks.
Dave
Hi David,

Have you run the IIS-wizard from the SBS-console.
I wouldn't worry about the Jetdirect, I've never really liked that stuff.

If your would like to run Outlook Express from the server (mind you, it is not recommended to use your server as a workstation!), you will have to make some modifications in ISA. I would have to look it up for you.

In the RRAS configuration, did you setup that RAS-clients will get an IP from the DHCP server, and that it should only look to your internal lan? You also could setup a static pool for this (but that's not necessary).

Marina
 
Umm... that should have been 'once again with the goods'
Dave
Hi David,

In ISA, drill down to servers and arrays, servername, access policy, ip packet filters.
Create a new packet filter, custom, TCP outbound, internal port dynamic, external port fixed 119.

Will this work for you?

Marina
"David Bolt" <[email protected]> schreef in bericht Marina,
Hello again.
I'll check up those locations.
Yes, I am running antivirus, managed to get something on the network while installing it but it's working fine now.
The thing that surprises me is that I have no problem using OE on one of the workstations as a newsreader, and when the network configuration that we have already worked through was incorrect I could access newsgroups from the server as well.
Anyway, no further access 'till Monday so no panic.
Thanks again
Dave

Hi David,

We gotta stop meeting like this ;-)

Did you already know about www.smallbizserver.net and the microsoft.public.backoffice.smallbiz2000 newsgroup? Have a look there anyway.

About OE on the server: I know you'll have to add some serverrules in ISA, but I would have to look it up for you. (You are running antivirus, right?)
I'll do that later tonight or tomorrow.

Marina

"David Bolt" <[email protected]> schreef in bericht Marina, Hello again!
Yes, I did run the IIS wizard. All it does is restrict to a particular ip address, I used 192.168.16.2
I agree about not using the server as a workstation, but with all the fun I am having it is very useful to be able to go to the newsgroups etc from the server, since it is the only computer in that room. If you have any idea where to find that information I would be interested.
I have now made sure that RAS clients will get IP from DHCP, and internal LAN. I also found some settings to do with enabling VPN that I thought I had already set.
I found a nice document that told me I have to set IIS to publish the web pages using port 81, which should have been a bit more easily found out. Sometimes I despair at MS's documentation. All the information is in there somewhere, but finding it can be 'difficult'
Anyway, I think your help has got me past my worst problems for now. Thanks.
Dave
Hi David,

Have you run the IIS-wizard from the SBS-console.
I wouldn't worry about the Jetdirect, I've never really liked that stuff.

If your would like to run Outlook Express from the server (mind you, it is not recommended to use your server as a workstation!), you will have to make some modifications in ISA. I would have to look it up for you.

In the RRAS configuration, did you setup that RAS-clients will get an IP from the DHCP server, and that it should only look to your internal lan? You also could setup a static pool for this (but that's not necessary).

Marina
 
Marina,
Yep! That works fine.
Thanks
Dave
Hi David,

In ISA, drill down to servers and arrays, servername, access policy, ip packet filters.
Create a new packet filter, custom, TCP outbound, internal port dynamic, external port fixed 119.

Will this work for you?

Marina
"David Bolt" <[email protected]> schreef in bericht Marina,
Hello again.
I'll check up those locations.
Yes, I am running antivirus, managed to get something on the network while installing it but it's working fine now.
The thing that surprises me is that I have no problem using OE on one of the workstations as a newsreader, and when the network configuration that we have already worked through was incorrect I could access newsgroups from the server as well.
Anyway, no further access 'till Monday so no panic.
Thanks again
Dave

Hi David,

We gotta stop meeting like this ;-)

Did you already know about www.smallbizserver.net and the microsoft.public.backoffice.smallbiz2000 newsgroup? Have a look there anyway.

About OE on the server: I know you'll have to add some serverrules in ISA, but I would have to look it up for you. (You are running antivirus, right?)
I'll do that later tonight or tomorrow.

Marina

"David Bolt" <[email protected]> schreef in bericht Marina, Hello again!
Yes, I did run the IIS wizard. All it does is restrict to a particular ip address, I used 192.168.16.2
I agree about not using the server as a workstation, but with all the fun I am having it is very useful to be able to go to the newsgroups etc from the server, since it is the only computer in that room. If you have any idea where to find that information I would be interested.
I have now made sure that RAS clients will get IP from DHCP, and internal LAN. I also found some settings to do with enabling VPN that I thought I had already set.
I found a nice document that told me I have to set IIS to publish the web pages using port 81, which should have been a bit more easily found out. Sometimes I despair at MS's documentation. All the information is in there somewhere, but finding it can be 'difficult'
Anyway, I think your help has got me past my worst problems for now. Thanks.
Dave
Hi David,

Have you run the IIS-wizard from the SBS-console.
I wouldn't worry about the Jetdirect, I've never really liked that stuff.

If your would like to run Outlook Express from the server (mind you, it is not recommended to use your server as a workstation!), you will have to make some modifications in ISA. I would have to look it up for you.

In the RRAS configuration, did you setup that RAS-clients will get an IP from the DHCP server, and that it should only look to your internal lan? You also could setup a static pool for this (but that's not necessary).

Marina
 
Great!
"Dave" <admin@_NOSPAM_BLOCK_blake-independent.co.uk> schreef in bericht Marina,
Yep! That works fine.
Thanks
Dave
Hi David,

In ISA, drill down to servers and arrays, servername, access policy, ip packet filters.
Create a new packet filter, custom, TCP outbound, internal port dynamic, external port fixed 119.

Will this work for you?

Marina
"David Bolt" <[email protected]> schreef in bericht Marina,
Hello again.
I'll check up those locations.
Yes, I am running antivirus, managed to get something on the network while installing it but it's working fine now.
The thing that surprises me is that I have no problem using OE on one of the workstations as a newsreader, and when the network configuration that we have already worked through was incorrect I could access newsgroups from the server as well.
Anyway, no further access 'till Monday so no panic.
Thanks again
Dave

Hi David,

We gotta stop meeting like this ;-)

Did you already know about www.smallbizserver.net and the microsoft.public.backoffice.smallbiz2000 newsgroup? Have a look there anyway.

About OE on the server: I know you'll have to add some serverrules in ISA, but I would have to look it up for you. (You are running antivirus, right?)
I'll do that later tonight or tomorrow.

Marina

"David Bolt" <[email protected]> schreef in bericht Marina, Hello again!
Yes, I did run the IIS wizard. All it does is restrict to a particular ip address, I used 192.168.16.2
I agree about not using the server as a workstation, but with all the fun I am having it is very useful to be able to go to the newsgroups etc from the server, since it is the only computer in that room. If you have any idea where to find that information I would be interested.
I have now made sure that RAS clients will get IP from DHCP, and internal LAN. I also found some settings to do with enabling VPN that I thought I had already set.
I found a nice document that told me I have to set IIS to publish the web pages using port 81, which should have been a bit more easily found out. Sometimes I despair at MS's documentation. All the information is in there somewhere, but finding it can be 'difficult'
Anyway, I think your help has got me past my worst problems for now. Thanks.
Dave
Hi David,

Have you run the IIS-wizard from the SBS-console.
I wouldn't worry about the Jetdirect, I've never really liked that stuff.

If your would like to run Outlook Express from the server (mind you, it is not recommended to use your server as a workstation!), you will have to make some modifications in ISA. I would have to look it up for you.

In the RRAS configuration, did you setup that RAS-clients will get an IP from the DHCP server, and that it should only look to your internal lan? You also could setup a static pool for this (but that's not necessary).

Marina
 
Back
Top