RPC Error in server 2003

[Ethan Pierce]

I know this isn't exactly the right server for this question but I can't
find a 2003 server so I'll give it a shot.....



Hi All,

Ok here is the deal. I have a Cisco uBR 900 DHCP Router that assigns 1
Static ip address to my server and dynamic ip addresses to my work stations
(my server is not DHCP). I have 2 Network adapters in my Server, one that
is connected to the Cisco and one that is connected to my hub. Now when both
of them have numbers entered in them I get a RPC error, like they are
bumping heads. I have been banging my head against the wall trying to get
them to work together any ideals?

Basically what I am saying is that I have 2 network adapters on my server
and they keep crashing my server. I need them to work together, 1 for my
static ip that my sales team uses to get into the server when they are out
of the office (24.138. ect) and the 2nd one to be the internal ip address of
the server (192.168.1.101 or what ever).

Besides that problem my server is running great. I greatly appreciate any
help. This is really kicking my butt.


~Ethan

 

[William M. Smith]

Hi All,

Ok here is the deal. I have a Cisco uBR 900 DHCP Router that assigns 1
Static ip address to my server and dynamic ip addresses to my work stations
(my server is not DHCP). I have 2 Network adapters in my Server, one that
is connected to the Cisco and one that is connected to my hub. Now when both
of them have numbers entered in them I get a RPC error, like they are
bumping heads. I have been banging my head against the wall trying to get
them to work together any ideals?

Basically what I am saying is that I have 2 network adapters on my server
and they keep crashing my server. I need them to work together, 1 for my
static ip that my sales team uses to get into the server when they are out
of the office (24.138. ect) and the 2nd one to be the internal ip address of
the server (192.168.1.101 or what ever).

Besides that problem my server is running great. I greatly appreciate any
help. This is really kicking my butt.

Hi Ethan!

A Windows 2003 Server newsgroup doesn't seem to exist yet, but you should
also be able to find relevant help in some of the microsoft.public.win2000.*
newsgroups.

From the your description, I'm seeing the router, switch and hub plugged
into a loop. I'm also seeing one NIC of your server getting a public address
directly from the router to connect to the Internet and also getting a
private address through the hub from the router again.

R -- S
\ /
H
|
Workstations

If this is the case, you may want to reconsider your network topology.
Unless your Server is acting as a router itself, which it shouldn't be doing
if you've already got a router on the network, then the two NICs don't
*need* to work together or even need to be used.

Arrange your network so that the server is another node on the network like
your workstations. Assign it a private IP address only.

R
|
H
/ \
S W

Your router should have ports that you can forward from the Internet to
ports on your server. For example, if you're running web services on your
server then you would open a port on the Cisco router so that:

any request coming from through public address 24.138.xxx.xxx on port 80
forwards to private address 192.168.xxx.xxx (your server) on port 80

Placing your server directly on the Internet with a public IP address and
all ports open is definitely a high security risk. Forwarding ports through
the router will block a lot of virus threats and hackers.

Hope this helps! bill

 

[Ethan Pierce]

Hi Ethan!

A Windows 2003 Server newsgroup doesn't seem to exist yet, but you should
also be able to find relevant help in some of the microsoft.public.win2000.*
newsgroups.

From the your description, I'm seeing the router, switch and hub plugged
into a loop. I'm also seeing one NIC of your server getting a public address
directly from the router to connect to the Internet and also getting a
private address through the hub from the router again.

R -- S
\ /
H
|
Workstations

If this is the case, you may want to reconsider your network topology.
Unless your Server is acting as a router itself, which it shouldn't be doing
if you've already got a router on the network, then the two NICs don't
*need* to work together or even need to be used.

Arrange your network so that the server is another node on the network like
your workstations. Assign it a private IP address only.

R
|
H
/ \
S W

Your router should have ports that you can forward from the Internet to
ports on your server. For example, if you're running web services on your
server then you would open a port on the Cisco router so that:

any request coming from through public address 24.138.xxx.xxx on port 80
forwards to private address 192.168.xxx.xxx (your server) on port 80

Placing your server directly on the Internet with a public IP address and
all ports open is definitely a high security risk. Forwarding ports through
the router will block a lot of virus threats and hackers.

Hope this helps! bill

Thanks! That makes a lot of sense. I finally got it working though, I
updated the bios of the mb, updated the drivers for my adapters, and changed
the pci slot of one of my adapters, after doing that I didn't have any
conflicts between the two adapters (thank god)... So I think I solved it.
Thanks! now the only problem I am having is connecting my macs with OS X.
it keeps giving me a login error, not the -5000 error, I resolved that
already. Which if any one is having that problem you can find a detailed
article on how to fix it at www.macwindows.com. Thanks again bill!


Ethan

 

[William M. Smith]

Thanks! That makes a lot of sense. I finally got it working though, I
updated the bios of the mb, updated the drivers for my adapters, and changed
the pci slot of one of my adapters, after doing that I didn't have any
conflicts between the two adapters (thank god)... So I think I solved it.
Thanks! now the only problem I am having is connecting my macs with OS X.
it keeps giving me a login error, not the -5000 error, I resolved that
already. Which if any one is having that problem you can find a detailed
article on how to fix it at www.macwindows.com. Thanks again bill!

Hi Ethan!

Glad you're up and working!

I'm curious to know if the login problem you're referring to has to do with
2003's default client signing policy or something different. I'm always
interested in these problems and what folks do to resolve them.

bill